WaasMedic Agent Exe stopping me from working

Had an issue about 12 months ago running 8.1, that was continuously running some Windows Process, not this one. I rebooted 1ce or 2ce but it appears to say, I have not finished, I'll carry on, the only way to get out of it was to let it run it's course. It was something connected to updates - I ran the trouble shooter - it reported something wrong - told it to repair - it wiped out all the updates history Thanks Microsoft. Bet Macintosh are rubbing their hands with all this new business coming their way. I always create a Restore point before installing updates although I assume you only restore once you are up & running. If it is supposed to cure problems why do the problems keep reappearing. Best computer I have is the old XP, MS made updates take hours to install forcing you to update to 8.0, I switched of updates there & then, still boot about once a week - no issues at all - no updates received for 8 years, only keep it live because of old apps that are useful but phased out years ago.

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.

WaasMedic running this morning on boot, created a bit of a slow motion issue but this soon cleared although it was running for another few minutes with no real noticeable effect. First boot of day normally a bit more disc activity as it runs various components on a daily basis such as WUD's etc.

Booted this afternoon, same strange lock screen/log-in  sequence as 12th March PM boot. Thought 'here we go again' - may as well go & do something else until Microsoft & computer decides it's time for me to use. Turned out to be ill founded, WAASMedic was not running - , waited my normal 3- 4 minutes before attempting to open anything - all OK. Looks as though delay I had in receiving March's update, Microsoft have not addressed this issue in that release.

I had the same issue and the below guide seems to have fixed it for me, so I guess it was related to Windows having some sort of issue with update checking. 

https://helpdeskgeek.com/windows-10/windows-10-checking-for-updates-taking-forever-how-to-fix-it/