But hey with 4 days’ notice they recently informed their Office 365 annual subscriptions are increasing.
Starting to think Linux might be the way to go…….
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
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.
But hey with 4 days’ notice they recently informed their Office 365 annual subscriptions are increasing.
Starting to think Linux might be the way to go…….
This is happening to me too, I discovered it when I was investigating why my PC had been freezing more and more lately. Event viewer says I've had 1522 errors in the past 7 days and 1334 of them have been "Autopilot.dll WIL error was reported.". I disabled Microsoft Account Sign-In Assistant Service and the errors stopped, but that's not a solution for me because I need to be able to sign in to do my job. Amazing that we're coming up on the 1 year anniversary of this thread.
I still get the errors also hundreds per day but strangely, its not crashing my PC anymore.
Autopilot.dll WIL error was reported.
HRESULT: 0x80070491
File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 128
Message: NULL
Same one, hundreds of times per day. I've run SFC, DISM, i deleted autopilot.dll and reinstalled it with a fresh one. I registered the fresh one. I remounted the image. Ive done everything I can possibly think of besides registry edits.
If anyone knows which registry edit to make or where to begin looking please update. Thanks for everyone who has tried to solve this so far, hopefully a solution is found soon because this is getting ridiculous.
Ahh fair enought; but still, there are thousands with the same issue and all have unique PC configuration of hardware.
So replacing a MB or CPU wouldn't be viable. Many have tried a full Windows reset and still get the issue.
MS really needs to get a handle on this software conflict issue and release a fix!!