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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2022-08-03T18:43:15+00:00

    I'm having the same error appear in my log, now at 1,679 error 1010, ModernDeployment-Diagnostics-Provider. Appears after every boot or resume from sleep.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-08-03T18:04:57+00:00

    Chill out people! It takes time to diagnose and fix bugs, then test them and get them into the servicing pipeline. You don't want to rush a fix and then create an even bigger problem. And yes, it can be a problem to get proper attention paid to a new issue.

    How many of you have used the Feedback tool to report this issue? If not then do so now. All you need to do is search for the event error and +1 the issue. That's it. That will draw attention to the problem. Be part of the solution.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. 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
  4. 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
  5. Anonymous
    2022-08-03T13:34:50+00:00

    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

    Was this answer helpful?

    0 comments