Autopilot.dll WIL error

Anonymous
2022-08-24T15:35:23+00:00

So this issue has been going on for almost a month now,event viewer is showing tons of these errors,i have 3 windows 10 installations and in each the error is there.Even tried to do a clean install on my main pc today to see if it would go away but to no effect.

This is the error:

Autopilot.dll WIL error was reported.

HRESULT: 0x80070491

File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 178

Message: NULL

I searched a bit trough the comunity and found out that there are tons of people having the exact same problem.

Windows for home | Windows 10 | 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

142 answers

Sort by: Oldest
  1. Anonymous
    2022-11-07T20:34:30+00:00

    I have a similar issue but on line 138. I do not have the 22H2 Windows 11 update installed. The problem started 10/24/2022. There are additional errors in Server, DbxSvc, DistributedCOM, etc. , but similar errors were occurring before this ModernDeployment-Diagnostics-Provider error started happening. A new problem is that yesterday and today my relatively new machine crashed and had to be forcibly rebooted. I can't prove this is related, however.

    Did you by chance perform an update using Windows update on or before 10/24/22?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-11-08T03:01:09+00:00

    Yes, but my date for this Fault 1010 line 128 started 10/28/2022

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-11-12T21:21:22+00:00

    After completing a fresh Windows 11 installation without saving any files from the previous installation, this error has not appeared even though the sign-in service is running.

    Installing Windows 11 22H2 fresh requires signing in with a Microsoft account, but after setting up the system, users can change the account into a local one, thus avoiding having to put in a PIN or password. The topic error has not occurred for me so far with either account type, so that's a positive. (Having to sign in to my local system with an MS account for the first boot is annoying and seemingly unnecessary.)

    On a side note, I cannot recommend Windows 11 22H2, because Microsoft has made so many unnecessary features and settings default. I have spent over three hours so far disabling, uninstalling, and changing settings that I do not want. For example, by default, essential folders like Documents and Desktop are in the OneDrive folder, so if you do not want to use OneDrive, you have to uninstall OneDrive, Unlink your system from OneDrive, and reassign those folders' locations back to their normal place, which ironically is called the default location. There is a multitude of similar annoyances in this version. I would expect this sort of thing if I'd purchased a Dell-built PC, but this is just the standard operating system. Sad times.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-11-13T11:56:54+00:00

    I get rid of that Autopilot.dll WIL. error by disabling Microsoft Account sign-in assistant service.

    Press the ‘Win + R’ key combination to open the Run command prompt

    1. In the prompt that shows, enter “services.msc”. This will open the Windows Services manager
    2. Scroll down and find the “Microsoft Account Sign-in Assistant service”. Right-click on it and further click on Properties
    3. In the subsequent dialog box, under the General tab, click on the Startup drop-down and select Disabled
    4. Save these changes by clicking on Ok > Apply

    RESTART

    credits to https://www.thewindowsclub.com/autopilot-dll-wil-error-was-reported-in-windows

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-11-17T19:53:29+00:00

    Like Migz-DH, I did a clean install and the error no longer occurred I used the same computer name, signed in with my Microsoft account, and installed the apps that were installed when I went from 21H2 to 22H2. I did that to see if I could spot what might have triggered the error.

    Due to my limited knowledge I did not find anything.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments