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 know only one thing. MS appears not interested in fixing it. Typical for MS.

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

Answer 2

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.

Answer 3

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.

Answer 4

I kept Microsoft Account Sign-in Assistant disabled, and except for Edge being unable to sign-in and sync (which I can live with for a while) I have had no other problems so far. No other Edge problems, and no other error events.

I didn't have any crashes or other issues, even before disabling the service (about a week after receiving the update). And my PC runs 24/7, only rebooted after the monthly Patch Tuesdays.

I keep everything from Microsoft uninstalled, disabled and/or logged out, unless I specifically need it, such as OneDrive. Again, I use a local Windows account. Maybe Office 365 or some of the other apps that rely on the Sign-in Assistant are the ones causing instability when they are unable to phone home like they were designed to do.

Answer 5

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.

Of course I agree that it should be fixed. And I think it will.

We have to remember the context here: Microsoft has thousands of people spending all their time thinking of ways to pull users and their information into the Microsoft datatank. They lose sleep over the very thought that some users escape their reach. They will make even the smallest Hello World app sign into your Microsoft Account, and thus become part of the Windows data suction plumbing. And preferably as automatically and discreetly as possible, so users don't decide to disable it or uninstall the app.

Like with Android, that is the entire purpose of Windows. (And yes, I am an Android and Gmail user as well.)

Evidently, this Sign-in Assistant service is an integral part of the plumbing used to facilitate the data suction. I think there is a good chance Microsoft will fix this to keep the suction running as smoothly and quietly as possible, and avoid threads like this, and avoid people disabling the auto sign-in service like we're doing here.