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
    2023-02-09T23:37:44+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.

    This was a no biggie step...

    Somehow Microslop managed to corrupt the TPM data, which resulted in a flurry of NULL message errors. Nice error message - not.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-02-10T15:29:12+00:00

    Nope. Resetting the TPM did nothing for me. Still getting oodles of these autopilot errors.

    I didn't really expect resetting the TPM to work since entire, clean Windows installs didn't help either. But, it was worth a try.

    For most of us, I assume it's a problem with 22H2 (Windows 10 and 11) and not with any configuration on our side.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-02-10T15:49:45+00:00

    Where is the elephant in the room at this time?

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Anonymous
    2023-02-15T14:08:06+00:00

    It looks like I was wrong when I said resetting the TPM didn't fix this. I just looked at my Event log and all my autopilot errors have stopped. But, for some reason, they stopped the day AFTER I reset my TPM. Odd. But, I guess I'd suggest others do the same thing (make sure you turn off Bitlocker first if you have it on).

    Anyway, thanks.

    EDIT: According to this site, I posted that this didn't work on 02/10/2023 7:29 AM and, looking at my event log, I'm pretty sure I'd reset my TPM about an hour earlier. Between the change and my post, I'd done multiple reboots (even into Safe Mode). Yet, the autopilot errors continued until about 9:30PM when I'm pretty sure I shut down my computer for the night (85 instances of autopilot errors that day). Since then, none. I don't see any updates having taken place in my Windows Update history, so, again, it looks like resetting the TPM was what fixed it. But, why it took all day, through multiple reboots, I don't know.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments