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

552 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-05-04T02:34:47+00:00

    @MichaelIrons - as you and @MarcHoppe have been providing some really good feedback on here, as you have several systems, I wanted to ask what you gut-feel was about what update caused this.

    I see that 19041.928 is KB5001330, 19041.867 is KB5000802 and 19041.662 is KB4586853.

    All of those contain 64-bit WaasMedic Rollup fixes.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-04T02:24:57+00:00

    @MichaelIrons - I totally agree with you about Windows Search. I gave up on it years ago, to find my "stuff" - I have used the excellent AgentRansack for years, and never looked back. I used to find that the "search Indexer" would  take over, rather like the WaasMedic does now, as shown by the debacle on here.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-05-03T18:34:01+00:00

    Yes you can right click on WaasMedic in the Task Manager and select "End Task" and that will shut it down for the time being. I've done that on one system and it did not run at the next boot but even if it did we can just End Task again. I'm going to do that next Sunday and see what happens.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-05-03T17:16:10+00:00

    SMJM. All contributors to this forum have been experiencing this problem to various degrees since the beginning of the year so strange it has just started, do you have new computer, updated to Windows 10 etc. or any other changes? As standard, Microsoft have included this as a scheduled task to run every 7 days on a Sunday. If you happen not to boot on a Sunday will run on next boot. There also appears another running of WaasMedic that seems to happen a day or two after downloading & installing updates. If you open Computer Management>Task Scheduler>Library>Microsoft>Windows>WaaSMedic you should see that it is scheduled to run every 7 days (7.00:00:00) with start time 03:00 (for people up early), also shown last & next running times. Like a lot of MS items, there seems 2 of the apparently same procedure, this is where the non scheduled runs occur. Touch wood, not have had the extreme problems of others, did have an issue yesterday morning which I don't think was directly connected, WaasMedic was one of a number of processes running, stopped in Task scheduler so it did not complete. This morning on boot, it ran so it appears by stopping you are actually postponing. Still awaiting some response from Microsoft,but as usual, they appear not to want to know. No need to apologise for not being tech savvy - you are in the company of MS developers.

    Was this answer helpful?

    0 comments