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?

I like talking with people with the same problem, But I made some bad choices of words, I never thought the process was necessary, I just over look what I type and I see I didn't add that Microsoft see it as a necessary process, that why there not going to add a stop button to it. They think WaaSMedic will be over in no time, and that the process won't do anything to the OS (meaning destructive or something bad, you know what I mean).

My bad Again. Yes I do understand it but, it seems I can't get the right choices of words out my head. As before I said "essential" and I said "necessary" I couldn't think of a word that comes close to needed and not needed. It seems I won't be a help to this "I forgot the word for this talk" Thread. I keep reading like allows I only respond if a mistake is made, if I found a solution (Most likely not happening), or if some needs me for something. Intel then I hope a fix can be found, 

And again I feel like I said something that someone didn't like, idk if I did, but I hope everyone is doing well and peace. 

edit: I hope you didn't take "that why there not going to add a stop button to it" the wrong way, I'm not going to explain why I put this here (I didn't know what to say that why I put it there), but I meant something close to, change.

For anyone wondering what I mean when I said "they not going to do jack" Simple

From a post about WaaSMedic in the past Kristen_S said. 

Kristen_S

Replied on March 11, 2021

Hello Tooney,

By design, WaasMedic is only going to work if it finds a problem with Windows Update. When the task is complete, there is no more spike in usage of CPU/HDD.

All recorded reports of issues with WaasMedic are about the usage with sporadic and intermittent issues. Some reports are short-term measured in minutes, some are longer, yet none fail to resolve. There are reports from 20H1, 20H2, and 1909, meaning this is not something newly introduced.

*You can think of it this way: If you launched a Video Editing app and then started a very CPU intensive action with that application and you saw your CPU and HDD being heavily utilized, you would not claim the program is broken and something is wrong. You would expect it because you initiated it. And it will go away when that app is done doing what you asked it to do.****The difference here is Windows started this task because it detected something that needs fixing.***It is serving its purpose, and it will end when it fixes are complete.

I hope this gives clarification on the topic.

Kristen S.

Forum Owner

Don't worry because, they also said.

Hi everyone,

We got to involvePaulin the original threadWaasMedic Agent Exe stopping me from working - Microsoft Community, and he'd like to start collecting high CPU or high disk usage cases of the WaasMedic agent throughFeedback Hub entry, and Feedback URLs on that thread.

We will continue to focus only in that thread to better support this issue.

Thanks,

Kristen S.

Forum Owner

Not that helpful was it. Unless all the Data that was being collected was sent to Microsoft and they was looking into a solution and still couldn't find one then, I take back what I said my bad, but if they not looking into a fix for it then, I don't think there be a real solution from Microsoft.

Thanks for the feed back, I take it down if it irrelevant

And also, MarcHoppe I like talking to you. You seem like at least 30 year old computer tech.

You seem to look at WaaSMedic Post's and can't seem to see a real solution to it.

and is waiting for a FIX from Microsoft. When you know damn well they not going to do jack, since it some what essential necessary for windows OS. I'm hoping for a fix too, so I don't get blamed for making the OS slow when it's just WaaSMedic in the background.