Share via

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-09-05T06:01:43+00:00

    I think the problem also causes startup problems. When I start my laptop, the logo is displayed but then the display remains black, but the laptop is on. Pressing the start button shuts it down, then wait for some time and press the start button again and the laptop starts normally. In the reliability monitor it says that a Hardware Error occurred, and that Windows was not shut down properly. Nothing of that kind in the Event Viewer. Question is: has the error something to do with it.

    0 comments
  2. Anonymous
    2022-09-08T07:41:16+00:00

    The error continues to exist. Today, I disabled the Microsoft Account Sign-In Assistant as it was suggested here. Then restarted the PC. What is the result? SAME ERROR!!! So, this is NOT a work around that can be recommended.

    0 comments
  3. Anonymous
    2022-09-08T08:21:50+00:00

    Check again just to be sure, i have zero errors and zero system crashes since i disabled the service.

    0 comments
  4. Anonymous
    2022-09-08T08:56:36+00:00

    I wouldnt really disable or do any "fixing" since this issue is entirely something on microsofts end.It happens on a brand new system with a fresh windows install 10 or 11 it doesnt matter.

    What worries me is that i saw this error back in july and it is STILL present today so we need to learn to live with it since microsoft needs half a year to fix something if they do it at all even...

    0 comments
  5. Anonymous
    2022-09-08T09:23:13+00:00

    Had a problem with WaasMedic last year, a lot of users had same issue, in that case, certain users found their computers unresponsive for up to an hour every Sunday morning on boot. It took MS 12 months to sort out following numerous postings on respective thread. People were using Feedback Hub to submit logs. No acknowledgements from MS. Issue suddenly disappeared after 12 months so perhaps Pekaa1's 6months to fix could be optimistic. MS know what it is, something they have included for data farming etc. they want to know what colour socks your wearing, how many coffees you have per day etc, they are not concerned the troubles this causes for their users.

    0 comments