I have a gigabyte AMD system with winver 22H2 22621.1194 with the same issue
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
2023-02-10T10:01:55+00:00 -
Anonymous
2023-02-09T14:38:05+00:00 It infects windows 10 as well, so I guess both 10 and 11 are the new windows 8.
-
Anonymous
2023-02-09T13:29:09+00:00 I have the same issue along with frequent freezing and stuttering, and it's not an MSI machine (nor do I have any of their software).
-
Anonymous
2023-02-09T13:09:34+00:00 Maybe it's not so easy to fix, especially if it involves third party software.
-
Anonymous
2023-02-09T09:58:58+00:00 Since this is been going on, does not matter machine you are, only common factor is that we are all on various versions of MS Windows - they, are who, for some ulterior reason have intentionally released this, otherwise why not fix it?