WaasMedic Agent Exe stopping me from working

I am not sure about the significance of the apparent HDD vs SSD difference. It can be just an indication of what precisely is installed that needs some attention.

For example, I never noticed this phenomenon until I started experimenting with Docker Containers, some others have mentioned other products in relation to the nasty behaviour.

But all that aside... Wouldn't it be nice if Microsoft themselves came back with an explanation, rather than us users working on this?

It is a confidence boost when the vendor shows that they know what they are doing.

Very low score to Microsoft in this case.

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.

MS is most likely going to "solve" this problem by hiding this malware under svchost like they did with superfetch.

Guys, when are we going to fully switch to Linux?

Yes, this is not a bug as far as MS is concerned. The "problem" is that their spyware was caught by users due to its ridiculous gluttonous consumption of system resources, and now they have already spread much or WaasMedic spying to other modules without relieving the resource consumption issues.

The main point here is that MS (being too big to break up or prosecute) is going to use it monopolistic power to:

1. violate your privacy in any way they can to effectively build a moment-by-moment profile of your machine use, tracking your every key stroke, and uploading the complete content of your HD's to their servers. This data they then use for algorithms to force marketing / advertising ware onto your system, and to figure out which competitors software they need to subvert so you'll buy a Microsloth product to replace it.
2. Utililize data about your devices to figure out how to spy on you even when you are not touching your device (e.g. spying through your camera, listening through your microphone, monitoring gyro and GPS to track your movements etc.)

As for Linux, I would love to switch but most of my "pro" video, audio and photo processing tools plus an Access 2007 database I have to maintain for a long-time client do not run on Linux. Otherwise I'd be gone in a second.

If it is spyware then why doesn't WaaS scan my SSD like it does my HDD drives? The SSD on this system has 68 gigs of files yet I don't see WaaS scanning this drive or the D: drive. It only runs for a few seconds. It started to run on Friday on the HDD of my studio system reading files in the WinSxS folder. I just did a quick restart and it did not run again. Let's see what happens tomorrow on the scheduled run. I'm going to monitor run times on every system and take note of the files it reads. I'm afraid this issue is simply not going away. It's either a bug that Microsoft can't fix or it's intended behavior that will continue to grind away at our drives every Sunday. We'll see if 21H1 brings any relief but I don't have much faith.