WaasMedic Agent Exe stopping me from working

MarcHoppe:

Thanks for your post.

I was wondering how you determined which files were accessed by a process. I see you used MS resource monitor... disk activity and filtered on the waasmedic agent process. I will use that in future.

Interesting the difference in files read by waasmedic on SSD system from those on HDD system. In the past have your SSD system(s) experienced performance degradation from waasmedic, or have you seen the problem only on HDD system(s)?

Happy WaaS Day everybody. Here is my report for 06-13-21. I finally managed to catch WaaS running on the system that has an SSD. It only lasted for about 30 seconds or so. It did not read all the files in the WinSxS or LCU folders even though all those files are present. However on another system with an HDD WaaS ran for over 8 minutes reading those files in WinSxS and the "Package for Rollup Fix" folders. On one system where I did the registry hack to disable WaaS it did not run and in the Task Scheduler gave the message "this service could not be started because it is disabled" so that reg hack appears to work. However on another system where I had done the reg hack a Windows update turned WaaS back on. So the reg hack is something that will have to be done again after every update. It only takes a few seconds to apply so no big deal. *Disclaimer* I am not advising anyone to do the reg hack as I have no idea what long term affect it will have on a system. If it causes Windows to stop working on the systems I have applied the hack I'll simply and gladly replace Winbloat 10 with a Linux distro and watch them perform 100% better. The image below shows what was scanned on the system with a SSD and again it only ran for about 30 seconds. So either this WaaS issue is something that only affects systems with HDDs or M$ is deliberately causing the system degradation from WaaS either for nefarious reasons or out of plain incompetence.

Rick HB - Had this Dell desktop a couple of years now from new, did not even know WaasMedic existed till the beginning of this year as it had shown no issues. Like everyone else, problems came to light early this year when it appears everyone began to notice performance issues, this seems about the time the WaasMedic app was modified and subsequently installed during the Dec/Jan WUD's. This morning, Sunday's scheduled run, today, did not notice any problems, only by opening task manager realised it was running, started a minute or two later than normal & lasted a minute or two shorter than 'normal' Sunday. I have Office 19 retail installed, here again from day one with this desktop from new. Just in passing, have had issues with manual updating & on-line repair with Office 19, come back with errors as it appears when attempting this, does not attempt to update installed version but the 360 version. Auto updates were OK until 12-18 months ago, then error came back with , again, trying to update with 365. MS cant even get this right. I disabled updates, that has been OK since. Still have a XP available as has a couple apps that are no longer available, switched off MS updates 5-6 years ago, still keeps plodding on, cant use Internet etc but no updates - no problems. Like wise Old HP laptop running 8.1, still receiving updates but of course lacks overall performance. A while back saw various reports that 8.1 was generally more stable & reliable than Windows 10 - reports seem to be correct.

This is getting ridiculous. My login this morning took over 45 minutes. I barely even use my new HP pavilion laptop due to logins ranging from 2 minutes to now over 45 minutes. This is without knowingly installing any new applications or loading any significant data. I'm amazed at how much I can consistently do on my iPhone making my laptop obsolete other than the screen size. I'm so frustrated I'm tempted to plug in my iPhone to a larger screen or buy a Mac at this point. I also entered a Hub and got zero response. Ironically, my performance also decreased after entering the Hub response. There is obviously something wrong with the O/S. From the other comments, it doesn't sound like it's isolated to HP hardware or Office 360, but those are the only two other variables I can think of potentially being a problem.