WaasMedic Agent Exe stopping me from working

Yep, my computer is doing exactly the same 'waas crawl'.

However, I feel lucky - My current computer is the replacement I bought for the one that a windows update before Christmas totally killed.

Corrupting my SSD driver as part of a software upgrade is simply not acceptable. I suppose it's chromebooks from now on..... sad, but necessary I suppose. 

Windows updates have now killed 2 of my computers. I had to pay for a previous one to be rebuilt by professionals after the Windows 10 forced update. I am content to pay Microsoft for windows, but they need to be financially accountable for any damage their updates cause.

If anyone has found a way to recover the cost from Microsoft of repairing PCs that have been incapacitated by updates I would be very happy to hear about it.

Same thing here, but...

After it took 45 minutes to get to the desktop the system became unresponsive, even trying to open Task Manager gave me the popup message: "Microsoft Windows: The system is not responding". (Never saw thatone before)

So I tried several reboots with the same result.

Finally I used the recovery stick to remove the latest update. After 30 minutes the system finally rebooted again OK.

I immediately turned off updates (well... suspended, since Microsoft no longer allows me to turn off any updates) but on the next reboot the system was very slow again, so i checked Task Manager and again WaazMedic running followed by diskdefragmenter and WINDOWS UPDATE orchestrator, manager, helper, installer...

Took over 2 hours! (while updates where still suspended!)

On next reboot the messages "updating system" and "preparing windows"  again taking over half an hour...

Then, checking update history, NO Updates installed in the past 2 days and no update errors...

What the hell are you doing Microsoft??

Another reboot, a cold boot - still no March Updates available. Windows Update from Tack Scheduler has also run this morning - I think this is a secondary check to see if main WUD has run. Still nothing - has March been pulled - we had a pulled release either in January 2019 or 2020. Perhaps a lot better NOT getting updates. Everything seen on web does not mentioned pulled but all mentioned items are timed prior to normal release time.

Timing with me is basically as MarcHoppe's posting of 3rd March. Being old fashioned, normally leave for about 4 minutes from switch on before doing anything. With me, as this morning get about 5 minutes of disc running, short break, then another 4-5 minutes before it settles down. PM start up normally shorter duration. When it does run, normally no real effect on performance, this morning when I checked Task Manager - performance showed total 6% CPU & 50% disc, WAAS was running but kept jumping between top 4 or 5 processes with at least a couple of apps on screen. I keep a note of WUD running, normally records as 3-5 after AM boot, last week there was a second running recorded from Monday - Friday between 7:12 am & 7:16 am although boot times were up to an hour prior to this. There has been no Errors shown in WUD but there again there appears to have been any updates either auto or manual search. Completely baffled what is going on, in good company though, as it appears MS have no clue either otherwise they would correct it (or would they?)