This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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?
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.
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!!! :)
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.
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'.
Hello Michaelirons, excuse my poor english langage.Thanks for your answord, so i wait !
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!!! :)
This error, in my case, occurred when I went from windows 11 21H2 to 22H2 in October. I used Windows update! The update appeared to go well, no errors. Running SFC and DISM found no errors.
So far I have not had any performance issues.
As for my configuration, with the exception of software, like Norton, I have made no changes or modifications to the system.
The error occurs at sign-in, I use my Microsoft account, and when I use a Microsoft app such as mail, store, etc.
