I have also applied your advice, I will keep you informed
Many persistent errors in Event Viewer after Windows 11 build 22598.ni_release.220408-1503: "Autopilot.dll wil error was reported"
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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?
Windows for home | Windows 11 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
338 answers
Sort by: Most helpful
-
Anonymous
2022-10-28T20:25:48+00:00 -
Anonymous
2022-10-28T17:50:59+00:00 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
-
Anonymous
2022-10-28T08:09:35+00:00 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.
-
Anonymous
2022-10-27T17:55:13+00:00 i've got that problem since 17/03/2021.
Start on w10, same problem on w11 of course.
Have to change OS ?
-
Anonymous
2022-10-27T17:09:39+00:00 I'm based in UK so monthly 'Patch Tuesday' first thing on Wednesday morning. Wednesday 10th August, installed August updates as normal, restarted, error first recorded at that exact time, no prior records which I believe are held in event viewer history for 14 days. Still on 21H2 Windows 10, 22H2 only arrived as an option to install less than a week ago. Seems there is no pattern who is affected no matter what system running and seems no definitive time when first noticed. Touch wood, all I have the error log recordings, noticed none of the issues mentioned by others. This, no doubt, is something MS concocted to steal our personal info held on computer. Sort it out Microsoft.