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. lmacri 2,505 Reputation points
    2023-03-03T14:57:32+00:00

    Looks like the fix is to reset the TPM!! Woo-hoo!! I wasn't using bitlocker, but understand that more complexities are involved.

    I reset it via typing "tpm.msc" in the search area to the right of the start menu symbol.

    You are then forced to re-enter your Microslop password again and afterwards re-entering your PIN...

    Hi Pekaaa1:

    I finally tried clearing my TPM as instructed in the MS support article Troubleshoot the TPM (i.e., Windows Defender Security Center | Device Security | Security Processor Details | Security Processor Troubleshooting | Clear TPM) and this appears to have stopped my ModernDeployment-Diagnostics-Provider / Autopilot.dll WIL errors. See my 03-Mar-2023 post on page 2 of in SageGhost's thread AutoPilot.dll WIL error was reported Event 1010 - Causes Crashing/Issues Any fix? for further details. I'll monitor my Event Viewer for a few more days and will post back if the errors start up again.

    I do not have BitLocker disk encryption enabled on my Win 10 Pro v22H2 laptop so I did not need my 48-digit BitLocker encryption key to re-boot my machine, but like MisterFlamp, I did have to reset my Windows Hello PIN to sign into my device. That didn't go as smoothly as I expected, but that was partly my fault because I use two-factor authorization (2FA) to protect my Microsoft Account from unauthorized changes and have 2FA set up so that the 6-digit verification code is sent to a secondary e-mail address instead of my phone number (it's hard to read your emails when you're stuck on your Windows login screen :-)). I was eventually able to retrieve my verification code and reset my Windows Hello PIN (see my comments in SageGhost's thread) and all is well now.

    Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.2604 * Firefox v110.0.1 * Microsoft Defender v4.18.2301.6-1.1.200000.2 * Malwarebytes Premium v4.5.23.241-1.0.1927 * Macrium Reflect Free v8.0.7279 * Microsoft Office Home and Business 2019 (Version 2301 / Build 16026.20200) Click-to-Run

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-03-13T11:34:29+00:00

    I HAVE THIS ERROR TOO

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-03-15T19:52:21+00:00

    I tried this solution, no luck. 😭

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-03-22T06:56:32+00:00

    ChatGPT gave me a solution that worked for me and I didn't lose any data... Was very simple..

    Remove and Re-install Autopilot..

    1. Open PowerShell as Administrator
    2. Run this line of code:
      Get-AppxPackage Microsoft.WindowsAutopilot | Remove-AppxPackage
    3. Now run this line of code:

    Get-AppxPackage -allusers Microsoft.WindowsAutopilot | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

    The end..

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-03-22T15:08:53+00:00

    Didn't work for me. Commands executed without error but error messages persist.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments