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

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 right as the device crashes.

• 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.

It does not help to make comments reporting the error on an individual PC. To repeat: it is apparently a programming error/failure, which puts it into MS's shop to fix! And that must happen fast. I have almost 1000 errors in my Event Viewer. So, MS please, please fix it fast. Do not wait or try to sit it out.

Jus so I leave a trace here, maybe this will help the devs, in my case, the error occurs on line 138 instead of 128, I set the service to auto (from manual) and after reboot I still get the errors in events however the touchpad works (which I believe will not be long after a reboot or two or even in an hour just so) Whenever this error occurs on startup it prevents the Intel I2C controller to start correctly (and it is displayed with a yellow exclamation mark in device manager, when trying to install the driver, device manager spits out error 10) which then prevents the system to see the touchpad device (ASUS precision touchpad).

My config:

Asus Zenbook 14 UX425EA

Intel i5-1135G7 CPU

Windows 11 Home 21H2 22000.832 feature pack: 1000.22000.832.0

The problem in my case is 100% caused by the autopilot crashing since I have tried every possible driver-related fix and whenever touch;ad crashed mid-use there was the autopilot event with the same time stamp.

Autopilot crashing may or may not cause hardware issues (depending on config), this may be something similiar to a quite famous incident, when microsoft crashed webcams on windows machines through an update which then gave the similar error 0x80070491, that was back in 2016 or so.

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!

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.