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

338 answers

Sort by: Most helpful
  1. Anonymous
    2022-08-18T19:58:15+00:00

    Bingo! Thank you very much.

    Indeed, the error occurs every time I load MS Edge.

    I tried disabling the Microsoft Account Signin Assistant service as suggested by others, which does indeed prevent the error from occurring -- but it also prevents Edge from signing into my MS account and thus prevents it from syncing.

    I was worried that disabling the service would prevent OneDrive from signing in and syncing, since I rely heavily on OneDrive. But OneDrive works just fine with the service disabled. Just MS Edge in my case (from what I've seen so far). Of course other apps as reported by other users.

    I wonder if this is related to me signing into Windows with a local account rather than a MS Account. Microsoft clearly hates that, judging by the lengths to which they go to prevent me from doing it.

    Not quite ready to dump Edge yet, although I could go back to Chrome if I have to. I will give it a little time to see if Microsoft provides a fix by the September patch. Now that they seemingly pushed the bug out to all their Win10 users (as opposed to just Win11 users) one can hope it gets on their radar.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-08-02T15:40:12+00:00

    All suggestions appear to be ok. BUT - I refuse to follow these because of their trade-offs. In my opinion, this must not be done, if this is a proven MS failure. It is their responsibility to fix it, not the users. So, MS to work and fix and soon!

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-08-01T17:23:05+00:00

    I also have the same problem on Win 11 Home 22000.832, in my case the laptop touchpad becomes completely unresponsive every time autopilot crashes

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-07-25T02:17:12+00:00

    The crashes always occur at the timestamp of the error after having rebooted.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  5. VARADHARAJAN K 9,721 Reputation points Volunteer Moderator
    2022-06-03T17:49:04+00:00

    Boot windows in to safe mode and delete the following file

    dllmain.cpp

    from *onecoreuap\admin\moderndeployment\autopilot\dll* folder

    Restart windows.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments