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

Anonymous
2022-04-28T20:22:08+00:00

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?

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

338 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-10-26T12:14:36+00:00

    Do you use fTPM and can you check on which version (curious if it's either 1.2 or 1.3)?

    EDIT: Also, have you at any point used developer options or software, like Dev Mode in the advanced settings or Visual Studio Community or the latest 2022?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-26T10:16:51+00:00

    My system is Intel based. Everything was fine on Windows 11 21H2. No modifications.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-10-26T05:59:31+00:00

    Sorry to destory your theory but I am on a Surface Pro 8. It came with Win 11 preinstalled. The first installed insider build was 22622.440 on 29 July.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-10-26T03:37:17+00:00

    AMD, yes.

    Motherboard - ASUS PRIME X570-PRO, BIOS 4403, May 2022
    ---- AMD Chipset Drivers 4.08.09.2337, September 2022

    I upgraded to Win 11 in mid-November 2021.

    I use a local account for Win 11 login and had my system offline to do it.

    No WSL or hyper-v.

    I disabled some bloatware programs, but I did not uninstall any in unconventional ways.

    I hope this helps.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-10-25T23:39:50+00:00

    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.

    Was this answer helpful?

    0 comments