Many persistent errors in Event Viewer after Windows 11 build 22598.ni_release.220408-1503: "Autopilot.dll wil error was reported"

Question

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?

Answer 1

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.

Answer 2

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.

Answer 3

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

Answer 4

I have Windows 10 PRO!!

Answer 5

I have two identical Dell computers that were updated from Windows 10 Pro to Windows 11 Pro and then to "attempt" to fix a windows update issue I was told to reinstall Windows 11 Pro. On the computer that had Windows 11 Pro reinstalled is where I have the same issue that is described here. Both systems have been updated regularly. On the computer with the reinstall I have run SFC and DISM and the issue remains.