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-09-12T10:05:35+00:00

    So I too was having this problem, but at least I was able to figure out what it was doing wrong in my case. I ran the Microsoft process monitor Process Monitor - Windows Sysinternals | Microsoft Docs tool to see what files, registry, and resources WaaSMedicAgent.exe was actually accessing at the time. I discovered that the WaaSMedicAgent.exe was busy reading files in the C:\Windows\servicing\LCU folder, so I navigated to it using explorer. The folder contains 3 subfolders:

    C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1110.1.15 dated 7/17/2021

    C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1165.1.8 dated 8/25/2021

    C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.1202.1.15 dated 9/3/2021

    If you're not aware, these folders contain files used by Windows Update to patch various services in literally every OS version for the listed cpu architecture (amd64 in this case). The 3 folders collectively contain 255,153 files in 80,059 subfolders totalling 3.09 gb of data.

    According to procmon, WaaSMedicAgent was reading every single one of these 255,000 files and checking each one to see if it was needed. Here's the kicker though, each of those folders is from a PREVIOUSLY INSTALLED WINDOWS UPDATE! That means WaaS is checking OLD patches to see if they need to be patched AGAIN! Not only that, they're for the amd64 architecture, but my cpu is intel64. So I don't even need any of the updates! Womp womp. The resolution is to delete all 3 folders to keep Windows from attempting to patch things it doesn't even need. The bug appears to be that Windows Update does not delete these folders when it is done with them, and of course downloaded files for the entirely wrong cpu architecture.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. JX313 7,050 Reputation points
    2021-09-12T05:28:55+00:00

    Click the Subscribe button under the body of the question part > click Unsubscribe. That's all.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-09-07T00:06:28+00:00

    That is because Microsloth monitors this thread so they can defeat any method users fine to disable MS snoop-ware and pushes those fixes out with a far higher priority and speed than they use even for security flaws (like the one they left open FOR EIGHT MONTHS after the loophole was publicly exposed, during which time BILLIONS were lost to ransomware attacks!).

    In the case of some spyware, they have added an invisible "user", and given it permissions only they can manage - ABOVE AND BEYOND WHAT SYSTEM ADMINISTRATORS CAN MANAGE! So in essence, they have take possession of your system without your permission to administer as they see fit regardless of your requirements or needs. Get used to it - that has been their intent all along - to completely own your entire IT data and life once they got too big to be challenged by the marketplace, the courts, or national governments let alone a few "disgruntled looser users" (MS opinion of us, not mine).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-09-06T11:01:25+00:00

    Seems the only way is to disable it in the Task Scheduler.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments