Windows 8 and 8.1 Forums


Windows Update Cleanup in Windows 8

  1. #1
    Windows Update Cleanup in Windows 8

    Windows Update Cleanup in Windows 8
    How to Use Windows Update Cleanup in Windows 8 and 8.1
    Published by Brink is online now
    10 Apr 2014
    Default Windows Update Cleanup in Windows 8

    Published by


    Brink's Avatar
    Administrator

    Join Date: Jul 2009
    Posts: 22,576

    How to Use Windows Update Cleanup in Windows 8 and 8.1


    information   Information
    Windows Update Cleanup is an option in Disk Cleanup that you can use to have Windows automatically delete Windows updates that you no longer need to free up hard drive space.

    This tutorial will show you how to use Windows Update Cleanup to delete outdated Windows updates from the WinSxS folder (component store) to free up hard drive space in Windows 8 and 8.1.

    You must be signed in as an administrator to be able to do the steps in this tutorial.

    Note   Note
    The Windows Update Cleanup option is available only when the Disk Cleanup wizard detects Windows updates that you do not need on the computer.

    To let you roll back to previous updates, updates are stored in the WinSxS store even after they are superseded by later updates. Therefore, after you run the Disk Cleanup wizard, you may be unable to roll back to a superseded update. If you want to roll back to a superseded update that the Disk Cleanup wizard deletes, you can manually install the update.




    Here's How:

    1. Press the Windows+R keys to open the Run dialog, type cleanmgr, and press Enter.

    2. If you have more than one hard drive, select the C: drive, and click/tap on OK. (see screenshot below)

    Name:  Windows_Update_Cleanup-1A.jpg
Views: 38125
Size:  13.2 KB

    3. Click/tap on the Clean up system files button. (see screenshot below)

    Name:  Windows_Update_Cleanup-1.jpg
Views: 38568
Size:  84.4 KB

    4. If prompted by UAC, then click/tap on Yes.

    5. If you have more than one hard drive, then repeat step 2 above.

    6. Check the Windows Update Cleanup box, and click/tap on OK.

    NOTE: Notice how much space disk space you will gain. This can be GBs.

    Name:  Windows_Update_Cleanup-2.jpg
Views: 38430
Size:  81.7 KB

    7. Click/tap on Delete Files to confirm. (see screenshot below)

    Note   Note
    If you like, you can view the details of what will be deleted listed in the dism.log below before clicking on "Delete Files".

    %SystemRoot%\Logs\DISM\dism.log


    Name:  Windows_Update_Cleanup-3.jpg
