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

https://appuals.com/autopilot-dll-wil-error-was-reported/

I was able to solve the problem on that site.

The Microsoft Account Sign-in Assistant Service seems to be the problem.

What option worked?

Answer 2

https://appuals.com/autopilot-dll-wil-error-was-reported/

I was able to solve the problem on that site.

The Microsoft Account Sign-in Assistant Service seems to be the problem.

What option worked?

Disabling the Microsoft Account Sign-in Assistant service tends to work.

Answer 3

https://appuals.com/autopilot-dll-wil-error-was-reported/

I was able to solve the problem on that site.

The Microsoft Account Sign-in Assistant Service seems to be the problem.

What option worked?

Disabling the Microsoft Account Sign-in Assistant service tends to work.

TSM007, thanks for clarifying what worked for you. I agree the Microsoft Account Sign-in Assistant Service appears to be the culprit. The error appears any time a Microsoft app is used.

That option didn’t work for me since I use Microsoft's calendar, Store, and mail app. I also have to use Edge in Internet Explorer mode to access my security cameras.

When I disabled Microsoft Account Sign-in Assistant service the error went away but was unable to access MS apps.

Creating another user didn’t solve the issue either.

Answer 4

https://appuals.com/autopilot-dll-wil-error-was-reported/

I was able to solve the problem on that site.

The Microsoft Account Sign-in Assistant Service seems to be the problem.

What option worked?

Disabling the Microsoft Account Sign-in Assistant service tends to work.

TSM007, thanks for clarifying what worked for you.

 

That option didn’t work for me since I use Microsoft's calendar, Store, and mail app. I also have to use Edge in Internet Explorer mode to access my security cameras.

 

When I disabled Microsoft Account Sign-in Assistant service the error went away but was unable to access MS apps.

Creating another user didn’t solve the issue either.

 

Yes indeed, that is the limitation for this workaround. MS really needs to fix this issue ASAP.

Answer 5

Wanted to reply to the most recent and intelligent comment about this issue as I'm sure you know, Google results go back a year or more. My two cents:

This cropped up for all of us during a "no going back" update, like 22H2 in our cases. But not everyone on 22H2 is getting this, and it seems sporadic with users of earlier versions of Win 11 who didn't go up to 22H2 yet. It's related to MDM and the Autopilot services, which are part of the whole Cloud Login Live Microsoft **** apparatus that is common for mass-deployment business systems that can be rolled out to all AD users in a domain. There is a commonality between all of us though and I am wondering if it has to do with one or more of the following:

AMD-based TPM attestation issues, or just fTPM use in the BIOS in general.

Critical failures during the initial or subsequent Win 10 to Win 11 update that we all did when it was offered. Especially if all of us took the earliest update possible as part of the Insider Build program in Win 10, like I did. Perhaps something specific to the version specifically rolled out to us on the day/cycle version of 11 we were given.

Interuption of the OOBE provision/mandatory "first screen setup" of 11 at either the 21H2 or 22H2 update and most critical "please don't break" moment.

Use of WSL and/or hyper-v .

Manual uninstallation of "critical" Windows Store apps that Microsoft was very stuck on making permanent no matter what and now giving no options for removal either from Store direct or the Installed Apps system menu.

I think it's something in those scenarios that did it, with my money being on AMD and their complete failure with TPM 1.2 and 1.3 and fTPM integration into the mandatory Win 11 UEFI system we went to. On boards older than around 450+ model, the chipset and firmware problems and GPU driver issues can be severe and system breaking. Also, disabling the Live Sign-In service is not a good solution at all and I'm amazed it hasn't broken something on the dependency chain for someone badly enough to cause posts about it. It breaks a lot of things that aren't necessarily visible.