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

But... that's not a solution.

That's like placing a match book in front of the Check Engine light on a car's dashboard so that you can't see it light up anymore.

Answer 2

But... that's not a solution.

That's like placing a match book in front of the Check Engine light on a car's dashboard so that you can't see it light up anymore.

Hello my name is Don. I agree with you that SH2071's suggestion is not a solution and I am sure he does too as well as others but it is better than having that log fill up with hundreds upon hundreds of these errors while waiting for MS to find a solution and send out an update to fix it. MS knows about this problem and how could they not know with so many users experiencing and reporting it. MS will not even acknowledge this problem. Whenever MS decides to fix this I will re-enable that log on my wife's laptop.

Respectfully,

Answer 3

MS have had various issues like this for years affecting users. They reckoned that they were going to do more intense testing before releasing updates, there is also the so called 'insiders' who get pre-release issues for testing so in fact releases are 'tested' twice before release. Why are we still getting these problems - these issues are known to MS, ignored by them & still released - conclusion can only be for some ulterior motive on behalf of MS.

Answer 4

Dude you are right. That's the same error I am getting, same PID and everything. It freezes up my PC for several seconds and causes my audio drivers to change in discord. Occasionally it will cause a TDR error with nvddmkm.sys which freezes PC up longer, causes a game to crash, or flat out blacks out my screen(no BSOD yet). Microsoft you have a huge error going on right now with Windows 11 do you not realize that?

Answer 5

Gah. My system just crashed due to one of these. First time it's crashed instead of just closing a program.