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. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2021-06-28T10:18:48+00:00

    I am totally confused now then.

    The machine I removed third party AV from has no WaasMedic running.  Actually, looking in the Services Waas Medic is reflected as STOPPED.

    I did not stop it.

    What the hell is this damned thing?

    Anyway, I am out o here.

    Thanks to everyone.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-06-28T06:17:42+00:00

    6-8 weeks ago, booted on the Sunday morning, attempted to open Task Manager from Task Bar so could catch WaasMedic running. Task Bar not responding, could not open TM, any apps, Start etc. Control/Alt/Delete brought up Task Manager, WaasMedic not running. Put away TM, control/alt/delete again, WM still not running, realised mouse working OK so could interact with TM. Couple of minutes later WM kicked in, another couple minutes later decided to stop. then forced a reboot.. Assumed, rightly or wrongly, WM was not causing issue with Task Bar not being responsive.

    WaasMedic than ran on Monday morning's boot which seemed fair enough, doing a catch-up. Since then, this weekly second run has been moving out each week from am boot to pm boot, next week moves on a day, back to am boot. last week had progressed to Wednesday pm boot, so, in theory this week will run Thursday am boot. Must admit, overall, each run might last a minute or so less duration, now might be 6 minutes each run instead of 8 - put this down to me cancelling the run of 6-8 weeks ago. So does a cancel trigger a second boot, cancelling each time triggers another, is this why some people reporting WM running each day.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-06-27T15:00:14+00:00

    Can't say if this is the root cause of this mess or not....

    I have an old desktop not used anymore that I started running to see if the cause could be rooted out.

    Bottom line, once I removed the antivirus software from that particular machine, the WAAS Medic was cut down to approx. 5 minute running time.

    BTW, I replaced that antivirus package with the windows 10 security apps just for some protection.

    Anyway, that solved the WAAS Medic problem on that machine.  Will continue to watch it before making changes to my other machines.

    Hope this helps everyone.

    Was this answer helpful?

    0 comments No comments