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
{count} votes

338 answers

Sort by: Most helpful
  1. Anonymous
    2022-10-26T21:21:28+00:00

    I can't speak for others but I dropped it into Feedback hub back in May. Moderators have told me that this error is by design. lololol Of course my response was that if that's the case and it's just dropping info that's supposed to be there, they could save a lot of time and energy wasted by many people by simply changing it to an INFO line instead of ERROR, pointing out that the word ERROR means that something isn't working as it should be.

    0 comments No comments
  2. Anonymous
    2022-10-26T21:28:34+00:00

    I wish that were the case. But I was told that this behavior is by design. Also, I don't think any manufacturers can be blamed for a new error that pops up in Windows on machines that were manufactured in some cases, several years ago. It's been across numerous machines, AMD and Intel, and seems to span nearly every combination of parts.

    Most of the time it is as you say and I'm usually the first to point that out but this one I'm pretty sure is entirely owned by MS. The funny thing is, my last reply to them nearly a month ago was that if it is intended behavior and letting us know something has been attempted that shouldn't be and it was stopped by design, the proper notation would be INFO and not ERROR. I just checked and as of today they never replied.

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

    I agree 100% with what you said Kevin. By design my *** LOL. Thank you for your response.

    Respectfully

    0 comments No comments
  4. Anonymous
    2022-10-26T22:15:18+00:00

    To kevinfreels! Thank you for your information on the response from "moderators" at Feedback hub. I do not think of them very much: they are a useless bunch of ...... (think what you may). I have not heard a more stupid response like this one. Are they trying to take the mickey out of us???? This unprecedented. I don't think that the CEO would agree with such a dumb and stupid response from his employees, or would he? I am flabbergasted by that response. The question is what can be done about such a mess. If MS comes through with this, what can we expect in the future? More of this?

    0 comments No comments
  5. Anonymous
    2022-10-27T05:52:28+00:00

    Someone reporting RESPONSE from MS ?????. Surely that is unknown!. Have seen no MS response on this this particular thread.

    0 comments No comments