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

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.

Answer 2

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.

Answer 3

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.

Answer 4

Actually windows hello services does not have to use the webcam, it can also refer to IR Camera or the fingerprint scanner, regardless I get the windows hello events too (I am using IR face unlock) so this issue clearly corrupts drivers or internal device communication in some way or another

Answer 5

It does help to keep commenting on this post. Keep it at the top so Microsoft hopefully sees it and works towards a solution. The original post is 90 days old, and no reply or answers from Microsoft.

This is exactly why we keep commenting. Maybe someone will find something that helps them figure out what the issue is.

Microsoft still wants all my data, so I'm sure they will pay attention at some point unlike elected officials.