WaasMedic Agent Exe stopping me from working

@MarcHoppe - so saying that "Windows is a bloated pig of a data collection system disguised as an operating system" will help this post and users? Why not spend some time using Marc Russinovich's "procexp"  to check out what your WaasMedic process is doing next time it happens, and reporting your results. Now THAT could prove very useful.

As regards a "fix", only Microsoft can do that, unless someone happens to find a "magic bullet" of a registry tweak that MIGHT help in some cases. Basically, we are all waiting on Microsoft. If you DO find anything useful, try putting that into the Feedback Hub.

I am NOT trying to defend Windows 10 and updates, I have had my fair share of issues over time, I was just pointing out WHY it (and big updates) may seem bloated, so I do rather object to your over aggressive and slightly rude response on here.

It's items not files but did I say 46,000 files is a lot ? Of course it's not in comparison the whole Winbloat package. Try looking at the contents of those folders. Anyway you're missing the point. I was reporting the "Package for Rollup Fix" which may be related to the WaasMedic problem people are reporting here. If you're just going to blindly defend Windows then don't bother. I've run several Linux distros and currently have three running so I know that Windows is a bloated pig of a data collection system disguised as an operating system. We're trying to figure out the WaasMedic problem. If you're not willing to help then stay out of it.

Endless updates. Day after week after month after year. 

Are we supposed to believe all of this is for OUR benefit? 

The tech tyranny. The ugly monopoly.

Constant, unceasing, repetitive "updates" just for OUR benefit, we the people. 

What nonsense. 

My machine no longer names waasMedic. A layer of disguise has been added. 

What schlock.

@MarcHoppe So, you think that 46,000 files is a lot? See:

https://docs.microsoft.com/en-us/troubleshoot/windows-client/deployment/standard-terminology-software-updates

Update rollup:

A tested, cumulative set of hotfixes, security updates, critical updates, and updates that are packaged together for easy deployment. 

Monthly Rollup:

A tested, cumulative set of updates. They include both security and reliability updates that are packaged together and distributed over the following channels for easy deployment:

• Windows Update
• WSUS
• System Center Configuration Manager
• Microsoft Update Catalog

The Monthly Rollup is product-specific and addresses both new security issues and nonsecurity issues in a single update. It will proactively include updates that were released in the past.

Now the update system will not know exactly what "hotfixes" or out-of- band 

updates you may have installed prior, so these will include ALL updates "rolled up" from the previous major update onwards

(e.g. those AFTER 20H1 or 20H2 whatever). Hence the growing size over time until the next feature update.

 So although it might appear "overblown", those items ALREADY at the correct level/version will NOT be applied or updated, it goes to the next item and so on. 

As regards the SIZE of the whole product "OS Release" itself, 

you have to realise that Windows 10 has to work with THOUSANDS of different PC/Laptop configurations from many manufacturers, many with

add-in extra expansion cards and peripherals. When you addin the mix of the many AMD and Intel processors out there that it has to support,

IMHO - it does an AMAZING job of getting that configured and bootable! Apple INC has it easy with their "locked down" systems!

But, although there may be a few MILLION files in the whole released product to get that to happen,

your typical configuration might only have about 250K worth of "files" in the actual OS that is booted (with DLL's and XML, param INF files etc).