New
#940
After Version Upgrades.bat
fsutil resource setautoreset true c:\&fsutil usn deletejournal /d /n c:&Dism.exe /online /Cleanup-Image /StartComponentCleanup&sfc /scannow&Dism.exe /Online /Cleanup-Image /RestoreHealth&sfc /scannow&Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase&winsat formal&pause
Basically it cleans up the component store(WinSxS) of old uneeded .dll, .exe portions of API's, and other cruft, checks your system for missing Windows files & folders, replaces them if possible, and the does Winsat, which runs test on your hardware, so Windows can make adjustments to it's under the hood settings, like it check how fast your drives are, to see if they're HDD or SSD and can the select defragmenting or retrim, it test your CPU so Windows can set processor affinity's and priorities, and so on.
All this gets done by auto maintenance, but after an upgrade, if it goes well, I like to run Windows Update Cleanup, and that batch file, just to get rid of the leftovers & cruft of the last build.,
Note that one of the DISM commands uses the /ResetBase option. This maximizes the amount that can be removed, but also sets your baseline build to your current build. It will no longer be possible to uninstall any previous update. If you're not comfortable with that you could always leave that command out. It will still make a significant reduction in the size of WinSxS, juts not the maximum possible.
So I hopped onto the insider ring, installed 16299.19, then hopped off. Come tomorrow, will I continue to get regular, non-insider updates like normal?
Don't know. Please let us know what happens, I'm very interested. I also have 16299.19 and have Insider Fixes, apps and drives active for now. I will get out of Insider tomorrow after the Fall Creators Update has been released. I'm hoping that will put me back to the normal update stream.
Tweet
— Twitter API (@user) View on Twitter