I ran the System File Checker today and it actually did this to me as well and immediately started giving the errors again. I was able to delete the new file after disabling the Sign In Assistant and then I was able to turn it back on but obviously if your computer is going to do that every time it's not a great solution 😑 This is just an extremely frustrating issue!
Many persistent errors in Event Viewer after Windows 11 build 22598.ni_release.220408-1503: "Autopilot.dll wil error was reported"
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.
338 answers
Sort by: Most helpful
-
Anonymous
2023-02-24T18:37:47+00:00 -
Anonymous
2023-02-26T19:30:56+00:00 The .bak solution worked perfectly for me - after months of debilitating mini freezes. Thank you M3800! Not a single related error in Event Viewer so far and all related applications sync normally. Everything continues to work after a reboot. NOTE I did use the .bak extension, not .bkp as used in one post.
-
Anonymous
2023-02-27T11:06:08+00:00 I have Legion 5 15ARH05H laptop, with AMD Ryzen 5 4600H, Windows 11 22H2. I had exactly the same problem in my Event Viewer:
Autopilot.dll WIL error was reported.
HRESULT: 0x80070491
File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 128
Message: NULL
I was searching for answers about this issue and found this Microsoft article: https://learn.microsoft.com/en-us/mem/autopilot/known-issues
I don't know why i can't paste image there but whatever, i will just copy-paste text from that article:
"TPM attestation isn't working on AMD platforms with ASP fTPMTPM attestation for AMD platforms with ASP firmware TPM may fail with error code 0x80070490 on Windows 10 and Windows 11 systems. There's currently no update available to resolve this issue.**"
My error code was 0x80070491, but still solution i want to tell you about worked for me without any problems (atleast there is no more new errors in Event Viewer)
! I'm not sure but I heard on some forum that disabling TPM may do something bad to bitlocker if you use it, but i dont use bitlocker, do this on your own risk !
Firstly i checked if my TPM was enabled by searching for tpm.msc (Trusted Platform Module (TPM) Management on Local Computer) in windows search and opening it. I saw there that TPM was enabled on my machine.
After that i restarted my pc, opened bios, advanced settings, and is security tab i found AMD Platform Security Processor which i disabled. I booted into windows, it offered me to change PIN of my account, i set it to PIN i had before disabling TPM and after that logged into my machine without any problem. I opened tpm.msc and saw message "Compatible TPM cannot be found", which means that i succesfully disabled TPM. For now there is no more Autopilot.dll errors in Event Viewer. -
Anonymous
2023-03-02T19:26:39+00:00 be aware that TPM was a requirement for running windows 11. Much of the work on Win11 was to harden the platform from malware. This is a part of that. Think of what you are doing as driving a car without your seatbelt, you may go many miles without a problem, then one day your body is smashing through a windshield.
-
Anonymous
2023-03-02T20:29:39+00:00 I hardly see how increasing security is resolved by a choice between a persistent error and turning off biometrics and disabling the sign-in assistant.