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-17T14:31:05+00:00

    The URL for the feedback entry I created above is: https://aka.ms/AAckw40

    Thank you, GlenS9. I see the feedback entry and I have promoted it.

    Paul...

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-05-17T14:05:28+00:00

    The URL for the feedback entry I created above is: https://aka.ms/AAckw40

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-05-17T14:00:32+00:00

    WaasMedic ran this afternoon on boot, bit more pronounced than yesterday am. During this time opened one app and that one continued to open slowly even after WassMedic had finished. Restart brought the app. running OK. Couple of weekends during the Sunday scheduled run, had to cancel thru' task manager due to another start issue. Then it ran on the Monday, since then has run on both Sunday & Monday - does this mean by cancelling a run, the situation is made worse? Each time you cancel you get an extra run, would this eventually mean it will run every day as some people are reporting? Evidently something major wrong with either WaasMedic or Windows 10 OS.  General lack of response/solving by MS infers this is happening by design. I thought a MEDIC was supposed to help with the health of a person etc. it appears WaasMEDIC works in contrary to this as far as Windows 10 OS is concerned. We know you are picking up this issue by various MS stealth means, you KNOW the issue -SORT IT

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-05-16T13:56:00+00:00

    LucyScott1 - My 'Normal' Sunday morning WaasMedic run lasts maximum 8 minutes as this morning (UK) - we seem the 'Lucky' ones. This morning mine was hardly noticeable , few apps bit slower in opening during first access of the day, peaked after about 4 minutes then effect tailed till the 8 minutes had elapsed. Normally I have another run after day or day & half after installing WUD's, did not happen this May patch Tuesday release - had hoped issue may have been solved - apparently not. Since beginning of year had a couple of bad runs but these still only lasted the 8 minutes total. Only trouble is that it runs at start-up when there is other stuff loading such as system files/apps etc. Unfortunately appears to be inbuilt to run on Task Scheduler Trigger which is not changeable. Seems to run before checking if any updates out there. Six days a week this is logged as 3-5 minutes after boot, but, like today, recorded as 12 minutes, 3-5 + the 8 WaasMedic running time. MS don't seem to be making any effort to solve this major issue.

    Was this answer helpful?

    0 comments