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: Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2021-05-02T14:03:26+00:00

    Ok I've booted two computers so far today on "WaasDay". On one it ran for 7 minutes at 100% disk. On this system it only ran for about 2 minutes but this system has an SSD. Waas spent more time reading from the disk than writing. You can't fix Windows problems by only reading files. I did notice that Waas was reading personal files from the D: drive that have nothing to do with Windows. There is no reason a "service" that is supposed to be fixing Windows update problems needs to read from the non-system drive and access files that have nothing to do with Windows. So it appears that WaasMedic is spyware and Windows is a virus. Now I've got to boot three more systems. WaasDay has become a real source of frustration here.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-05-02T14:08:47+00:00

    I noticed that Waas was reading files from this location. Notice there are folders for each Rollout Tuesday since March. So they broke something with a rollout in January or February and have been trying to fix it since then. But again they're not fixing Windows issues by reading non-Windows files from the non-system disk. 

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-05-02T15:20:12+00:00

    Just booted my laptop. Waas ran for 22 minutes and 30 seconds at or near 100% disk along with other Winbloats services. It was reading files in my Download folder....my Download folder. 90% of the time Waas was simply reading from the disk not writing with apparently no network activity. What the hell is Waas doing to our systems ? Is it simply designed to wear them out so we have to buy new ones ? God I hate Winblows.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments