WaasMedic Agent Exe stopping me from working

Update 5th June on posting of yesterday. Someone at MS must of read my posting, this morning, a little slow opening apps for a few minutes. Task Manager showed Windows Module Installer running. When checked WUD's, 21H1 no longer an option, had auto installed, just requiring restart so moved directly from 2004 to 21H1 bypassing the 20H2 version. According to MS, auto install only happens after 18 months, appears to be another MS fib. Only difference seems start screen a lot darker - complaints seen from users with this issue on 20H2 update. See what happens tomorrow with WaasMedic auto. Also optional KB5003214 preview released for 2004 to 21H1, could muck up taskbar icons, about time MS employed a 5 year old to do updates, no doubt could do better.

Paul:

Another recent submission about WaasMedic hurting system response to Feedback Hub:

June 2, https://aka.ms/AActhif  “WaasMedic Agent makes system unresponsive”  

--------------------- 

Note: If you have a problem with WaasMedic Agent hurting your system performance,

please use the Feedback Hub app on Windows 10 to report the problem to Microsoft Engineers.

-- This forum is a user-to-user help forum. The vast majority of responses here come from volunteers.

-- Matters in this forum are not automatically passed on to Microsoft engineers for resolution.

-- The “official” method to report technical problems to Microsoft is to use the feedback hub app on Windows 10.

Another interesting WaasDay yesterday. On this system which has an SSD it only ran for a few seconds, too fast to even catch. On my studio system with an HDD it ran for 13 and a half minutes grinding away at 100% while reading files in the WinSxS and LCU folders and then reading personal files that have nothing to do with windows. This system is an old i5 3470 with 8 gigs of ram while the studio is an i7 8700K with 16 gigs so there's no way it should perform less than this system other than the type of drives they have. I don't think I can call Waas spyware at this point despite its activity since if it was it would also scan my internet system with the SSD which is loaded with files. I think that's a clue, the difference between the SSD and HDD and also Waas doesn't seem to scan the D: drive only the C: drive. I think the Waas issue is a BUG that M$ simply can't fix. The fact that M$ employees won't read this thread to get an idea of what's going on to see if we might actually provide them some information that's not included in the Feedback Hub reports tells me there will be no fix and every Sunday I'll have to put up with Win 10 degrading the life span of my hard drives. So I've been looking at Apple Mac systems for music production and will continue to use Linux more and more for internet duties. Not one more penny from me M$ not one penny more.

It is nice you have found the feedback entries. I gather it is possible for random MS engineers to access the reports because when I try to look at the links, for every one that has been posted in this thread for the past several months, I get "your account does not have access to this feedback" so there is no way to add support to it. In fact, I can't even locate / access the report I filed through feedback last month. So I think "Feedback Hub" is just another way to sucker people into spending more time logged in to their MS account so that MS gets that much more access to your machine, can add more personal data to their profile of you (likely for sale to third parties as well as for expansion of MS efforts to market to you) and to give you the false sense that they will actually DO SOMETHING about the "problem".

In this case the only "problem" MS sees is how to prevent users from interfering with MS spyware, in this case WaasMedicAgent and all the "minions" it spawns during the boot process. After everyone caught on to "compattelrunner" and how to prevent that from running they had to design a newer spyware item, more intensely integrated into the OS, harder for users to thwart so they could continue to upload the contents of your HD to their "data analytics" systems.

I guess, even if you have managed to disable OneDrive, if you ever lose a critical file you could always petition MS to get it back from their spyware-obtained image of your system. ;^}