AutoPilot.dll WIL error was reported Event 1010 - Causes Crashing/Issues Any fix?

Maybe if enough dissatisfied customers use the Feedback hub, Microslop might listen. Disabling the sign-in service is not a work around since it also prevents MS account login according to the service info.

... User chris__74 posted today (en français) in Pekaaa1's Autopilot.dll WIL Error that a reset of your TPM module should stop these ModernDeployment-Diagnostics-Provider / Autopilot.dll WIL errors, and a few users have confirmed this workaround was successful. ...

WARNING: If you use Bitlocker Disk Encryption and want to reset your TPM module I would advise that you suspend or disable Bitlocker first (e.g., at Control Panel | Security | Bitlocker Drive Encryption for Professional editions of Windows) and ensure that you have your 48-digit Bitlocker recovery key on hand before starting. ...

...Before proceeding you might also want to read some recent feedback on pages 5 an 6 of Pekaaa1's thread. For example, MisterFlamp reported <here> in Pekaaa1's thread that a TMP reset stopped their Autopilot.dll WIL errors but that they were required to enter their Microsoft password and login PIN after the reset...

Hi GhostSage:

I finally tried clearing my TPM and am happy to report that my ModernDeployment-Diagnostics-Provider / Autopilot.dll WIL errors have stopped. I'll monitor my Event Viewer for a few more days and will post back if they start up again.

I cleared my TPM just after 8:00 AM on 02-Mar-2023 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 I've gone an entire day (and several system restarts and power off / power on cycles) without seeing any new Autopilot.dll WIL errors logged in my Event Viewer.

From my Win 10 Pro v22H2 Event Viewer (Application and Service Logs | Microsoft | Windows | ModernDeployment-Diagnostics-Provider | ManagementService) which shows my last error was logged at 8:00:36 AM on 02-Mar-2023. Recall that my Event Viewer was logging about 80 of these errors every day before my TPM was cleared.

If anyone wants to try clearing their TPM please read the warnings in the MS support article Troubleshoot the TPM first. 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 I did have to reset my Windows Hello PIN to sign into my device, which turned out to be a bit more complicated than I expected. That was partially my own 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. After I cleared my TPM and my system re-started I was prompted to log in to my Microsoft Account to reset my Windows Hello PIN, but couldn't open my email program to retrieve the verification code because I was stuck at the login screen. I was eventually able read my email and retrieve the verification code to complete the reset of my Windows Hello PIN and all is well now.

If you use a Windows Hello PIN to sign in to Windows and/or unlock your lock screen you can temporarily remove it at Start | Settings | Accounts | Sign-in Options | Windows Hello PIN as instructed in the MS support article Windows Sign-in Options and Account Protection before clearing your TPM and then create a new PIN when you're finished. If you don't want to do that and have 2FA set up for your Microsoft account just make sure that you will be able to receive your 6-digit verification code if you get stuck at your Windows login (e.g., from a second device like another computer or cell phone).

As an extra precaution I created a full disk image of my hard drive using Macrium Reflect Free before clearing my TPM just in case I needed to perform an emergency recovery, but it wasn't needed and my computer hasn't displayed any new problems since my TPM was cleared.

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

I'm observing that the autopilot errors have multiple root causes.

In my case, I confirmed that somehow the TPM data was corrupted and generated the useless error continually. I call the error useless in that the data provided misleads and is ambiguous. Referring to a specific line of code in a module is useless for the user, unless they have insight into Microslop's code.

I encountered this error on two of my PCs, both of which have a TPM (HW module that stores encrypted data). The error was resolved by clearing the TPM.

I observed these scenarios:

• One PC with a TPM is running Winders 11.
• One PC with a TPM is running Winders 10.
• Another PC without a TPM running Winders 11 never exhibited the multiple autopilot errors. I know a TPM is a HW requirement for Winders 11, but that can be worked around via a flashing tool. I wanted to test Winders 11 on my older "scratch" PC.

Based on this data, I concluded that one of the root causes is related to TPM corruption, which I believe occurred during one of the Windows updates to BOTH 10 & 11. I do not know which update caused this issue.

Hi GhostSage:

Thanks for posting about this.

