I have this error on a Windows 10 machine running build 19044
Many persistent errors in Event Viewer after Windows 11 build 22598.ni_release.220408-1503: "Autopilot.dll wil error was reported"
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-07-27T21:05:22+00:00 -
Anonymous
2022-08-02T08:57:32+00:00 I encountered the same problem in Windows 10, the latest update. 136 errors in Event viewer this morning. So far. I have not found a solution to the problem.
It appears - as usual - that Microsoft does not care. I ask myself what the programmer was programming here. Did he actually test it? I do not think so.
The suggestion to reinstall W 10 or 11 is unacceptable. This is a programming error and can only be corrected by MS even though, it does not hinder normal operation in WiFi (in my case). So, MS please investigate and fix it.
-
Anonymous
2022-07-31T19:48:20+00:00 Boot windows in to safe mode and delete the following file
dllmain.cpp
from *onecoreuap\admin\moderndeployment\autopilot\dll* folder
Restart windows.
No such path exists on my Win 11 system, Autopilot error is extremely persistent, please provide specific instructions to terminate error, or admit not possible.
-
Anonymous
2023-09-01T09:51:32+00:00 16 months now since reported, no acknowledgement seen from MS. So far been 52,848 views - MS used to also list number of actual postings - looks as though they are too embarrassed to do that now.
As always, with MS, there possible is something about this that they are not willing to disclose - their usual data farming of our personal data etc.
-
Anonymous
2022-11-12T21:20:53+00:00 After completing a fresh Windows 11 installation without saving any files from the previous installation, this error has not appeared even though the sign-in service is running.
Installing Windows 11 22H2 fresh requires signing in with a Microsoft account, but after setting up the system, users can change the account into a local one, thus avoiding having to put in a PIN or password. The topic error has not occurred for me so far with either account type, so that's a positive. (Having to sign in to my local system with an MS account for the first boot is annoying and seemingly unnecessary.)
On a side note, I cannot recommend Windows 11 22H2, because Microsoft has made so many unnecessary features and settings default. I have spent over three hours so far disabling, uninstalling, and changing settings that I do not want. For example, by default, essential folders like Documents and Desktop are in the OneDrive folder, so if you do not want to use OneDrive, you have to uninstall OneDrive, Unlink your system from OneDrive, and reassign those folders' locations back to their normal place, which ironically is called the default location. There is a multitude of similar annoyances in this version. I would expect this sort of thing if I'd purchased a Dell-built PC, but this is just the standard operating system. Sad times.