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.
With me, upon restarting the August 22 Windows monthly updates, the first ever instance of this error was recorded with-in a few seconds of logging in to the restart. Searching thru' the internet, this particular issue has a long history of coming & going. I seem to remember the first instance was over 3 years ago. MS must know what caused the issue then & how they resolved it so why can't they apply that same patch NOW?.
It was pointed out earlier that this is an out-of-box issue (probably not the OOBE Microsoft wants). But, for specifics, the time between Windows' first recorded boot following Resetting the PC and this Autopilot error showing up for the first time was 2 minutes and 9 seconds.
They should be afraid. There are other operating systems. Every cup of patience overflows once.
Seven months since this thread was opened - seen no response from MS yet - par for the course from MS - we are only users anyway - why should they worry about us !!
I did report to MS. Ist Tech went through the usual settings then connected with another tech who knew about the problem and said there will be a fix coming in the next upgrade. That was September. The next tech I contacted wanted to go back to square one. When I said there was supposed to be a fix for the event he closed down. I am still waiting for the supposed fix.
