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

Anonymous
2022-12-17T18:01:05+00:00

Hello everyone.

I've looked around the net to figure out what's going on and try to fix the issue, but to no avail. There's suggestions where it's mentioned to disable "Microsoft Account Sign-in Assistant Service", I don't want to go that route as I won't be able to sign in for services. Another suggestion is to update, and my PC is fully up to date. Another suggestion was fixing Windows System Image and I've tried that and it's still happening.

OS: Windows 10 Home 64 bit (10.0, Build 19045) This is the latest build

My pc has been having some issues where sometimes the screen goes blank. Basically it looks like when you hit control alt delete to bring up the task manager/lock/sign out/switch user screen but it's blank. There's times where the icons on the task bar disappear as well as desktop icons and the pc will lock up where I can't do anything, not access the start menu, not access the process manager, nothing at all. This has been happening a lot so I pulled up my event log to see what's going on and the time seems to be linked to the Autopilot error mentioned in the title of the thread. This event happened 3 times today. Two times back to back at 12/17/2022 11:52:28 AM and then once more at 12/17/2022 11:53:57 AM

UPDATE: It's not happening every time the error shows as it's happened a decent amount of times since the last time I've mentioned.

The details of the event are as follows

General tab

Log Name: Microsoft-Windows-ModernDeployment-Diagnostics-Provider/ManagementService

Source: Microsoft-Windows-ModernDeployment-Diagnostics-Provider

Date: 12/17/2022 11:52:28 AM

Event ID: 1010 Task

Category: None

Level: Error

Keywords:

User: -----------

Computer: ------------

Description: Autopilot.dll WIL error was reported.

HRESULT: 0x80070491 File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 191

Message: NULL

XML View

  • <Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">
  • <System> <Provider Name="Microsoft-Windows-ModernDeployment-Diagnostics-Provider" Guid="{bab3ad92-fb96-5902-450b-b8421bdec7bd}" /><EventID>1010</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x1000000000000000</Keywords><TimeCreated SystemTime="2022-12-17T16:52:28.1338145Z" /><EventRecordID>7719</EventRecordID><Correlation /><Execution ProcessID="6064" ThreadID="19168" /><Channel>Microsoft-Windows-ModernDeployment-Diagnostics-Provider/ManagementService</Channel><Computer>-----------------</Computer><Security UserID="S-1-5-21-3571332062-3799675618-396578140-1002" /></System>
  • <EventData> <Data Name="HRESULT">0x80070491</Data><Data Name="File">onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp</Data><Data Name="Line">191</Data><Data Name="Message">NULL</Data></EventData> </Event>
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

24 answers

Sort by: Most helpful
  1. lmacri 2,505 Reputation points
    2023-11-03T21:14:18+00:00

    Hi OmarCayasso :

    The only way I was able to stop these ModernDeployment-Diagnostics-Provider / Autopilot.dll WIL (Event ID 1010) errors on my Win 10 system was to clear my TPM, but a few users have reported this workaround didn't stop their errors.

    If you want to try clearing your TPM please read my 03-Mar-2023 post <here> on page 2 of this thread about a minor glitch I ran into with the Windows Hello PIN number I use to log into Windows. However, I could have easily avoided this glitch if I had temporarily removed my Windows Hello PIN 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 my TPM and then created a new PIN after my TPM was cleared.

    Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.3570 * Firefox v119.0.0 * Microsoft Defender v4.18.23090.2008-1.1.23090.2007 * Malwarebytes Premium v4.6.5.293-1.0.2181 * Macrium Reflect Free v8.0.7690 * MS Office Home and Business 2019 Version 2903 / Build 16287.20166 Click-to-Run

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-07-22T15:11:58+00:00

    It can cause application's to crash cause in idle it can give a spike in performance draw and when you check logviewer you might see multiple within short amount of time. Than it is just enough to make other applications crash.

    Window's obviously is incompetent of fixing it and to bring up the moral to feel care for our "performance", wich they obviously lack... the care.

    We have to work a way around now... we, the client's, the user's... we have to develop and fiddle half microsoft to get it sort of to work the way you want.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-02-17T13:07:27+00:00

    what about bitlock? well it break it?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-02-16T20:52:25+00:00

    i am getting this too, Im not good with computers and it will not stop so i disabled it ( even though people say thats a bad idea because youre unable to login ) have you found a way to fix it? because i haven't. I worries me that my pc will forever be like this

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-02-10T16:14:03+00:00

    I reset the TPM and enabled the ModernDeployment-Diagnostics-Provider again. I was then able to connect to my phone as before, but the event log is telling me that Autopilot.dll is faulting again like crazy. 56 times in the last half hour, so far.

    Can spontaneous reboots be far ahead? I hope the investigation into the real source of the problem continues.

    Was this answer helpful?

    0 comments No comments