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
Shouldn't this be 17763.167 & not 17763.107 ? amd64_microsoft-windows-wid-xtp_31bf3856ad364e35_10.0.17763.107_none_478580b40f62aef0
how much impact is there on system performance if we clean the component store regularly... Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore I am experiencing better performance.
That one is .107 in the new release. There's a mixture of versions in theses updates. In the new one, there's .167, .55, .134 & .107. Open the update with 7-Zip or WinRAR and you can see this. The one that bumps the OS build number in the registry to .167 is this one: amd64_microsoft-windows-coreos-revision_31bf3856ad364e35_10.0.17763.167 And, of course, this one needs to be .167: amd64_microsoft-windows-os-kernel_31bf3856ad364e35_10.0.17763.167_none_e0e54b7339db6ddd
Please post benchmark results instead of "feelings". /AnalyzeComponentStore only analyzes the componentstore's content, doesn't clean anything. Code: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>dism /online /cleanup-image /AnalyzeComponentStore Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.167 [===========================99.5%========================= ] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 8.13 GB Actual Size of Component Store : 7.79 GB Shared with Windows : 5.77 GB Backups and Disabled Features : 1.98 GB Cache and Temporary Data : 31.55 MB Date of Last Cleanup : 2018-11-23 01:26:04 Number of Reclaimable Packages : 6 Component Store Cleanup Recommended : Yes The operation completed successfully. /startcomponentcleanup compresses superseded components, /resetbase removes them entirely (as said, that breaks the ResetPC functionality).
Code: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>dism /online /cleanup-image /startcomponentcleanup Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.167 [===== 9.8% ] [==========================100.0%==========================] The operation completed successfully. Re-ran analyze: Code: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools>dism /online /cleanup-image /AnalyzeComponentStore Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.167 [==========================100.0%==========================] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 6.26 GB Actual Size of Component Store : 6.20 GB Shared with Windows : 5.75 GB Backups and Disabled Features : 445.49 MB Cache and Temporary Data : 0 bytes Date of Last Cleanup : 2018-11-30 16:43:57 Number of Reclaimable Packages : 0 Component Store Cleanup Recommended : No The operation completed successfully.
Well I enabled /resetbase from registry. and executed the below command: Dism.exe /Online /Cleanup-Image /StartComponentCleanup /ResetBase recovered about 3 gb space , RS5 17763.167 is performing better , my system startup is quick and especially shutdown speed has improved.
Nothing of the files that got cleaned up has to do with the use of system resources, it's just disk space that gets cleaned up. It won't change boot time nor system speed. And used incorrectly/without warning, it will break system functionality.
you are right i agree. main advantage i got was space freed. but nothing got broke and system is working fine , i don't need any roll back from .167 created a system restore point .
The manual dism command works regardless that setting. I didn't investigate further but likely that setting affects just the scheduled task and / or the disk cleanup tool behavior.