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 No comments

338 answers

Sort by: Most helpful
  1. Anonymous
    2022-08-18T20:05:48+00:00

    Same issue on two computers. The first runs win11 22H2 build 22622.575 and the second win10 build 19044.1889.

    The problem on the Win10 pc leading to kernel critical errors and system restarts once per day. Disabling Microsoft signin assistant service eliminates the errors AND the system crashes but has major side effects (problems with Office 365, cant sign in on Game pass etc).

    At least i haven't experienced system crashes on the win11 pc.

    Thank you!

    Yes, as you and others report, disabling the MS Account Signin Assistant service does indeed stop the error from occurring, but also prevents some apps from signing in properly. In my case it's MS Edge, but Office 365 would be big as well if I used that.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-08-03T15:35:41+00:00

    Are we there again? MS does not care and gives a damn? Mr. Nadella, I hold you responsible for everything that happens at MS! Obviously and as usual, you Mr. Nadella are not interested in what your employees are doing.

    I agree that comments have to continue.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-08-03T15:22:50+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-08-02T15:44:28+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-08-02T02:24:32+00:00

    I'm hitting this problem the rate of about 500 crash events per 24 hours according to Event Viewer.

    I did a clean install of Win 11 21H2 about a week ago and have installed nothing other than Office and Adobe Photoshop/Lightroom. It crashes about every 5 - 10 minutes in a never ending death spiral. The system is negatively impacted by this event, sluggish and non-responsive for a few seconds at a time as I've used it.

    The computer is an AMD 5800x based desktop on an Asus MB with 32gb ram and a pair of nvme drives, so it's a very fast system in general. I am running the Pro SKU with only an MSA connected. No domain, AD, or corp access of any type so the computer should have nothing to do with Autopilot functionality.

    I was running 22H2 Beta for a while, but had to roll back to a clean install of 22H2 after a fatal Window Update failure I could not clear. It's been frustrating to have this completely clean and fresh install crippled by this problem.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments