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

.... 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)

Hi GhostSage:

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.

I haven't tried chris__74's suggestion yet, but if you want to see if this works then go to Windows Security | Device Security | Security Processor | Security Processor Details | Security Processor Troubleshooting and then click "Clear TPM". An alternate method is to enter tpm.msc in a Run dialog box (Windows key + R) to open the TPM Management Console shown below and click "Clear TPM ...".

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. Bitlocker is currently turned off on my Win 10 Pro v22H2 laptop and I have no idea what unexpected problems might arise if you reset your TPM module while Bitlocker is enabled.

For more information (and warnings) about clearing the TPM see the Microsoft Learn article Troubleshoot the TPM.

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. The Microsoft Learn article Troubleshoot the TPM notes that "Clearing the TPM resets it to an unowned state. After you clear the TPM, the Windows operating system will automatically re-initialize it and take ownership again."

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 * Dell Update for Windows Universal v4.7.1 * Macrium Reflect Free v8.0.7279 * Microsoft Office Home and Business 2019 (Version 2301 / Build 16026.20146) Click-to-Run

Hi everybody,

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:

error about WIL autopilot appears several times, even every minutes in some part of the day, the dcom service then also got errors and after 3 restart it makes the pc to reboot...

dump file is not created due to other errors, therefore is impossible to check it.. it's really a mess of errors!

what i'm most worried about is the laptop is restarting up to 10-15 times per day, would this damage the hardware too??

it's really incredible this problem is affecting so many users and still not having a patch to fix it... i'm seriously considering to exit the insider program.

hope to get a reply and solution soon

I use Intel as well and I have the 0x80070491 and it has been mentioned in the replys. I doubt MS has this as a priority but maybe they do as who knows as they seem to not communicate with users. I am sure they know about this as many users are complaining about it. You are correct that turning off the logging is only a band aid over a wound that will not heal but it does keep the errors from constantly filling up the log and overwriting all the time. Now what I did on my Omen back in November was I did an in place upgrade of my Win10 https://www.microsoft.com/en-us/software-download/windows10/ on my Omen for other issues I was having like a cumulative update failing to install which solved that and other things so maybe it solved this Error...... I do not know but I thought I would mention it. A in place upgrade may solve the problems you are having now. It was somewhat time consuming and there were times when the upgrade was running that I thought it was stuck but I had the patience to wait and it went to completion. It did not touch my settings or Apps I had installed. I am thinking about doing it with my wife's HP Envy laptop but she is not experiencing any problems so far because of that error since I turned off that section of the Event Log where the events are being recorded but if she does start getting problems I will try it. Just be aware that if you try an in place upgrade just be patient and let it do its thing and run to completion. You can file a bug report in the Feedback Hub about the error. The more they get the quicker they will act hopefully. Good luck my friend and if I hear anything I will let you know.

Respectfully,

Hello my name is Don and a user like yourself. I want to let you know that you are not the only one with this problem. The problem you are experiencing is a known problem to many users and there has been a few discussion threads about this very subject. I will point you to several of these discussion for you to read the comments in them. I want to remind you this problem was created by MS and only they can fix it. I would caution against trying different ways to solve this as they may cause you more problems in the long run. Personally I am not seeing this Error on my HP Omen desktop but I do see these Errors on my wife's HP Envy laptop. What I did do is turn off the logging of these errors in the Event Viewer on her laptop as that is covered about how to do that in the discussions. The discussions are as follows:

https://answers.microsoft.com/en-us/windows/forum/all/many-persistent-errors-in-event-viewer-after/c218ee04-89a5-4ce2-805d-565b8d1b1744 and https://answers.microsoft.com/en-us/windows/forum/all/autopilotdll-wil-error/9432c664-8a28-4aa9-8655-4a8db6508c17

Respectfully,