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

Question

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?

Answer 1

I am on Windows 10 Home 21H2 19044.1889 and began receiving LOTS of occurrences of this error after accepting last week's Patch Tuesday (KB5012170 and KB5016616).

I am 100% certain I never had them before these updates.

So this issue is (A) STILL present today, (B) ALSO present in Windows 10, and (C) is triggered by SOMETHING included in KB5012170 or KB5016616.

I can roll back to a restore point, but I accept these updates for the protection they provide. Also, I prefer not losing changes in other software since the update. So would like to avoid rolling back.

I hope a fix is on its way. Thank you in advance.

Answer 2

Looks like it's a MS Edge bug. If you start MS Edge, new errors will immediately appear in the log. While MS Edge is running, the number of errors increases. I have so. If I run Google Chrome, then no errors appear.

Answer 3

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.

Answer 4

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.

Answer 5

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.