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
    2023-01-06T09:29:04+00:00

    Yes, lately my computer (Lenovo Ideacentre 3 07ADA05) which is a %#$@# cheap POS system...will start to pause and freeze if I have too many programs/apps running. Or it just simply will freeze after being on it for about 6-10 hours. Then it goes to the blue screen and restarts. I have the MiniDump files if anyone wants to debug them??

    I believe it has something to do with my Kernel as well as the Event viewer errors:

    Autopilot.dll WIL error was reported.
    HRESULT: 0x80070491
    File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 128
    Message: NULL

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-02T14:34:38+00:00

    Hello Microsoft - any body there? Been 8 months now since this thread started - so far no response at all, what about people that have sent you reports via feedback hub, appears you don't read USERS threads & comments - usual abysmal service from MS

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-01-02T12:08:09+00:00

    Ugh... so I updated, and while it did improve stability, the error came back. I want to disable that as a workaround, but one of my games called PHANTASY STAR ONLINE 2 requires the service to be active, or it will not let me sign in, so I am forced to activate it for now. Hopefully it won't give me many errors..

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-01-02T10:22:20+00:00

    Is it just me - but it appears quite a few postings follow the week-end. The trouble a lot of people had a year or two ago with WaasMedic was when it ran every Sunday morning at start-up, is this also more noticeable over the weekend, possibly running Sunday?

    I don't know. Could be.

    I hibernated my laptop. So far it started up and is running fine now. I think disabling the work folder service in services.msc might have probably fixed it. That or disabling and then manually enabling the Authetication service (the one that is causing issues). Probably either option since I did both of them. I am going to update to 22H2 and see if that will get rid of the problem, I've had a few suggest to me that since it provides stability.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-01-02T06:58:27+00:00

    Is it just me - but it appears quite a few postings follow the week-end. The trouble a lot of people had a year or two ago with WaasMedic was when it ran every Sunday morning at start-up, is this also more noticeable over the weekend, possibly running Sunday?

    Was this answer helpful?

    0 comments