WaasMedic Agent Exe stopping me from working

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.

Reading something a while back that MS will not be progressing to Windows 11, apparently they are thinking that the evolution will be a pay by monthly subscription instead of a once only licence payment included in purchase price of computer which no doubt we all accept. Hands up anybody who would be prepared to pay for the current standard of service of updating & record of ignoring customers views and issues.

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.

My laptop just got fed KB4601554 which was released 02/24/21 even though it didn't popup with a manual search yesterday (damn rolling updates). 4601382 was installed on 02/27/21. 20H2 was installed back on 11/3/20. I don't see WaasMedic running now although the description for 4601554 doesn't seem to address any update issues. I'll keep an eye on activity and see if WaasMedic comes back. Maybe 4601554 was the fix. https://support.microsoft.com/en-us/topic/february-24-2021-kb4601554-cumulative-update-preview-for-net-framework-3-5-and-4-8-for-windows-10-version-2004-windows-server-version-2004-windows-10-version-20h2-and-windows-server-version-20h2-958fff0c-783b-27b3-8a93-226f7798225a