Many persistent errors in Event Viewer after Windows 11 build 22598.ni_release.220408-1503: "Autopilot.dll wil error was reported"

Question

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?

Answer 1

Unfortunately I have limited computer expertise. That being said; I snooped around and learned this was added to my system 10/16/2022. That’s about the time I updated from 21H2 to 22H2.

I found onecoreuap when I did a search in Windows system32 directory looking for onecoreuap.

When I click on properties; due to my limited knowledge and not understanding what I’m looking at, I noticed when I clicked on “Details” at the bottom it displays “Remove Properties and Personal Information”. Needless to say I didn’t click on it since I don’t know the consequences.

I don’t know if this information is of any value or means anything. Possibly someone more knowledgeable can sort it out.

Answer 2

Mine started when I upgraded from Win 10 21H2 to Win 10 22H2 on the 19th. I too think it is from that.

Answer 3

Mine started when I upgraded from Win 10 21H2 to Win 10 22H2 on the 19th. I too think it is from that.

No, it is not! Mine started at the beginning of August under W 10 21H2. So, it has nothing to do with the upgrade to 22H2, which was a minor one anyway.

Answer 4

Mine started when I upgraded from Win 10 21H2 to Win 10 22H2 on the 19th. I too think it is from that.

No, it is not! Mine started at the beginning of August under W 10 21H2. So, it has nothing to do with the upgrade to 22H2, which was a minor one anyway.

I concur. Mine started in August as well after a regular Windows update. I was on W11 21H2.

Answer 5

I'm based in UK so monthly 'Patch Tuesday' first thing on Wednesday morning. Wednesday 10th August, installed August updates as normal, restarted, error first recorded at that exact time, no prior records which I believe are held in event viewer history for 14 days. Still on 21H2 Windows 10, 22H2 only arrived as an option to install less than a week ago. Seems there is no pattern who is affected no matter what system running and seems no definitive time when first noticed. Touch wood, all I have the error log recordings, noticed none of the issues mentioned by others. This, no doubt, is something MS concocted to steal our personal info held on computer. Sort it out Microsoft.