I’m also seeing these ModernDeployment-Diagnostics-Provider errors (Description: "Autopilot.dll WIL error was reported"; Event ID = 1010) logged in my Win 10 Pro v22H2 Event Viewer at Applications and Services Logs | Microsoft | Windows | ModernDeployment-Diagnostics-Provider | ManagementService. I believe they started on 06-Dec-2022, which happens to be the same day I updated my Win 10 Pro OS from v21H2 (Build 19044.2251) to v22H2 (Build 19045.2251). I am currently seeing at least 40 or 50 of these errors logged every day.

I've found multiple threads about these recent errors in a variety of Win 10 and Win 11 forums, and the 28-Aug-2022 Appauls.com article Fix: Autopilot.dll WIL Error Was Reported on Windows suggests this error could be associated with the Microsoft Account Sign-in Assistant service. These errors don't seem to be causing any BSODs or other serious issues on my laptop so I'm not going to try disabling that service as suggested in that article, since the author notes that disabling this service will prevent you from using certain Windows features or programs like the Outlook Calendar widget.

I upvoted Ludvig C's Microsoft Feedback Hub problem report Event 1010, ModernDeployment-Diagnostics-Provider and added my own comments there today using my Feedback Hub app but don't know if anyone at Microsoft is actually doing anything about this issue.

Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.2486 * Firefox v109.0.0 * Microsoft Defender v4.18.2211.5-1.1.19900.2 * Malwarebytes Premium v4.5.20.230-1.0.1868 * Macrium Reflect Free v8.0.7279 * Microsoft Office Home and Business 2019 (Version 2212 / Build 15928.20216)

.... i was not experiencing such issue since 2 weeks ago, when I switched on Cortana service to let my wife use the speech to text function in MS Word...

The problem is not just the WIL autopilot.dll error, but the laptop is rebooting every dya several times! the blue screen is too fast to catch the error mentioned but i can see the errors in the event log...

Hi Luca_Onga:

Cortana is disabled on my Win 10 Pro v22H2 laptop, and in the past 7 days over 95% (488/509) of the errors logged in my Event Viewer have been due to the ModernDeployment-Diagnostics-Provider / Autopilot.dll WIL errors being discussed in this thread. Most of my other errors are due to a FirmwareTPM.exe application error (Event ID 1000) caused by a known bug in my Dell SupportAssist and Dell Update utilities - see my 18-Dec-2022 thread <here> in the Dell community. These constant ModernDeployment-Diagnostics-Provider / Autopilot.dll WIL errors are a nuisance but as far as I know they have not caused any Blue Screen stop errors or obvious problems on my Win 10 laptop.

If you haven't already done so you should run the DISM command Dism /Online /Cleanup-Image /CheckHealth from an elevated command prompt with Administrator rights as instructed in the ghacks.net article Use DISM to Fix Issues SFC Can't. If that DISM scan doesn't find any issues with your Windows component store then run the System File Checker command sfc /scannow to look for and repair any damaged or missing Windows system files. You can also run the Windows Update Troubleshooter built in to Win 10 / Win 11 to see if it can fix your WindowsUpdateAgent (Event ID 20) errors.

I'm guessing your VolMgr (Event ID 161 - dump file creation failed) and critical Kernel-Power (Event ID 41 - system has re-booted without a clean shutdown) errors are logged at the same time as your Blue Screen stop errors and system restarts. These types of errors are often associated with corrupted or out-of date firmware or hardware drivers, but in rare instances they can also be caused by a failing power supply. The 25-May-2022 MakeUseOf article How to Fix a Windows 10 Kernel Power Error in 5 Easy Steps suggests disabling the Fast Startup power option and running ChkDsk and SFC scans, but if that doesn't stop your unexpected system restarts I'd suggest you leave the Windows Insider Program and post in BleepingComputer's Windows Crashes and Blue Screen of Death (BSOD) Help and Support board (see their posting guidelines <here>) if your Blue Screen stop errors persist.

Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.2486 * Firefox v109.0.1 * Microsoft Defender v4.18.2211.5-1.1.19900.2 * Malwarebytes Premium v4.5.21.231-1.0.1890 * Macrium Reflect Free v8.0.7279 * Microsoft Office Home and Business 2019 (Version 2301 / Build 16026.20146)