WaasMedic Agent Exe stopping me from working

Microsloth wants to sell the idea that WaasMedic is all about insuring the integrity of Windows Update.  This appears to be a bald-faced lie.

WaasMedic just stopped running, 4 hours after initial boot-up when it apparently installed "KB4023057: Update for Windows 10 Update Service components".  But here is the problem: It was bogging down my email (Thunderbird) and browser (Firefox) making them "click-go-get-coffee-while-waiting-for-response" operations.  In Resource Monitor, Disk tab, Disk Activity pane there were several hundred lines of WaasMedic entries listing almost exclusively non-Microsloth, non-Windows OS files being read from / written to.   The files ranged from applications like Rosetta Stone to Thunderbird and Firefox an numerous other applications I have installed.  Many were in "Program Data" but it was not limited to that directory.   It was also accessing cache files for some programs and even a directory called "deleted Apps".

This strengthens my opinion that WassMedic is being used to enforce removal of non-Microsloth applications they don't want you to run whether you want to or not, and whether they are actually compatible with Windows or not.  (e.g. Flash, removal of which now prevents me from having full use of the scanner function of my older AOI printer).

So Microsloth is not being honest when they maintain the point of WaasMedic is to fix / insure the integrity of Windows Updates.  If that were the case, they would have no need to access hundreds of files that belong to third-party applications, bogging down those applications in the process.

Again you're just not getting the problem. The problem is not that WaasMedic is running it's the fact that it's running for so long and so often. On my i7 8700K system it ran for over 13 minutes at or near 100% disk. Sometimes at over 8 megabytes per second. Even if we say that it averages 2 MB/sec for 13 minutes that's over 1.5 GIGS of disk activity. For what ? Then today it started to run again and after 3 minutes I simply did an End Task but had to do a restart to keep the rest of Winbloats tasks from grinding away at my hard drive. After the restart everything was fine. That system has no third party AV, no third party browser and only a handful of audio apps installed and it needs to run at maximum efficiency in order not to get under runs and audio degradation. People who only use their computers to surf the net or check e-mails may not even notice the problem but those of us who do system intensive work like audio or video production do notice. 

I am afraid that is NOT going to help those users with systems already broken by previously applied updates, and NONE of those things you mention will stop WaasMedic from hogging system resources, that this thread post is all about! This is something that Microsoft need to fix, as many frustrated posters have said on here!

Yes, this is related to windows updates. 

Answer:  go to your search bar and type in "updates" / go to windows updates settings / select Pause Updates for 7 days/  then change your active hours to 1 hour before you expect to use your computer every day and 1 hour after you expect to be finished for the day.  

(desktop users only ) 

Next in power settings select sleep never.

Next just don't ever power down your computer and it should update at off hours time when you are not using the computer.

I know this is not a perfect fix but it will let you get working again. 

Cheers