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

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.

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.

Thanks for the vapid reply. Only an entire thread of people receiving this error in the time frame of their device rebooting. The best answer someone could muster is turning off your memory XMP profile.

Since the odds everyone in this thread is running different hardware, cannot blame a singular component. The average person who purchased a device from Dell, HP, etc. probably does not have an XMP profile enabled.

We can expand this out that the issue is with autopilot.dll, which I would guess a majority of these individuals aren't having their device deployed and managed by the Intune MDM solution.

So would you like to try again, or are you in it for the post count?

Hi,

Windows 11 Pro Build: 22000.832 (Not insider) have the same problem.

The problem still exists in Insider Preview 10.0.22622.290 (ni_release). This is getting annoying. I'm having to save often. The problem seems to be after my computer has gone into sleep mode and I wake it up.