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-06-08T08:44:44+00:00

    I don't think the burden of proof is on the user here.

    At least 3000 people have done their police work and identified WaasMedic as the culprit and I am writing this in June '21, 5 months after the OP submitted this and his feedback and I am still facing the problem.

    What happened to the time you guys took your money upfront and left us alone?

    I am fed up of having to find out what things you keep screwing up with my computer on a regular and consistent basis.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-04-15T00:28:48+00:00

    Yes we know what WaasMedic is. Nobody is going to install some shady third party app to workaround this issue. Microsoft needs to fix it.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-04-04T05:24:03+00:00

    We are the people suffering but are expected to notify Microsoft -this has been going on for a while now - time they sorted, got to be something MS have got wrong in one of their releases - this was first reported in this thread 2nd January 2021 - nearly 4 months ago - does not inspire confidence in MS. Just to think, couple of years ago, after various problems, they promised a lot more testing & Insider feedback before releasing 'iffy' WUD's - does not seem to be the case -come on Microsoft CURE IT now.

    Why are we still paying for this OS? It's getting slower and more invasive for each "update", is there any petition one could sign up on to wake them up? Microsoft used to do great OS:es, what happened?

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2021-03-07T04:39:51+00:00

    Also back for me. Probably because "Xerox - Extension - 7.208.0.0 Failed to install - 0x800f020b" every day since 02/17/2021 under "Driver Updates." Now, I have a Xerox Phaser 6510 connected to a combo wired / wireless router via ethernet cable. My workstation is connected to the router by ethernet cable. I have the latest "type 3" drivers installed, and the printer works just fine.

    The 6510 does NOT show up under Control Panel->Device Manager->Printers, but does show up under Device Manager->Print queues, Control Panel->Devices and Printers and Settings->Devices->Printers & Scanners.

    According to elsewhere in this forum (https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/error-code-0x800f020b/79af6b76-9143-41d1-bf67-512905ae2256) the "Windows expert" says this is because the device for which a driver update is attempting to install no longer is connected to the system OR a simple run of "Windows Update troubleshooter" will fix the problem.

    WRONG! I've uninstalled / reinstalled the driver, run the windows update troubleshooter, tried "Retry" on the update failure message in Windows update when the printer was on, off, the driver removed, driver reinstalled, etc. with no change. The proper solution would be for Microsloth to provide a "give up on this update since you are too stupid to figure out it won't install" option and hence stop WaasMedic from preventing me from getting any work done for the first 40 mins - 1 hour after booting.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments