I have since updated to 22610.1 and the errors persist.
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-05-05T15:43:45+00:00 -
Anonymous
2022-08-01T23:51:18+00:00 Another user enjoying the lovely crashes. Microsoft, a few people moved to working from home, it is a bit difficult to continue working when your OS keeps crashing. If you cannot produce a solid product, don't release it yet. Fortunately alternatives like macOS and Linux allow me to continue working. In the event someone from Microsoft looks into this at one point in my lifetime. Quite literally did a fresh install, not keeping my data, to get past this. No such luck. Is Windows 11 the new Windows 8, Windows Vista, or Windows ME?
Edition Windows 11 Pro
Version 21H2
Installed on 7/29/2022
OS build 22000.832
Experience Windows Feature Experience Pack 1000.22000.832.0 -
Anonymous
2022-07-24T20:18:58+00:00 Has anyone found a solution to this? I keep getting dozens per hour and my system hard crashes as a result.
-
Anonymous
2022-05-11T02:51:08+00:00 Thank you, I have since updated to 22616.1 as well and the errors persist.
-
Anonymous
2022-05-11T02:44:35+00:00 I'm still getting them on 22616.1