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

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.

I seriously doubt the issue is MS Edge. I'm on Win 10 Home and my Event Viewer is riddled with the error as well, but I never even bother to open Edge and the errors are still there. I use Firefox, I refuse to use Edge browser. It also cannot be tied to OneDrive as again I have the issue yet that was one of the first pieces of junk I deleted ASAP. If I could get rid of that dumb Your Phone app too that would have been gone without a second thought as well.

To people complaining about them needing to fix the issue though, run this through your heads. There's a known issue with the DWM background process that's been around since Windows 8. It causes major spikes on the GPU to the point the entire system can get locked up for 10 seconds or more, not even cursor movement is possible, or it can cause a memory leak that straight out crashes the system after an hour or so of running. This has NEVER been fixed in all the years since it started and an obscene amount of people (myself included) have the issue. But all Support can do is point fingers at the users, not their own products. There's an audio issue on here as well, also known that a lot of people are experiencing which has never been resolved either. Both issues have been there from the very start of this 2yr old computer after the initial setup and updates were done, before anything else had been added onto it. They also dont' care to fix their "Disable Automatic Updates" feature that's fully broken on the Xbox App and has been a very long time now as well. MS only cares about making money, they don't care about their customers as long as they keep wasting money.

If they happen to fix it, great, if not, no big surprise in the slightest. Companies care nothing about their customers. They never have and never will. They are only in it for the money.

Answer 2

With me, does not seem to be an Edge issue. First instance of error was 10th August, started at exactly same time as restarted after installing August WUD's, Edge would have been opened later. Checked this morning, first recorded error @ 6:39 am, which was same time as pressing 'ON' button. First open of Edge, 14 minutes later. Edge itself was auto updated on 7th August & again on 13th, I assume if it was an Edge issue this would show an update same day/time as WUD's install.

Update. Looks as though I got it wrong. On boot got at least 14 errors in first couple of minutes. But, yes, when opening Edge, get 2 to 3 occasions of error BUT also get random errors between when Edge is closed. In theory, all background Edge tasks are OFF but who knows with MS. I'll try to keep eye on it. Last 24 hours shows 95 instances of errors, during this time had 2 boots, so in theory, 30 could be occurring at start ups,

Answer 3

This morning at starting my laptop, event viewer recorded 139 errors, event id 1010.

I think MS does not care a bit to fix this at all. Why for heaven's sake?????

Answer 4

AS always with MS, there is an ulterior motive behind this, they know about what this is, normally stealing your private data etc.

Answer 5

Been keeping eye on errors. They do occur immediately @ boot, most of them are when I open Edge, does not appear to be affected how long a session is.

Number of errors per session seems to vary considerably - 2 entries over zero time, 8 entries over 13 seconds, 6 entries over 7 seconds, 5 entries over 65 seconds. As you see, nothing consistent about happenings.