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

I encountered the same problem in Windows 10, the latest update. 136 errors in Event viewer this morning. So far. I have not found a solution to the problem.

It appears - as usual - that Microsoft does not care. I ask myself what the programmer was programming here. Did he actually test it? I do not think so.

The suggestion to reinstall W 10 or 11 is unacceptable. This is a programming error and can only be corrected by MS even though, it does not hinder normal operation in WiFi (in my case). So, MS please investigate and fix it.

Maybe uninstalling the latest update and use the old update might help but need to test

Answer 2

Update:

Normally I return to my PC in the morning and it has rebooted, however after disabling the Microsoft Account Sign-in Assistant and found my PC had not rebooted overnight. I'm not claiming this to be the answer but may be worth testing.

Warning: I do not use a Microsoft account to login to my PC. If you do, this potentially could negatively impact you. Proceed with caution.

Status: Update 8/3/2022: My device has crashed and rebooted unexpectedly once in 24 hours. Thus far disabling the service has provided a huge boost in stability. Troubleshooting and diagnosing continues. There are two interesting alerts (on my device) for Windows Hello for Business.

• The driver \Driver\WudfRd failed to load for the device ROOT\WINDOWSHELLOFACESOFTWAREDRIVER\0000
• Windows Hello for Business provisioning will not be launched.

I explicitly choose not to configure Windows Hello, so why it is even trying to load a driver is confusing to me, outside of the fact that clearly Microsoft wants access to your webcam regardless of what you tell it during install.

How to [screenshots below]:

1. Press Windows Key + R on your keyboard to open the Run option.
2. Type services.msc and press enter. This will open a new window with the header Services. Don't randomly stop and start services unless you enjoy potentially crashing your device.
3. Find the service entitled Microsoft Account Sign-in Assistant. Double click the aforementioned service to open a new window for the Microsoft Account login service.![Image](https://learn-attachment.microsoft.com/api/attachments/60b8f214-4e51-47c3-89d0-bd14c193ef37?platform=QnA"https://learn-attachment.microsoft.com/api/attachments/91dd34fb-a617-446e-a6f1-e361f818e8f2?platform=QnA" rel="ugc nofollow">![Image](https://learn-attachment.microsoft.com/api/attachments/91dd34fb-a617-446e-a6f1-e361f818e8f2?platform=QnA

Answer 3

Update:

Normally I return to my PC in the morning and it has rebooted, however after disabling the Microsoft Account Sign-in Assistant and found my PC had not rebooted overnight. I'm not claiming this to be the answer but may be worth testing.

Warning: I do not use a Microsoft account to login to my PC. If you do, this potentially could negatively impact you. Proceed with caution.

Status: Device is still running. I will edit this post if it crashes once more.

How to [screenshots below]:

1. Press Windows Key + R on your keyboard to open the Run option.
2. Type services.msc and press enter. This will open a new window with the header Services. Don't randomly stop and start services unless you enjoy potentially crashing your device.
3. Find the service entitled Microsoft Account Sign-in Assistant. Double click the aforementioned service to open a new window for the Microsoft Account login service.![Image](https://learn-attachment.microsoft.com/api/attachments/60b8f214-4e51-47c3-89d0-bd14c193ef37?platform=QnA"https://learn-attachment.microsoft.com/api/attachments/91dd34fb-a617-446e-a6f1-e361f818e8f2?platform=QnA" rel="ugc nofollow">![Image](https://learn-attachment.microsoft.com/api/attachments/91dd34fb-a617-446e-a6f1-e361f818e8f2?platform=QnA

Answer 4

Disabling the Microsoft Account Sign-in Assistant will stop the errors associated with Autopilot.dll. I've done that and it works, but it comes with a trade-off. If you use Microsoft widgets that show your calendar or To-Do list or you use the Phone Link desktop app to connect with your mobile device, those connections will no longer work. There might be other consequences but those I've mentioned were relevant to my windows implementation. I'm on Windows 11, latest release.

I've decided, until Microsoft fixes the root cause of the Autopilot.dll WIL error, that I will ignore the event log, and just live with the problem. Fortunately, my PC does not crash as others have reported, so you'll need to decide which trade-off is best for you. I agree with everyone that this is a frustrating and irritating programming bug that Microsoft is taking way too long to fix.

Answer 5

All suggestions appear to be ok. BUT - I refuse to follow these because of their trade-offs. In my opinion, this must not be done, if this is a proven MS failure. It is their responsibility to fix it, not the users. So, MS to work and fix and soon!