WaasMedic Agent Exe stopping me from working

Anonymous
2021-01-02T19:26:13+00:00

My computer slowed to a crawl. I cannot work. I checked task manager and saw a process waas Medic agent exe is the culprit. It is using 2.8 mb of memory and 1.2 mbs of disk usage.

I understand this is a Microsoft process. What I don't understand is what give Microsoft the right to take over my computer whenever it wants to and stop me from working.

How do I stop this?

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2021-03-16T19:13:13+00:00

Update (5/5/21) - Editing with some additional details.

Can some of you reporting high CPU or high disk usage of the WaasMedic agent create a Feedback Hub entry for me and share the Feedback URL on this thread?

The most important part would be the 'Recreate my Problem' recording while you see the high resource usage in Task Manager.

Image

I want to promote some of these Feedback entries for investigation.

Updates:

Thank you for those who have been trying to file feedback. In some cases the system performance has prevented the use of Recreate my problem.

The Feedback is still useful without the recording, I will still raise those entries.

It is also useful if the Feedback is done shortly after the system is no longer experiencing the high disk usage, I will be calling out those entries as well.

Finally, I was not clear about the best Category and Sub Category selections. Please use Category: Install and update Sub Category: Downloading, installing, and configuring Windows Updates

Thanks,

Paul...

Was this answer helpful?

70+ people found this answer helpful.
0 comments No comments

552 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-08-29T14:44:02+00:00

    Hey Microsoft here's some Telemetry for you. This is on a system with an SSD and only two third party programs installed. No third party AV. There is NOTHING else running at the time of the screenshot except Windows and the Task Manger. 81% CPU doing NOTHING. Now I get to go watch Winblows 10 grind away at 100% on my most powerful computer's hard drive for over 10 minutes. FIX....THIS....PROBLEM.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-02-28T13:29:25+00:00

    See there has been a lot of 'I have same question". This morning same as normal, usually leave a 3-4 minutes from pressing ON button before attempting to open anything. Then normally 2-3 minutes of disc activity. This morning, just out of curiosity, checked Task Manager immediately after this 3 minutes- WAAS taking 6% CPU & up to 40% max disc. Process finished after 2-3 minutes. The other day WAAS was running for about 10 minutes, there was a small drop in performance - just about when an auto update for an app is installing. That was one of the times when opening Update & Security showed an ERROR on the next or following reboot, no error shown on auto WUD run first boot of day, even doing a manual check. First noticed Error on WUD's in November last year, had that error about another 4 times - always with mid term releases. I assume background updates to Health Tools is MS attempts to cure issue, so far failing.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-02-28T09:16:27+00:00

    I found this solution, which worked for me so far
    https://appuals.com/what-is-waasmedic-and-how-to-disable-it-and-fix-it/

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-02-26T07:35:39+00:00

    Bit of an update. Looking thru' records, 'Update Health Tools' was updated for me on 22nd January 2021 to Version 2.70.0.0 & again on 20th February 2021 to 2.75.0.0. Both came through unannounced - just appeared in update history. Does this infer Microsoft are trying to solve a known issue and have failed ? I am still on version 2004 Home.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments