WaasMedic Agent Exe stopping me from working

For the last week WaasMedic Agent has been reducing my PC to a crawl. I've checked updates, as suggested, it says I am up to date. Why is there no response from Microsoft concerning this problem?

Update - just checked back - scheduled run should have been on 14th March - actually run from my records on 12th March - day after of installing March WUD's which I should have received on 10th but did not come thru' that day, no error shown, manual runs not picking up anything. Actual updates arrived & auto installed on AM boot of 11th. This instance was the worst I have seen but effect disappeared within 10 minutes of pressing ON button to boot but this was PM,

Just searching internet and found something on WAASMEDIC issues but that was dated 2017 so appears this is an ongoing problem which MS seem to have lost control of. Looking thru' scheduled tasks, there is an entry for WAASMEDIC which is scheduled to run once every 7 days, in my case at 4:12 am so would then be overdue & runs when I log in normally about 6:30 am every morning (once or twice on secondary PM boot). History of Tasks is only held for 14 days so current  history shows as run on 28th March & 4th April. Have seen no further postings from Microsoft nor people mentioning reporting using feedback hub. Did try once when effects were not too bad but by the time collected my thoughts & refreshed how to submit, it had ended. On another instance was more severe, but as people have reported, how do you do this when the computer is virtually 'frozen'. This time after running for about 4 minutes, it had finished - too late then.  If there were problems at least 3 years ago, MS must know how that was resolved so why not apply that fix - strange how various MS issues seem to keep repeating themselves from time to time. Come on Microsoft sort it out and show some concern for your users.

After not having the waasmedic issue for a week or so all four of the Windows 10 machines I booted today had waasmedic.exe running for quite some time after start up. That's not a coincidence that's planned activity by Microsoft. Some of the systems are up to date with 20H2 and one is still running 2004 becuase I'm afraid to update it now. Some have third party security software and some are just running Microsoft Defender but they have little in common besides Win 10.           

That's why Microsoft is not "fixing" the waasmedic issue they're deliberately causing the issue. Something went wonky with Windows Updates early this year and waasmedic is constantly stuck in a planned loop trying to fix it. Yes you can shut it down from Task Manger but it will just come back. Come on Micro$oft get your act together. Remember, Linux is free and quite frankly a far superior operating system.......