Full resetbase is disabled by default on windows, /startcomponentcleanup is the best way to go, /resetbase broke windows functionality (ResetPC).
hi listen carefully. "Restart your PC" i mean don't shut it down but click restart from start menu. You will see improvement.
Windows gets slower with time as always did because of bunch of reasons, larger caches, more services more, programs on autostart, more fragmented drives and so on. A larger WinSXS should have little impact on speed. But on an installation never reset based, you have each copy of each updated file to allow a rollback, but that also means that you waste a ton of space. Even 4/5 GB on a fairly old version, like Server 2012R2 or Server 2016. In short after a reset base you have an installation which is the same as one made with a Refreshed ISO. You can't rollback, but you recover space. No user data/settings are deleted in the process, unlike what Enthusiast is trying to say.
What i said was: "a full resetbase breaks the resetpc function, that's why MSFT disabled resetbase by default so only /startcomponentcleanup is performed". This is not really news, it's been so since 15063.
Using the full cleanup option If you are completely satisfied that all the installed updates are working correctly, you can use the /ResetBase option and recover a lot more disk space. However, keep in mind that if you run the DISM command with this option, you will be unable to uninstall any updates, patches, or service packs. In other words, there's no turning back. To begin, launch an Administrative Command Prompt window as described earlier. Once the Command Prompt is accessible, enter the following command and press [Enter]: Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase In this command line, the first three options are the same, and the /ResetBase option removes all superseded versions of every component in the component store.
Never used that feature in my life, it may have some use on a tablet or so, surely if you need a refreshed an cleaned install on a Server or a PC is way faster to reinstall from scratch, or to do an in place upgrade keeping the personal files only (or nothing).
iirc, @abbodi1406 said it went even deeper, they disabled it even for winpe images. He has a fix in the W10UI cmd but he also warns about the crippling if the windows functionality ResetPC when /resetbase is used.
Afaik a full reset base was never done automatically right after the the update, for the obvious reason of allowing a rollback from a buggy update. There was (is ?) a scheduled task that did it after a month or so. So I assume that setting affects the disk cleanup behavior, and /or the mentioned scheduled task.
Out of curiosity, did a file comparison between the original and the new revision of KB4469342 (posted by @DiamondMon above). Here's what's different between the two (for x64): These were in the original, but are now removed in the new release: Spoiler: removed Code: amd64_microsoft-windows-dns-server-dnscmd_31bf3856ad364e35_10.0.17763.165_none_5be92152d3db6e86 amd64_microsoft-windows-d..vices-dsrole-server_31bf3856ad364e35_10.0.17763.165_none_9d490347f031ac96 amd64_microsoft-windows-dns-server-wmiprovider_31bf3856ad364e35_10.0.17763.165_none_a5712b297be4c1f9 amd64_microsoft-windows-dns-server-snapin_31bf3856ad364e35_10.0.17763.165_none_0b26559a91098e52 amd64_microsoft-windows-d..-commandline-dsdiag_31bf3856ad364e35_10.0.17763.165_none_c0e1edc783c347e8 x86_microsoft-windows-d..-commandline-dsdiag_31bf3856ad364e35_10.0.17763.165_none_64c35243cb65d6b2 amd64_microsoft-windows-d..aincontroller-setup_31bf3856ad364e35_10.0.17763.165_none_4992575c0533d7f5 x86_microsoft-windows-d..aincontroller-setup_31bf3856ad364e35_10.0.17763.165_none_ed73bbd84cd666bf amd64_microsoft-windows-d..r-commandline-setup_31bf3856ad364e35_10.0.17763.165_none_4078082cedd213ef x86_microsoft-windows-d..r-commandline-setup_31bf3856ad364e35_10.0.17763.165_none_e4596ca93574a2b9 These have been added to the new release (weren't in original): Spoiler: added Code: amd64_microsoft-windows-hello-face-migration_31bf3856ad364e35_10.0.17763.167_none_9bd462622583e32a amd64_microsoft-windows-workstationservice_31bf3856ad364e35_10.0.17763.167_none_40ef01c05c8a1ce9 amd64_product-onecore__mi..-workstationservice_31bf3856ad364e35_10.0.17763.167_none_6568b4ec2c8de0ec amd64_product-coresystems..indows-time-service_31bf3856ad364e35_10.0.17763.167_none_d771cebdb555885b The original had a newer version of one component. Spoiler: older Code: In original: amd64_microsoft-windows-wid-xtp_31bf3856ad364e35_10.0.17763.165_none_4742a0980f9523e8 In new: amd64_microsoft-windows-wid-xtp_31bf3856ad364e35_10.0.17763.107_none_478580b40f62aef0