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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2021-09-12T10:30:52+00:00

    Feedback link with log file: https://aka.ms/AAdsqzb

    Was this answer helpful?

    0 comments
  2. JX313 7,050 Reputation points
    2021-09-12T10:22:31+00:00

    amd64 folders are NOT from AMD (even if it's used in AMD-powered devices). You should NEVER delete those files! Instead, press Win key + R and type cleanmgr and press Enter > after the first scan, choose Cleanup system files > after the 2nd scan, choose all options and proceed to delete them.

    Suggest reading before deciding to delete:

    1. https://answers.microsoft.com/en-us/windows/forum/all/why-are-there-amd64-files-on-an-intel-machine/7482ee8f-511a-45c0-b3a3-8542a74801c9
    2. https://superuser.com/questions/804490/huge-amount-of-amd64-files-in-winsxs-8-93gb-what-are-they
    3. https://answers.microsoft.com/en-us/windows/forum/all/amd64-microsoft-windows-files/59410fb5-001e-4e09-9e19-30236526d1a2

    Those are system folders you shouldn't delete. If you do, it could corrupt your system and may need reinstallation / InPlace upgrade to fix it.

    Was this answer helpful?

    0 comments
  3. 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
  4. Anonymous
    2021-09-12T05:32:51+00:00

    Thanks. I must be dizzy, daffy or both. I'll swear earlier clicks on Subscribe only yielded another "Subscribe" option. For now, I got what I need. Thanks for your patience and quick reply.

    fm

    Was this answer helpful?

    0 comments