W10UI v5.4 Added support for multi-versioned updates, to avoid skipping new version if old version already installed e.g. KB4469342 17763.165 & KB4469342 17763.167
It's the third time that I have to do an in place upgrade to be able to install the latest update on Server 2019. No problem in W10 1809, but on Server 2019 everything ends apparently well, the server is updated correctly and works perfectly, but when a new CU update is released, it always fail with Dism error 50. I never saw that behavior before, so I guess there is something connected to the new update format which apparently isn't as rock solid as the older one. If anyone has a clue on that behavior he is welcome.
Reset base after installing a CU? I always do that given I always have an older copy of the vhdx stored somewhere, and rolling back is slower than swapping a vhdx.
Do I need to do that everytime I install CU? I feel like my computer gradually become slower and my disk is becoming full too after every update.
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).