WaasMedic Agent Exe stopping me from working

So I got a new laptop. Well I didn't actually buy a new laptop I just installed Kubuntu Linux on my old one and it runs like new. So much faster and more responsive than Winblows 10 21H1 and Linux doesn't spend all day grinding away at my hard drive. On the day I did the installation I booted Winblows 10 for one last time and WaaS medic ran at 100% disk longer than it took me to download the 2.7GB Linux .iso on my Kubuntu desktop system and then burn that .iso to USB to create the installation media. WaaS was STILL grinding away. That was it I had enough and overwrote Winblows and now I have a fast, elegant, and privacy respecting Operating System instead of a data collection system that is only designed to wear my computer out. Then I began to wonder maybe that's Microsoft's plan. Get people to stop using Windows 10 on older systems so they don't have to support them (not that M$ ever gave ANY support at all) and it will save them a ton of bandwidth every update Tuesday. They've already got our money so what's to lose? On my studio system WaaS tried to run again yesterday even though it ran for ten minutes on Sunday. I just did an end task which is what I'll have to do every time it tries to runs I guess. WaaS Medic is nothing more than Malware intentionally created by M$ to wear out older systems. If M$ didn't have enough money to buy every lawyer in the world I'd say a Class Action Lawsuit would be in order but consumers can't fight a corporation as big as M$.

megawhite,

Unfortunately you are under the impression that Microsloth CARES about users - individual users like us - when they have demonstrated this past year that they don't even give a **** about their "Enterprise" users. (REF 8-month lack of response to security community notification of security hole that allowed billions of losses due to ransomware attacks that MS could have prevented if they simply responded to the warnings and tech info supplied by the security community.) The calculus is that they are SOOoo BIG, and users are SOOoo HOOKED on the Windows platform that secure or not, efficient or not, they will continue to spend on upgrades and subscription renewals of MS OS and applications.

THEREFORE, there is no point wasting the 20 - 30 engineering hours to close security loop holes or to patch the OS to STOP SPYING ON USERS. Rather, since we are "addicts" it is more in MS' interest to spend hundreds of hours figuring out ways around the law (e.g. the EU anti-trust ruling against integration of Internet Explorer into the OS which is now being done with Edge) to FORCE users to use MORE MS products that require GREATER transfer of your money to MS coffers, AND increase the amount of personal profiling spyware MS can load on your machine for their data mining endeavors - info both for sale to third parties and for their own 'internal' use.

Right now one of the most obvious uses is to find and eliminate any user workarounds that defeat MS spyware and / or OS configurations that provide greater efficiency for USER TASKS and 3rd party application use. IOW, MS is DONE "innovating" the OS - it has now turned into a professional hacking operation to hook you into the questionably legal "subscription" (ransomware?) licensing schemes on more and more MS products. Don't be surprised at the number of 3rd party applications that may not run on Win 11 - Microsloth will offer MS "alternatives" because it is now all about thrusting MS hands deeper into your pockets and becoming more intimately knowledgeable about you than your lover or soul-mate. There is no longer any interest in serving YOUR needs or wants in the operation, configurability or efficiency of the OS.

First of all, as I posted ages ago, a Microsloth employee actually said the assumption that WaasMedic was an update repair tool was false despite its "Properties" description. The clear implication is that it is actually designed to do something MS does NOT want you to figure out. On my system it did not restrict itself to perusing update file directories; it always read EVERY FILE IN MY UID after going through the system files. Since I have over 20,000 photos plus "side-car" files for each from various photo processing applications, WaasMedic would run for over an hour making the machine unusable for 40 to 90 mins after boot. Clearly, despite all my privacy settings, MS was building a detailed profile of my system but for what purpose?

Since the trend since Windows XP has been to reduce user-confgurability, force the user to give up more system control directly to Microsloth, cede more privacy rights to MS, and trick users to connect directly with MS servers (SkyDrive, OneDrive, Office / Microsoft 365, MS account to install / activate) if possible, for the entire time the system is powered up, the assumption that Windows will become a subscription service is probably a very good one. The point is the <removed> they have users by are the ones users unwittingly handed to them by letting slide all the privacy violations, monopolistic unfair business practices, and flat out lying they have done with impunity (WaasMedic being a prime example).

I only escaped WaasMedic impacts with the installation of an SSD about two weeks ago. My experience seems to confirm that WaasMedic on an SSD surveys VERY FEW files on a boot drive hosted on SSD. I cannot get Task Manager / Resource Monitor up fast enough to even catch it running. But still, to be safe, I moved "Documents", "Pictures", "Music" and "Videos" to the hard drive that used to be to boot volume. Now along with two separate RAID volumes, WaasMedic does not seem to access any personal files anymore.

So why would MS want us all on SSDs? Simple. They can mega-load the OS with spyware, marketware, MS Store apps all of which auto-start at boot time, yet users will not be "bothered" by the 30-secs to 1 minute SSD boot-up time. Purpose of all the fatware? To be able to capture your every keystroke, screen state, app activation, media file usage etc. etc. IOW, to have full-time, all-action surveillance of your system usage logged on their servers. The excuse? "Microsoft has innovated Windows to the first cloud-based Operating System, so like any other utility it needs to fully monitor usage for proper QoS to give its users the best experience." (Putting on waders as the MS BS is getting so deep.)

The government will not do its job and break-up or stand up to the monopoly. So, there is only one choice - Linux.

mrlc - Wishful thinking - now in the seventh month - only the one response from so called Microsoft employee - this WaasMedic thing is a MS designed feature - it does nothing useful for any Windows user, just MS poking their nose into your private files, data farming etc. If they were remotely concerned they would post s a regular update, they have not even acknowledged there is a problem Likewise the recent PrintNightmare issue. The fact people (me) were getting Blue Screens, people not able to print, people not able to access internet etc. - Ms the 'patch works'. The real experts version it may close the back door but does not close the side door. The did release a registry fix but apparently got either the key or value wrong. What little confidence we had in MS has now completely disappeared.