WaasMedic Agent Exe stopping me from working

Again you're just not getting the problem. The problem is not that WaasMedic is running it's the fact that it's running for so long and so often. On my i7 8700K system it ran for over 13 minutes at or near 100% disk. Sometimes at over 8 megabytes per second. Even if we say that it averages 2 MB/sec for 13 minutes that's over 1.5 GIGS of disk activity. For what ? Then today it started to run again and after 3 minutes I simply did an End Task but had to do a restart to keep the rest of Winbloats tasks from grinding away at my hard drive. After the restart everything was fine. That system has no third party AV, no third party browser and only a handful of audio apps installed and it needs to run at maximum efficiency in order not to get under runs and audio degradation. People who only use their computers to surf the net or check e-mails may not even notice the problem but those of us who do system intensive work like audio or video production do notice. 

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.

I advise everybody NOT to follow those instructions. He doesn't understand the problem so his "advice" is not only irrelevant it's potentially dangerous. 

No one really wants a workaround we want a FIX from Microsoft. But for now the simplest workaround is to simply End Task for WaasMedic in the Task Manager.

It appears the BEST solution is to simply switch to Linux since M$ doesn't seem to care their data mining system err I mean operating system is a Pig.