New
#70
Confirm NMI and Mike's comment on ResetBase. Use it without issues.
Hi @f14tomcat
Can you or anyone share me a cmd script like this
step 1: Check whether DISM is required or not:
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
If there is nothing to clean up then to user input/option will show for DISM cleanup
If recommended then user selection required input 1 or 2
1. For DISM Cleanup Command: Dism.exe /online /Cleanup-Image /StartComponentCleanup
2. For DISM +ResetBase: Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
Hello,
the "Windows Update Cleanup" (Disk Cleanup/Clean up system files) does exactly the same as the dism command - right?
At least the "The following actions will be performed" part in the cbs.log is identical.
Nevertheless on my machine the execution from the gui takes distinctly longer then with the dism command - is this normal?
With 21H2 "/ResetBase" does its thing (according to the cbs.log) regardless of "DisableResetbase" setting.
Has the behavior changed?
Besides that... I don't get the difference.
Without "/ResetBase" "updated components" are deleted, with the switch "superseded versions".
Is that not the same? Can someone please enlighten me?
Many thanks and greetings
Martin
Last edited by mfessler; 09 Aug 2022 at 22:37.
Howdy!
It has been a while, so I hope you're all doing great despite the circumstances!
I need some help for an issue that has been bugging me for some time now. Windows is haunting me with updates already installed and my ESET SSPbeta keeps warning me.
Checking System with DISM. Is it useful/related with these KB's knocking on my door, even when already installed?
Microsoft Windows [Version 10.0.19044.1949]
(c) Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>Dism /online /cleanup-image /AnalyzeComponentStore
Deployment Image Servicing and Management tool
Version: 10.0.19041.844
Image Version: 10.0.19044.1949
[===========================99.2%========================= ]
Component Store (WinSxS) information:
Windows Explorer Reported Size of Component Store : 7.47 GB
Actual Size of Component Store : 7.23 GB
Shared with Windows : 3.94 GB
Backups and Disabled Features : 3.29 GB
Cache and Temporary Data : 0 bytes
Date of Last Cleanup : 2022-09-09 17:07:42
Number of Reclaimable Packages : 4
Component Store Cleanup Recommended : Yes
The operation completed successfully.
C:\WINDOWS\system32>
Thanks in advance, directions much apprecated.
Cheers
m4v3r1ck
- macOS 10.14.6
- VMware Fusion Professional Version 8.5.1 (4543325)
- Windows 10 Pro x64 21H2 OS Build 19044.1949
Hello @M4v3r1ck,
If you haven't already, you could see if resetting Windows Update using the method below may be able to help.
Reset Windows Update in Windows 10
Hello @M4v3r1ck,
Have you looked at this ? . . .
> How to Reset Windows Update in Windows 10
Also, have a look at the Related Tutorials at the BOTTOM of the above Tutorial [ there are a few ], as they may also be related.
I hope this helps.
Previous annual Windows updates were like a repair install and pruned the size of the Widows directory. This type of update hasn't happened for a while. I could use the command Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase. How much space would this likely save and is there any penalty apart from not being able to roll back a previous update?
ResetBase was disabled (it can break updates) and even if you enable it via registry, it is supposedly not working.
Windows 10 Hotfix Repository | Page 622 | My Digital Life Forums