Views: 37956
Size:  20.2 KB



    That's it,
    Shawn


  2. #1


    Posts : 20
    Win 7 Pro, Win 8.1 Pro x64


    Hello Shawn, I have a couple of questions/issues regarding WU cleanup on Win 8.1 - in Windows 7 there is a way to check for & see what packages are queued for deletion/cleanup in a log called "deepclean.log" as described here by UsernameIssues... there appears to be no such log in 8.1 nor is there any reference to "adding" package(s) in the cbs.log. Is there another/different log/output in Win 8.1?

    The other issue is WU Cleanup itself... it has been "running" a VERY long time and the progress bar is only at around 40%. Is this normal/to be expected? Please edumacate me as I have installed & been using 8.1 for only 2 days & am still feeling my way around so to speak.

    Edit to add: Cleanup finally completed after about 35 minutes and here are the pertinent entries in CBS.log:

    Code:
    2014-11-14 04:45:17, Info                  CBS    Maint: Deepclean: Trying to uninstall package Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4
    2014-11-14 04:45:17, Info                  CBS    Appl: detect Parent, Package: Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, Parent: Microsoft-Windows-Client-Features-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~6.3.9600.16384, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present
    2014-11-14 04:45:17, Info                  CBS    Appl: detectParent: package: Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, parent found: Microsoft-Windows-Client-Features-Package-AutoMerged-admin~31bf3856ad364e35~amd64~~6.3.9600.16384, state: Installed
    2014-11-14 04:45:17, Info                  CBS    Appl: detect Parent, Package: Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, disposition state from detectParent: Installed
    2014-11-14 04:45:17, Info                  CBS    Appl: Evaluating package applicability for package Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, applicable state: Installed
    
    2014-11-14 04:46:43, Info                  CSI    0000000e@2014/11/14:09:46:43.491 CSI Transaction @0xca6e085b00 destroyed
    2014-11-14 04:46:43, Info                  CBS    Perf: Stage chain complete.
    2014-11-14 04:46:43, Info                  CBS    Perf: Execute chain started.
    2014-11-14 04:46:43, Info                  CBS    Perf: Entering stage: Install/Uninstalling
    2014-11-14 04:46:43, Info                  CBS    Exec: Not trying hotpatching because root package is not hotpatch-aware: Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4
    2014-11-14 04:46:43, Info                  CSI    0000000f@2014/11/14:09:46:43.491 CSI Transaction @0xca6e085b00 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [79]"TI4.30408686_2642874344:4/Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4"
    
    2014-11-14 04:46:43, Info                  CBS    Exec: Uninstall package: Package_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4
    2014-11-14 04:46:43, Info                  CBS    Exec: Uninstall package: Package_for_KB2918614_RTM~31bf3856ad364e35~amd64~~6.3.1.4
    2014-11-14 04:46:43, Info                  CBS    Exec: Uninstall package: Package_for_KB2918614_RTM_GM~31bf3856ad364e35~amd64~~6.3.1.4
    2014-11-14 04:46:43, Info                  CBS    Exec: Uninstall package: Package_2_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4
    2014-11-14 04:46:43, Info                  CBS    Exec: Uninstall package: Package_2_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, Update: 2918614-2_neutral_GDR
    2014-11-14 04:46:43, Info                  CBS    Exec: Unprojecting Package: Package_2_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, Update: 2918614-2_neutral_GDR, UninstallDeployment: amd64_d5aa9cc7683e94407683e8913b572e15_31bf3856ad364e35_6.3.9600.17198_none_e562adfcccf7feee
    2014-11-14 04:46:43, Info                  CBS    Appl: Selfupdate, Component: amd64_microsoft-windows-installer-handler_31bf3856ad364e35_0.0.0.0_none_5ed31a4d4c573af1 (6.3.9600.17399), elevation:5, lower version revision holder: 6.3.9600.17198
    2014-11-14 04:46:43, Info                  CBS    Exec: Unpinning Package: Package_2_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, Update: 2918614-2_neutral_GDR, UnpinDeployment: amd64_d5aa9cc7683e94407683e8913b572e15_31bf3856ad364e35_6.3.9600.17198_none_e562adfcccf7feee
    2014-11-14 04:46:43, Info                  CBS    Exec: Uninstall package: Package_2_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, Update: 2918614-3_neutral_GDR
    2014-11-14 04:46:43, Info                  CBS    Exec: Unprojecting Package: Package_2_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, Update: 2918614-3_neutral_GDR, UninstallDeployment: amd64_798a95ad7ef569bbd66328a75afed2c1_31bf3856ad364e35_6.3.9600.17198_none_74a2588e9328b4df
    2014-11-14 04:46:43, Info                  CBS    Appl: Selfupdate, Component: amd64_microsoft-windows-installer-engine_31bf3856ad364e35_0.0.0.0_none_83730f5cb40c6c6d (6.3.9600.17278), elevation:4, lower version revision holder: 6.3.9600.17198
    2014-11-14 04:46:43, Info                  CBS    Appl: Selfupdate, Component: amd64_microsoft-windows-installer-engine_31bf3856ad364e35_0.0.0.0_none_83730f5cb40c6c6d (6.3.9600.17399), elevation:5, lower version revision holder: 6.3.9600.17278
    2014-11-14 04:46:43, Info                  CBS    Exec: Unpinning Package: Package_2_for_KB2918614~31bf3856ad364e35~amd64~~6.3.1.4, Update: 2918614-3_neutral_GDR, UnpinDeployment: amd64_798a95ad7ef569bbd66328a75afed2c1_31bf3856ad364e35_6.3.9600.17198_none_74a2588e9328b4df
    
    (There are many more entries for KB2918614, packages 2, 3, 4 etc which were removed)
    
    2014-11-14 04:46:46, Info                  CBS    Maint: Deepclean: packages removed: 1
    
    2014-11-14 05:20:50, Info                  CBS    Maint: end scavenge, scavenge time so far: 2001 seconds
    So my second question still remains; Is this a "normal" amount of time for WU cleanup to run?
    Last edited by Urthboundmisfit; 14 Nov 2014 at 05:48.

      My System SpecsSystem Spec

  3. #2


    Posts : 22,576
    64-bit Windows 10


    Hello Joe,

    The amount of time it takes to cleanup Windows Update depends on how much it needs to clean up and how fast your system is, but yeah it could easily take that long with large GB amounts.

    I see it listed in the "%SystemRoot%\Logs\DISM\dism.log" for Windows 8.1, but it seems that there's not a "%SystemRoot%\Logs\CBS\DeepClean.log" anymore.
    Last edited by Brink; 14 Nov 2014 at 10:08.
      My System SpecsSystem Spec

  4. #3


    Posts : 20
    Win 7 Pro, Win 8.1 Pro x64


    Thank you for confirming, Shawn. This was the initial scan after fresh install & about 80 or so updates, I imagine subsequent cleanups should be speedier, no?

    I have 7 installed on my SSD & I am testing Win 8.1 on the (slower 5400 rpm) HDD that came with the laptop, eventually will dual boot 7 & 8.1 on the faster SSD.
    Last edited by Urthboundmisfit; 16 Jan 2015 at 10:32.
      My System SpecsSystem Spec

  5. #4


    Posts : 22,576
    64-bit Windows 10


    Yeah, it should be quicker next time with not as much to clean. The slower HDD would have slowed it down some as well.
      My System SpecsSystem Spec

  6. #5


    When should I run Windows Update Cleanup?
      My System SpecsSystem Spec

  7. #6


    Posts : 22,576
    64-bit Windows 10


    Quote Originally Posted by williamsjesse17 View Post
    When should I run Windows Update Cleanup?
    There's really no set time when you should since it's basically just optional maintenance to help free up hard drive space if needed.

    However, I'd say that after you have installed a batch of Windows Updates and sure that you won't need to uninstall them after a week or so, that would be a good time.
      My System SpecsSystem Spec

  8. #7



    Trying to Sith things out
    Bamberg Germany
    Posts : 2,290
    Windows 10 Pro 64 bit


    To pimp Disk Cleanup a bit
    ---------------------------------
    To clean more using windows Disk Cleanup:

    Right-click Windows icon>choose Run> then type:
    Code:
    cleanmgr.exe sageset:10
    Press Enter
    In the window that appears - click Clean up system files
      My System SpecsSystem Spec

  9. #8


    Quote Originally Posted by Cliff S View Post
    To pimp Disk Cleanup a bit
    ---------------------------------
    To clean more using windows Disk Cleanup:

    Right-click Windows icon>choose Run> then type:
    Code:
    cleanmgr.exe sageset:10
    Press Enter
    In the window that appears - click Clean up system files
    Cliff, what do you mean by this?
      My System SpecsSystem Spec

  10. #9


    Posts : 22,576
    64-bit Windows 10


    That command opens an extended Disk Cleanup with more options.
      My System SpecsSystem Spec

