The only answer we can get is directly from Microsoft - they are the ones who instigated it (no doubt for some ulterior motive). Typically, no response from MS, I wonder why - guilty person's response always 'no comment'.
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: Newest
-
Anonymous
2022-11-05T08:26:07+00:00 -
Anonymous
2022-11-05T08:14:33+00:00 You are basically asking the same pertinent questions the rest of us are. We know all of us have something in common, something that happened around the upgrade (or a big upgrade) and that's the start point for diagnosing it as long as we don't have dev help. When this is explained and fixed, there will be something in the README about it that every one of us can say applies to us.
-
Anonymous
2022-11-05T04:35:59+00:00 Does anyone have news? Can this really cause some system instability and loss of performance? Is it a false positive and can we ignore this error?
It seems to be a recurring thing and several builds.
Is it linked to some initial configuration during Windows installation?
If you have this error, how did you update it? Clean install with recent ISO (without having to resort to major updates after installation) or was it through Windows Update?
Sorry for too many questions. LOL...
Thanks!!! :)
-
Anonymous
2022-11-03T18:14:47+00:00 Gah. My system just crashed due to one of these. First time it's crashed instead of just closing a program.
-
Anonymous
2022-11-01T22:54:51+00:00 Dude you are right. That's the same error I am getting, same PID and everything. It freezes up my PC for several seconds and causes my audio drivers to change in discord. Occasionally it will cause a TDR error with nvddmkm.sys which freezes PC up longer, causes a game to crash, or flat out blacks out my screen(no BSOD yet). Microsoft you have a huge error going on right now with Windows 11 do you not realize that?