[Giveaway]: Windows 7 Component Store Cleanup Tool (Rebase)

Discussion in 'MDL Projects and Applications' started by harkaz, Apr 1, 2017.

  1. harkaz

    harkaz MDL Novice

    Dec 27, 2012
    42
    85
    0
    #1 harkaz, Apr 1, 2017
    Last edited: Apr 1, 2017
  2. carefully

    carefully MDL Novice

    Apr 23, 2016
    21
    2
    0
    Thanks harkaz for everything.
    Did you ace your big doctor exam ? :)
     
  3. Mr.X

    Mr.X MDL Guru

    Jul 14, 2013
    6,946
    14,623
    210
    Will max reliability be compromised in any way if I don't use it?
    I use to offline integrate updates running Simplix Pack which does not have that rollup... :g:
     
  4. harkaz

    harkaz MDL Novice

    Dec 27, 2012
    42
    85
    0
    #4 harkaz, Apr 12, 2017
    Last edited: Apr 12, 2017
    (OP)
    You're welcome! I have a lot of practical work this year, so the board exams will have to wait a bit longer...


    @MrX: Yes, this cumulative update ensures that everything is on the LDR branch, and there are no mixed GDR/LDR update files in winsxs. I have discovered that the servicing stack cannot always handle properly the compressed files when you have GDR+LDR branch files: sometimes the compressed GDR base file may be used as the active version. This means you'll be running Windows with a system file that is invalid.


    Also, a potential improvement in rebase cleanup: Delete (using the powerrun tool) all superseded driverpacks from C:\WINDOWS\SYSTEM32\DriverStore. They are redundant since you won't be able to uninstall updates and revert to them, but rebase won't auto-remove them.
     
  5. harkaz

    harkaz MDL Novice

    Dec 27, 2012
    42
    85
    0
    It should work with all updates, even in 2018.
     
  6. CEW

    CEW MDL Senior Member

    Jan 21, 2011
    273
    143
    10
    Thank you, useful tool.
     
  7. Tiger-1

    Tiger-1 MDL Guru

    Oct 18, 2014
    5,174
    6,215
    180
    Hi bro thanks for share app+ info :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. bgd2006

    bgd2006 MDL Novice

    Jul 18, 2011
    1
    0
    0
    Thank you
     
  9. Dude Guyman

    Dude Guyman MDL Member

    Jun 20, 2017
    125
    91
    10
    Thanks @harkaz for this! Saved me about 1.3 gigabytes of space. I think it saved me a lot more, like ~3GB on my old install that had lots of individual updates from Windows Updates. This time I had them all right in the ISO before installation, so less for Rebase to do.
     
  10. adric

    adric MDL Addicted

    Jul 30, 2009
    748
    380
    30
    #11 adric, Jul 2, 2020
    Last edited: Jul 2, 2020
    Has anyone used Rebase on an ESU ready system with all June updates?
    I'm wondering how this compares with the cleanup from DISM++

    DISM++ lets you scan before cleaning, which I don't see as an option in Rebase

    Since this thread is a bit old, maybe Rebase has seen its days. :eek:
     
  11. haz367

    haz367 MDL Member

    Jan 11, 2020
    157
    142
    10
    I used it on a offline image (ESU ready // All updates) with default settings...
    The size increases by around 300MB?! Install works fine, and WU working as it should...

    Used DIsm++ Cleanup on a Windows 7 Live OS and after cleanup, WU showing me (again)) the SP1 KB while SP1 is already installed. It must be the cleanuo somehow as it never occurs previously

    Anyhow, thx for the share :)
     
  12. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    31,504
    49,633
    450
    Did you rebuild the wim?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. haz367

    haz367 MDL Member

    Jan 11, 2020
    157
    142
    10
    Hey @Enthousiast

    Yes, i just mount the wim, run the rebase tool (no compress) and then unmount /commit the image using Imagex. The size increases by 300MB's. Did i do something wrong here? After that i cleanup the image using Dism and it shrinked again by 800MB's. Final wim image = 3,62 GB (3.895.765.553 bytes)
     
  14. haz367

    haz367 MDL Member

    Jan 11, 2020
    157
    142
    10
    Running the tool on this install.wim/Online OS, it removes 300MB's
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    31,504
    49,633
    450
    Many servicing commands result in a [deleted] folder inside the install.wim, rebuilding will clean this up, rebuilding is actually exporting the index(es) to a new install.wim, the [deleted] folder inside the wim will be cleaned up, wimlib-imagex optimize will do the same, but a little bit better.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. haz367

    haz367 MDL Member

    Jan 11, 2020
    157
    142
    10
    Ok, so yes i rebuilded/exported the wim...800Mb's, could be a bit more as i didn't use /Compress.

    I just found it weird that the rebase tool increased the size on that offline wim...One should assume it decrease the size right? Then the thing i just noticed when running rebase again on this wim after installing, it cleans up 300MB's. Thx for explaining things as usual :)
     
  17. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    31,504
    49,633
    450
    /compress:recovery (LZMS) you mean? that would result in an install.esd, when the target wim is named install.esd in the export commandline.

    Cleanup-image is not rebuilding.

    As said, servicing can result in a [deleted] folder inside the wim, and its size is added to the total install.wim size, rebuilding/optimizing will clean it up, thus the size should decrease after it ran.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. haz367

    haz367 MDL Member

    Jan 11, 2020
    157
    142
    10
    /Compress:max otherwise need to re-convert it everytime adding updates, system aint that fast....

    Rebuild/Export-image i mean >

    Code:
    dism /Export-Image /SourceImageFile:j:\_wim\install.wim /ALL /DestinationImageFile:j:\_wim\new.wim /Compress:max /CheckIntegrity
    It works as it should obvioulsy (my bad...) It creates a [DELETED] folder of 2GB in size. Unmount /commit makes it a little bigger then the original wim. Then cleanup > export-image rebuilds /cleans the wim from 4.15GB >> 3.32GB. Very nice :)

    After installing the (other) wim, it removed another 300MB. Testing this jan2020 image later to see if it removes some more mb's using -online

    It works so fine on Windows 10, great little tool for 7 :)
     
  19. haz367

    haz367 MDL Member

    Jan 11, 2020
    157
    142
    10
    This indeed rebuilds it a bit better
    Code:
    wimlib-imagex optimize j:\_wim\install.wim --check --recompress
    3,25 GB (3.498.901.355 bytes)

    vs
    Code:
    dism /Export-Image /SourceImageFile:j:\_wim\install.wim /ALL /DestinationImageFile:j:\_wim\new.wim /Compress:max /CheckIntegrity
    3,32 GB (3.575.132.668 bytes)