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: Newest
  1. Anonymous
    2022-08-19T08:46:39+00:00

    I had some errors caused by the file MicrosoftEdgeUpdate.exe located C:\Users\User_Name\AppData\Local\Microsoft\EdgeUpdate

    It has a launch through the task scheduler. Temporarily replaced MicrosoftEdgeUpdate.exe with old version 1.3.147.37

    I have this version does not cause errors on startup.

    After replacing the file, MS Edge keeps throwing errors on startup.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-08-19T07:25:31+00:00

    Being bit of a nerd, try & keep records of updates etc:

    August 5th - MS Edge Webview2Runtime appeared automatically in Programs & Features

    August 7th - Edge Update

    August 8th - MS Edge Webview2Runtime update

    August 10th - Installed August WUD's (UK based - get on first boot Wednesdays)

    August 10th - Noticed issue when checking event viewer, issue started immediately after re-boot - no history prior to this time & date.

    August 13th - Edge Update

    August 14th - MS Edge Webview2Runtime update

    Edge settings Start Up Boost OFF, Background Extensions OFF - both of these if ON apparently means when CLOSING Edge, it is not really closed, but still runs in background, supposedly to make opening Edge quicker to open & loading last opened web-pages.

    Checked this morning, issued first recorded timed as on boot-up, did not load Edge till 10-15 minutes after.

    Been mention of using Feedback hub - between January & December last year had issue with WassMedic. 533 postings on community, 4075 views. THREE responses from some-one allegedly working for MS, all three near identical word for word. Numerous postings of logs being submitted, no acknowledgments or progress reports from MS, another case of MS deserting users. Issue finally sorted last December - still no MS response that issue had been fixed.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-08-19T05:52:52+00:00

    I know only one thing. MS appears not interested in fixing it. Typical for MS.

    Workarounds are not good enough, fixing it is the subject.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-08-18T20:05:48+00:00

    Same issue on two computers. The first runs win11 22H2 build 22622.575 and the second win10 build 19044.1889.

    The problem on the Win10 pc leading to kernel critical errors and system restarts once per day. Disabling Microsoft signin assistant service eliminates the errors AND the system crashes but has major side effects (problems with Office 365, cant sign in on Game pass etc).

    At least i haven't experienced system crashes on the win11 pc.

    Thank you!

    Yes, as you and others report, disabling the MS Account Signin Assistant service does indeed stop the error from occurring, but also prevents some apps from signing in properly. In my case it's MS Edge, but Office 365 would be big as well if I used that.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. 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