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

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
4. Press Stop.
5. Change startup type from its' current setting to Disabled.![Image](https://learn-attachment.microsoft.com/api/attachments/91dd34fb-a617-446e-a6f1-e361f818e8f2?platform=QnA
6. Press Apply followed by OK to close the dialogue box.
7. Reboot your device and cross your fingers, send your thoughts and prayers, throw salt over your shoulder, or whatever else you do for good luck.

I saw one guy putting Automatic (delayed start) does it work?

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
4. Press Stop.
5. Change startup type from its' current setting to Disabled.![Image](https://learn-attachment.microsoft.com/api/attachments/91dd34fb-a617-446e-a6f1-e361f818e8f2?platform=QnA
6. Press Apply followed by OK to close the dialogue box.
7. Reboot your device and cross your fingers, send your thoughts and prayers, throw salt over your shoulder, or whatever else you do for good luck.

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

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.

I'm hitting this problem the rate of about 500 crash events per 24 hours according to Event Viewer.

I did a clean install of Win 11 21H2 about a week ago and have installed nothing other than Office and Adobe Photoshop/Lightroom. It crashes about every 5 - 10 minutes in a never ending death spiral. The system is negatively impacted by this event, sluggish and non-responsive for a few seconds at a time as I've used it.

The computer is an AMD 5800x based desktop on an Asus MB with 32gb ram and a pair of nvme drives, so it's a very fast system in general. I am running the Pro SKU with only an MSA connected. No domain, AD, or corp access of any type so the computer should have nothing to do with Autopilot functionality.

I was running 22H2 Beta for a while, but had to roll back to a clean install of 22H2 after a fatal Window Update failure I could not clear. It's been frustrating to have this completely clean and fresh install crippled by this problem.