WaasMedic Agent Exe stopping me from working

Having looked a LOT at the event logs on my systems, and seeing various "odd" failures, I have come to the (possibly incorrect) conclusion that 3 Microsoft internal "remediation" and related services are fighting each other, getting in the way of each other, and creating "catch 22" conflicts.

I have noticed that the event ID 2, showing that "Session "Microsoft.Windows.Remediation" failed to start with the following error: 0xC0000035" most likely caused by trying to set up or open 2 files with the same name (the error is an "object name collision"), but it DOES seem to get going an create a log file (this function lives in C:\program files\rempl controlled by the "sedlaucher.exe" and the SED is short for "sediment" -- nice).

Now the "WaasMedic" service appears to be ANOTHER type of "remediation" service, but most likely "cloud" based. However, it seems to be linked to "settings" as these are checked, and again, looking at event logs, I see LOTS of failures with "settingsync" - again looks to be cloud based.

If there is a lack of defensive code to check for unexpected errors, bad API calls, or bad responses from other code objects and improper status returns, or issues out on the "cloud" server agents, HOW can this stuff possibly work well or cohesively?

Many users are looking for an answer from Microsoft on these issues, how can we tell if they are looking?

TD47 - I have the same error about Remediation but large majority happen with-in 2 - 3 minutes of pressing start button to boot. There are various other errors also showing but, once again, within this 2-3 minutes. so I assume, at start-up it has to load by priority and first attempt to load 'Remediation' is of lower priority. In my case, it is a one-off entry so it must load 2nd attempt a few minutes later when the computer is fully up & running otherwise there would be a second fail a short time later. Have a look in Event Viewer, Information, section 19, notated Windows Update. Windows push down all manner of updates on various apps etc in the background unannounced so updating is a continuous procedure - not only once a month. Whether some of the daily updates are bad or not - who knows.

I got this today. It's the second boot since the Waas scheduled run on Sunday. Notice the "Package for Rollup Fix". There were dozens of entries and it was only reading not writing for the majority of the time. So what are you "fixing' M$ ? Over and Over and Over ? 

If you look in Windows>Servicing>LCU you'll find the "Package for Rollup Fix" folders.  There are two folders on this system, one from 3-11-21 and one from 04-13-21 each one has over 46,000 items in it and each are over 600MB in size. Like I said Winbloats 10 is a Pig of an operating system.