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 had same problem on a Lenovo laptop that updated to windows 11. The culprit was the Lenovo software, it didn't like windows 11. Removed Lenovo software and the laptop came back like new! Hope this helps you!

Cheers!

Answer 2

At first, I updated from 21H2 to 22H2 via Windows Update. Along with this problem, that introduced several others to my system. So, I went to Settings > System > Recover > Reset This PC and had it download a copy from the cloud and keep my files. Some of the other issues went away, but this one continues. I'm on a local account. Has anyone tried converting over to a Microsoft Account login and then switching back to local to see if that clears it up?

Some of the posts here say with a full re-install (saving nothing), the problem goes away. But, I really have no desire to do yet another re-install of this OS.

We should not have to do go down rabbit holes chasing down a fix for this. I am not about to do that and risk screwing up my wife's HP Envy Laptop because of MS sloppy programming . I am not going to do a factory reset and go through that needless agony or remove the manufacturers software that is used and even doing all of this does not guarantee it will not come back with the next updates. This is a MS problem and MS needs to get off their *** and fix it. It would seem by now with the number of posts about it and the bug submissions to the Feedback Hub that they have noticed this is causing problems but I guess they are to busy coming up with more updates to send out for us to install that will cause more errors besides this one.

Now there is a work around and mind you only a work around and "NOT A FIX". If you are tired of seeing these errors then I would suggest going here https://answers.microsoft.com/en-us/windows/forum/all/many-persistent-errors-in-event-viewer-after/c218ee04-89a5-4ce2-805d-565b8d1b1744?page=18](https://answers.microsoft.com/en-us/windows/forum/all/many-persistent-errors-in-event-viewer-after/c218ee04-89a5-4ce2-805d-565b8d1b1744?page=18)  and look for the first post by "[SH2071" . Like I said this is no way a fix. When MS decides to deploy an update to correct "their" problem and it is corrected I will re-enable the log. I have had no problems with my wife's laptop computer with disabling that log. I do want to let you know that several days ago I re-enabled that log just to check and within about 5 minutes there were over 30 errors already. There is no excuse for this to happen. I then cleared the log and disabled it again.

I would not count on a fix anytime soon with the way things look and now that it is the holidays as well.

Respectfully

Answer 3

The problem with the Feedback Hub (besides Microsoft not paying any attention to it) is that for Autopilot problem, I currently see only 40 people having upvoted 7 reports (and not one of those has an official response of any kind). Of course, MS won't let us see reports by people in other rings. But, still, 40 upvotes for something I've seen happening on the web for over 3 months isn't going to get their attention.

If anyone is suffering from this, go upvote those. Even better, submit your own report with a Recording.

Answer 4

I did report to MS. Ist Tech went through the usual settings then connected with another tech who knew about the problem and said there will be a fix coming in the next upgrade. That was September. The next tech I contacted wanted to go back to square one. When I said there was supposed to be a fix for the event he closed down. I am still waiting for the supposed fix.

Answer 5

Seven months since this thread was opened - seen no response from MS yet - par for the course from MS - we are only users anyway - why should they worry about us !!