Many persistent errors in Event Viewer after Windows 11 build 22598.ni_release.220408-1503: "Autopilot.dll wil error was reported"

Anonymous
2022-04-28T20:22:08+00:00

I used to be part of the the Windows 11 Insider Beta channel. After updating to build 22598.ni_release.220408-1503 I began to see the same error in Event Viewer extremely frequently:

The errors are all the same and read as follows:

Autopilot.dll WIL error was reported.

HRESULT: 0x80070491

File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 128

Message: NULL

I have never used any program called Autopilot or Modern Deployment. After seeing this problem I immediately left the insider program and am now queued for enrollment. However no new Windows update has happened and these errors persist. How do I prevent these errors?

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

338 answers

Sort by: Most helpful
  1. Anonymous
    2023-02-07T13:32:27+00:00

    Didn't fix it for me. Still getting Autopilot errors. Forty-nine (49) yesterday.

    0 comments No comments
  2. Anonymous
    2023-02-07T16:13:46+00:00

    I only have a personal account. I disabled logging of the error to hopefully minimize the impact of this annoying error. I know this is a bandaid.

    0 comments No comments
  3. Anonymous
    2023-02-08T16:11:26+00:00

    how long till an update is rolled out? I can not resort to reinstalling windows.

    0 comments No comments
  4. Anonymous
    2023-02-09T07:57:51+00:00

    Hi all,

    I just noticed that some of us are on a MSI machine. Does someone has the same problem on another brand? Just in case maybe it's an issue with some MSI software installed that can be disabled until they solve.

    g4b0

    0 comments No comments
  5. Anonymous
    2023-02-09T09:58:58+00:00

    Since this is been going on, does not matter machine you are, only common factor is that we are all on various versions of MS Windows - they, are who, for some ulterior reason have intentionally released this, otherwise why not fix it?

    0 comments No comments