WaasMedic Agent Exe stopping me from working

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

When this thread started it may have seemed like WaasMedicAgent et. al. were "buggy", needed to be reported to Microsloth (because all their own people running Windows were too stupid to notice it or too lazy to report it to the 'development team'). But if you've followed the thread you realize there are several mistaken assumptions regarding this issue.

MISTAKEN ASSUMPTIONS:

1. WaasMedicAgent etc. are legitimate routines that just have resource hogging bugs that Micosloth wants to know about and fix.
2. That WaasMedicAgent is as described in its properties, a routine to find and fix Windows Update errors. (An MS official has stated this "user assumption" is incorrect.)
3. Microsloth is the least bit worried about losing a few individual and small business owners to Linux / iOS.

The calculus and focus are as follows:

1. The majority of money is made from enterprise users. They form a captive market because moving to a new OS / platform would be prohibitive in terms of both cost, down-time, retraining expenses etc. So they can be abused to no end and the monthly service fees and upgrade fees etc. will keep pouring in. No need to really "innovate" the OS anymore, just add features that increase their dependence on MS "Enterprise / Cloud / Colaboratiive" services that allow MS to peruse all kinds of data, including hijackable proprietary corporate information that can be used to tighten a monopolistic grip on IT services.
2. Individual / SMB users are really more of a pain than the profit from their upgrades or license fees from individual device purchases is worth. But most are invested in MS and / or Windows compatible applications with proprietary data formats and are unwilling / unable to bear the cost and inconvenience to take on a new OS and try to convert / reconstruct all their personal / SMB data and operations on a non-Windows platform. So if MS "flushes" even 40% of such users from the "Windows Family" - not only "no big deal", actaully "good riddance".

MS doesn't give a **** about anything said in this thread or anyone posting to this thread. Any "feedback" that has been submitted regarding this issue, I'm sure, has been piped directly to the land of NULL. So while it may provide a little relief to your BP to post here, beyond that it is a total waste of time. Our only real options are 1) move to a non-Windows platform or 2) surrender to the abuse and just admit to ourselves that we are just MS drones / suckers for life.

I couldn't have said it better myself. I am utterly disgusted and extremely angry by what is going on. MS are literally shipping malware!

"I have the same issue and the interesting part is in the performance monitor it is not possible to terminate the process.

While this process is running it almost impossible even to access the performance monitor, it tests your patience."

I have ZERO patience for this nonsense. It is absolutely DISGUSTING the level of utter rubbish software this trillion dollar company is pushing out. Incompetence beyond belief.

"I expect a clear and profound explanation and no lousy excuse."

Absolutely, I demand an explanation as to why MS MALWARE is carrying out a denial of service attack on one of my computers every week. As a software developer it is utterly beyond me how such junk is allowed to go out the doors. The simply don't consider that not every computer running W10 is i7 spec with an SSD.

When this thread started it may have seemed like WaasMedicAgent et. al. were "buggy", needed to be reported to Microsloth (because all their own people running Windows were too stupid to notice it or too lazy to report it to the 'development team'). But if you've followed the thread you realize there are several mistaken assumptions regarding this issue.

MISTAKEN ASSUMPTIONS:

1. WaasMedicAgent etc. are legitimate routines that just have resource hogging bugs that Micosloth wants to know about and fix.
2. That WaasMedicAgent is as described in its properties, a routine to find and fix Windows Update errors. (An MS official has stated this "user assumption" is incorrect.)
3. Microsloth is the least bit worried about losing a few individual and small business owners to Linux / iOS.

The calculus and focus are as follows:

1. The majority of money is made from enterprise users. They form a captive market because moving to a new OS / platform would be prohibitive in terms of both cost, down-time, retraining expenses etc. So they can be abused to no end and the monthly service fees and upgrade fees etc. will keep pouring in. No need to really "innovate" the OS anymore, just add features that increase their dependence on MS "Enterprise / Cloud / Colaboratiive" services that allow MS to peruse all kinds of data, including hijackable proprietary corporate information that can be used to tighten a monopolistic grip on IT services.
2. Individual / SMB users are really more of a pain than the profit from their upgrades or license fees from individual device purchases is worth. But most are invested in MS and / or Windows compatible applications with proprietary data formats and are unwilling / unable to bear the cost and inconvenience to take on a new OS and try to convert / reconstruct all their personal / SMB data and operations on a non-Windows platform. So if MS "flushes" even 40% of such users from the "Windows Family" - not only "no big deal", actaully "good riddance".

MS doesn't give a **** about anything said in this thread or anyone posting to this thread. Any "feedback" that has been submitted regarding this issue, I'm sure, has been piped directly to the land of NULL. So while it may provide a little relief to your BP to post here, beyond that it is a total waste of time. Our only real options are 1) move to a non-Windows platform or 2) surrender to the abuse and just admit to ourselves that we are just MS drones / suckers for life.