This is the problem, this file does not exist in Windows home, hence the error. We have to wait for Microsoft to fix this in an update
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-08-05T11:46:15+00:00 -
Anonymous
2022-08-05T09:13:50+00:00 This is the message (several hundred) in Event Viewer:
Autopilot.dll WIL error was reported.
HRESULT: 0x80070491
File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 178
Message: NULL
Cannot find dllmain.cpp. Where is this file??? This error is becoming a nuisance.
-
Anonymous
2022-08-04T18:00:46+00:00 Well it decided to crash again. This time a new log file was too large. As such I'm going for a more permanent fix and just installing Windows 10. This has become too much of a nuisance to continue. I'll keep being a part of this thread as much as I can, but this is unacceptable.
The maximum file size for session "EventLog-Microsoft-Windows-Kernel-Process-Analytic" has been reached. As a result, events might be lost (not logged) to file "C:\Windows\System32\Winevt\Logs\Microsoft-Windows-Kernel-Process0x8800081Analytic.etl". The maximum files size is currently set to 1048576 bytes.
-
Anonymous
2022-08-04T16:55:10+00:00 The guy who is in charge of line 128 is currently out on PTO :).
On a serious note, I have not experience a crash as of yet, after my deluge of changes. My luck it will crash 10 minutes when my next call starts, but everyone keep on hitting that like and subscribe button.
-
Anonymous
2022-08-04T08:20:50+00:00 I do not think well of these "Work Arounds". They often cause some unexpected further problems in my experience. I repeat: MS fix it fast. It is MS's problem since it clearly says "..... in Line:128".