Page 1 of 3 123 LastLast
Windows Update Cleanup in Windows 8
Related Threads
I'm running 8.1 with all updates on, supposedly. In Control Panel, Troubleshooting, System & Security, Fix Problems with Windows Update, Advanced, Run as Administrator: It says it fixed the problem (whatever that may be). I rerun it. It says it fixed the problem. This goes on ad infinitum. It...
Windows Update Cleanup in Windows Updates & Activation
I got Glary Utilities Pro for Xmas.{$11} I saw Windows Update as something to be cleaned. I ran the cleanup of everything & it only took a few sceonds. I emailed Glary & asked if their Windows Update cleanup was the same thing as in Disk Cleanup in Windows. They said yes. They said it...
Well, as the title suggests, I'm having an issue with Disk Cleanup with a new SSD I recently purchased. In all my years with HDDs I never had this problem. I've been running Windows 8.1 with an HDD for over a year now with no such problem so this is quite new & odd to me. The Windows Update Cleanup...
About windows update cleanup in Performance & Maintenance
Hi its my first time to run windows update cleanup on my laptop. after analyzing i could get 1gb+ free space then i run it then i notice that it so slow its been 3 hours now then i should worry now coz my laptop fan hits 100% think so and laptop gets hot so i cancelled it then ive start then it...
Hi guys, I've been troubleshooting my MSI Laptop GE40 for quite awhile now, but I am just unable to find a solution online. My laptop is running Windows 8.1, I was doing some cleaning up for my laptop using Disk Cleanup. After running Disk Cleanup (With System Files), Windows Update files...
I've had this desktop for 10 months now. OEM purchase with 8.0, immediately upgraded to 8.1 and have applied all updates to date including the ones today. Never had any significant issues. I have a 1T HDD with over 820G free space and will probably never use half of that. Freeing up disk space...
I had to reinstall Windows 8 Pro x64. After installing all available Window Updates I ran Disk Cleanup. The Windows Update Cleanup entry showed about 1GB of stuff. After the cleanup ran, with no apparent problems, I have 28.0MB that always shows up. Cleaning this does nothing, the 28.0MB...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook