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've got that problem since 17/03/2021.

Start on w10, same problem on w11 of course.

Have to change OS ?

Answer 2

I have the same problem.

That said, my machine is working just fine, notwithstanding these error messages appearing multiple hundreds of time per day.

My untutored view is that it's sloppy programming somewhere and the offending party seems unable or unwilling to fix it.

Life's too short for this nonsense - I've disabled the log, so the errors are no longer reported.

How?

Within EventVwr, navigate down the logs (left hand pane) until you reach Applications and Service Logs-Microsoft-Windows-ModernDeployment-Diagnostics-Provider-ManagementService

Right-click on the log - Properties - Disable log

My machine continues to work just fine.

Answer 3

I have the same problem.

That said, my machine is working just fine, notwithstanding these error messages appearing multiple hundreds of time per day.

My untutored view is that it's sloppy programming somewhere and the offending party seems unable or unwilling to fix it.

Life's too short for this nonsense - I've disabled the log, so the errors are no longer reported.

How?

Within EventVwr, navigate down the logs (left hand pane) until you reach Applications and Service Logs-Microsoft-Windows-ModernDeployment-Diagnostics-Provider-ManagementService

Right-click on the log - Properties - Disable log

My machine continues to work just fine.

Thank you so much for this remedy as I will do this on my wife's laptop. Even though this does not solve what is causing these errors being generated and the lack of MS acknowledging this problem and implementing a fix, I find this the best way to take care of these errors at this time. I am so tired of MS updates causing errors that bleed red in our Event Viewers for users to chase down like this one. Like you my wife's laptop is running fine and I am sure it will continue to do so after I do what you suggest. Thank you again.

Respectfully

Answer 4

I have also applied your advice, I will keep you informed

Answer 5

I have the same problem.

That said, my machine is working just fine, notwithstanding these error messages appearing multiple hundreds of time per day.

My untutored view is that it's sloppy programming somewhere and the offending party seems unable or unwilling to fix it.

Life's too short for this nonsense - I've disabled the log, so the errors are no longer reported.

How?

Within EventVwr, navigate down the logs (left hand pane) until you reach Applications and Service Logs-Microsoft-Windows-ModernDeployment-Diagnostics-Provider-ManagementService

Right-click on the log - Properties - Disable log

My machine continues to work just fine.

Only logged on this forum to say to You, sir...THANK YOU!!!!!Big Thank you.

You alone fixed an issue that this God awfully "update" destroyed my laptop, amongst numerous issues that I had to spend precious time to fix.

But this constant error made most of my applications, especially games, just crash. 100% it was its fault.

Tested with the MS login Service Turned OFF, but that brings other issues with MS account like No Windows Store.

If only MS hired more competent, think out of the box people like yourself, we would not have such lame issues in the 1st place.

Thank you again, you saved me from performing a "format C:" and now I can enjoy, mostly as it was Before this useless update.

Totally works.