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

Another couple of months and we shall be at the first anniversary of this thread being posted, still no actual acknowledgment from MS of problem & solving. People here are reporting MS are aware and working on it - surely time now that it should have been resolved. If they are taking this long, no confidence in anything they do as this is of their own making, why should us users have to suffer the consequences!. Conclusion, as always, is this had been intentionally released for some ulterior motive, farming private info etc. again.

I am quite sure MS knows about these errors being generated and they are probably working and trying to find a fix so as not to harm user's computers when it is deployed. When you say suffer the consequences do you mean the number of errors being generated? I have explained how to remove those errors from the event viewer and stop them from constantly filling up the log and being overwritten. I said it is only a band-aid solution and not a fix. I believe the other consequences that you may be referring to may well be caused by other problems in a user's computer and not related to these errors. My wife's HP Envy never experienced any system problems when there were hundreds of these errors being generated on her laptop per day nor after I turned off the log for these errors. When MS announces a fix and deploys an update or instruction on how to fix the errors then I will enable the log for these events and see but right now I am not about to chase rabbits down holes and try this that or the other solutions and possibly damage her laptop in the long run. You said, "Conclusion, as always, is this had been intentionally released for some ulterior motive, farming private info etc. again." That is nothing but a conspiracy theory.

Respectfully

Another couple of months and we shall be at the first anniversary of this thread being posted, still no actual acknowledgment from MS of problem & solving. People here are reporting MS are aware and working on it - surely time now that it should have been resolved. If they are taking this long, no confidence in anything they do as this is of their own making, why should us users have to suffer the consequences!. Conclusion, as always, is this had been intentionally released for some ulterior motive, farming private info etc. again.

be aware that TPM was a requirement for running windows 11. Much of the work on Win11 was to harden the platform from malware. This is a part of that. Think of what you are doing as driving a car without your seatbelt, you may go many miles without a problem, then one day your body is smashing through a windshield.

I agree with you James. I have been following this discussion and others about this since the beginning. I have an Omen Desktop that does not have this problem but my wife's HP Envy laptop does. This problem was created by MS and only they can fix it. I would caution users against jumping down different rabbit holes and trying different ways to solve this or following other solutions from other users as they may cause you more problems in the long run. My wife's laptop never experienced freezing or Blue Screens or boot problems or anything else except these errors. The best thing to do at this point is to disable the part of the Event Log where the errors reported so the log will not fill up and keep overwriting. Within the Event Viewer, navigate down the logs on the left hand pane until you reach Applications and Service Logs then select Microsoft > Windows > ModernDeployment-Diagnostics-Provider > ManagementService. There you need to right click on the ManagementService log and select clear log and then select disable. This will clear all errors and prevent other errors from being logged. This is "clearly" not a fix but only band-aid solution to keep so many of these errors from being logged. MS knows about this problem because of the many discussions here and the number of complaints in the Feedback Hub. The only thing we can do is wait for MS to come up with a solution.

Respectfully

I hardly see how increasing security is resolved by a choice between a persistent error and turning off biometrics and disabling the sign-in assistant.

be aware that TPM was a requirement for running windows 11. Much of the work on Win11 was to harden the platform from malware. This is a part of that. Think of what you are doing as driving a car without your seatbelt, you may go many miles without a problem, then one day your body is smashing through a windshield.