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. Lz._ 38,106 Reputation points Volunteer Moderator
    2024-01-25T05:23:37+00:00

    @Rubert

    Appreciate you keep the 'discussion' going on. Another quite interesting finding...

    DISM /Online /Cleanup-Image /ScanHealth said "The component store is repairable". The corresponding Event Log event was "0 of 4 instances of system store corruption have been repaired...".

    So far so good

    DISM /Online /Cleanup-Image /RestoreHealth said "The restoration has been completed". The corresponding Event Log event was "1 of 4 instances of system store corruption have been repaired..."

    Not sure I understand???

    Same here, that did nothing re. the Autopilot WIL error :(

    0 comments No comments
  2. Anonymous
    2024-01-30T20:02:42+00:00

    Due to some other problems I was having, I went with "Recovery -> Reset this PC"... and after making a choice or two along the way, eventually got to and chose the one that basically said "Reset Windows, but please try to keep everything else as intact as possible."...

    As a result, I lost a couple of custom shortcuts on my start menu, but mostly everything else was OK. (No big program reinstalls or reconfigurations, for example).

    And now, no more of the autopilot errors. 👍

    3 people found this answer helpful.
    0 comments No comments
  3. Lz._ 38,106 Reputation points Volunteer Moderator
    2024-02-02T05:41:15+00:00

    After 3 years of updates over updates over updates... I reinstalled the PC (with 23H2 ISO) keeping nothing

    3 days later I haven't seen any Autopilot error

    0 comments No comments
  4. Anonymous
    2024-02-02T21:08:18+00:00

    I'd never had this issue before after W10 to W11, updates over updates, an in-place W11 upgrade from ISO and using the installation assistant to get 23H2 - effectively another in-place upgrade.

    But last week I was forced to re-install because after a system restore it became unbootable with Critical Process Died BSOD.

    I chose to install from USB keeping the partition which created a Windows.old folder but otherwise its was a clean install - except some settings and installed apps are recovered from the cloud during the install.

    Since then Ive been getting huge numbers of these events - around 200 a day

    There are multiple feedbacks in the Hub and posts going back years and still no resolution or comment.

    Just like the Metadata staging issue and others frequently reported - these days the focus seems to be on adding unwanted features instead of testing and actioning feedback.

    2 people found this answer helpful.
    0 comments No comments
  5. Lz._ 38,106 Reputation points Volunteer Moderator
    2024-03-08T18:46:38+00:00

    > 1 month after I reinstalled the PC (with 23H2 ISO) keeping nothing, still not a single Autopilot WIL error...

    0 comments No comments