WaasMedic Agent Exe stopping me from working

On my desktop WAAS can literally run the entire day. The entire time the desktop is pausing visibly. It all depends on how many files you have in %APPDATA%. I run a large plex media server and it has lots of files in %APPDATA%. The question for Microsoft is what value does it have to process these PLEX configuration files. There is nothing Microsoft can repair.

Sorry but you are wrong. This happens apparently every week and is totally unrelated to anything the user has done. You may not notice the overhead if your %APPDATA% has relatively few files in it. It's really horrendous overhead when you are running a service like PLEX media server that is serving out a large database of files. Why exactly does Microsoft have to process files that have nothing to do with Windows? %APPDATA% is used by any application for it's configuration data. There is not a thing Microsoft can do to "repair it" so why process it. We really need an answer from Microsoft on this because it is eating our systems alive.

You can disable waasmedicagent via the registry and a reboot. However the service keeps getting enabled (perhaps by windows update). This is truly outrageous in that this service is processing thousands of files unrelated to windows update. When it runs my system literally pauses for 30 seconds at a time! Why is a piece of windows update processing anything unrelated to windows update?

"2) always after starting the machine after forcefully closing down while a background update was running". This is incorrect. I've never "forcefully closed down while a background update was running" on any of my five Windows 10 systems. WaaSMedic runs as a scheduled task. You can check in the task scheduler. Here on all five computers it's set to run every Sunday. The problem is that on some systems it runs for long periods of time reading files in the LCU folder and WinSxS folders and then starts reading personal files. Again you can monitor that activity in the Task Manger. However on this system which has an SSD even with the scheduled run of WaaS it only takes a matter of seconds to run and finish. There is a reason for that and it's just a matter of finding out what that reason is. As for Microsoft getting bashed for "helping" what have they done? Nothing, absolutely nothing. They can't even be bothered to read this thread. The one guy who did respond a couple of times is not an M$ engineer. The WaaS long run time issue started earlier this year not only for me but for most others who are posting in this thread. It is NOT user error it is a BUG most likely introduced in an update earlier this year. Look in Windows>Servicing>LCU and you'll find at least one folder called "Package for Rollup Fix". That indicates something is BROKEN and it's up to M$ to fix that issue. So far they have been unwilling to help in any way.