WaasMedic Agent Exe stopping me from working

Today WaasMedic ran for over 40 minutes keeping the system next to useless. I did manage to get Resource Monitor open in time to catch it not only reading but also WRITING to disk. About 1/4 of its total MB/s IO were writes! Yes the machine was booted yesterday, yes it ran yesterday, and no there is no task in Task Scheduler to run today. So it appears MS got tired or resetting the task for the Sunday runs that we attempted to remove from the task list, and have just integrated WaasMedic running into the base OS boot procedure. I.e., MS knows what is best for you even if it means reducing your productivity to nil.

As for "MS Suicide", I believe the problem is this: MS does not like to hire experienced people. Rather they like to hire straight out of college to they can teach the "MS culture" to their 'engineers'. That basically involves keeping them in the dark about all but a specific aspect of the OS so that no one person knows enough to go out on their own and build a competing OS. I.e. they are keeping people from doing what Bill Gates did to the originators of CPM. He effectively stole their product, simply reversed command arguments and called it "MS DOS". The upshot of the "MS culture" is a patch work of modules assembled into an OS without an overarching, disciplined and rigorous "Integration Engineering" function. That is a person and department responsible for developing requirements, overseeing design and development to a holistic architecture the requirements define, and rigorously testing to the requirements before release. Without that you get the ad-hoc, "organic" sprawl and disorganize assemblage of functions that is Windows 10.

Further, since the "development team" are all social media babies, they are no longer OS engineers but "connectivity advocates" who are intent on hanging every bit of "connectedness" for a 24-7 "digital life", which means chaining you ever tighter to MS cloud and marketing services by weaving applications into the OS rather than providing the the most compact, secure, flexible yet easily configurable software to run your computer hardware in service of the applications of YOUR choosing.

I am consistently seeing a continual growth of these kinds of processes popping up on Windows OS (currently running v10). And yes, they do seem to be building up and impeding processing power on unchanging hardware. In this regard, Windows appears to be utilizing "Apple" performance limiting technology, identified to be downloaded on existing Apple hardware, used on Apple phones to promote upgrades to upcoming hardware platforms.

As Microsoft has the ability to download monitoring software agents to identify the hardware platform your software is running on, to avoid the eventual legal entanglements that Apple was hit by, perhaps it might be a better logical approach to tune your software products to not utilize platform information to churn CPU and Disk drive horsepower to determine upgrade paths.

You have this HW info on Microsoft databases, why are you not utilizing that data to build an effective update process to determine and deploy efficient updates to customers HW platform as they exist, rather than slamming software updates that extend beyond the capacity of existing hardware platform, then churning more CPU and hardware to determine viable or desired upgrades components after they have been deployed on said platform.

This process needs to be modified from current OS development proliferation standards. It is unfair to customers and creates an artificial need to upgrade hardware.

Though your idea of a smarter and continually insurgent AI existence in your software is considered an improvement to performance and your profit bottom line, it is clearly an aggression against your client base as well. It seems your company serve its customer more by better identifying the need for HW enhancement in you OS upgrades and communicate it, and allow for "bypass" components indicators within your upgrade delivery system that will denigrate overall system performance.

It is forcing me out of Microsoft OSes and into alternative OSes like LINUX derivatives. I understand the possible security impact arguments you would argue against such a move, but your company principles are consistently pushing me in that direction.

I think I may have found the solution at least on my laptop. KB4601382 was installed on 02/27/21 but KB4601554 which was released 02/24/21 wasn't offered up to my laptop until yesterday even though I did attempt manual updates.

Once KB4601554 was installed I have not noticed WaasMedic.exe running at all. So it appears Microsoft dealt out updates out of order and WaasMedic was trying to repair the issue. KB4601554 should have installed along with 4601382 on the 27th.

Of course "System" along with Microsoft Compatibility Telemetry etc are still running at 100% Disk for about 10 minutes but it has leveled off after that.

I have the theory that the constant disk wear caused by Win 10 is sort of a "planned obsolescence" ploy. If your system wears out or slows down you may be likely to purchase a new system and of course then Intel or AMD get their money and Microsoft gets money from another license.

Whenever I run a Linux Distro it does not have the constant disk activity. It loads then rarely ever accesses the disk unless you're loading a program or doing other tasks. It doesn't just sit there grinding away at the hardware while the system is momentarily inactive.

Thanks for posting. I do have an external drive which I use for backups. Next time this happens, I will try disconnecting it.