ResetBase on Windows 7

AeonX said:
I think that to completely clean WinSxS it is necessary to install the system in audit mode to complete the pending operations (pending.xml in WinSxS) caused by the updates after doing sysprep and capturing the image again into install.wim.
Click to expand...
That would be incredible if true. Will try. Thanks!
 
nuhi im getting leftovers after stripping out winsxs on a captured wim. i disable all compatibilities and set "disable protections" to true. v2.0.0.7656_x64.
Windows Component Database still appears on reload. grab is the processed image extracted. cant upload the captured wim :(.

edit, tried running elevated with power run, still the same.

Capture.JPG
 

Attachments

  • test.7z
    9.4 KB
Last edited:
tharri will need to see what nuhi says to my post above before i can proceed any further.
i have seen winsxs with very few folders before(moons ago) after ripping out winsxs. need to check this isnt pebkac before i scream bug.
 
Clanger said:
nuhi im getting leftovers after stripping out winsxs on a captured wim. i disable all compatibilities and set "disable protections" to true. v2.0.0.7656_x64.
Windows Component Database still appears on reload. grab is the processed image extracted. cant upload the captured wim :(.

edit, tried running elevated with power run, still the same.

View attachment 4068
Click to expand...
If Component Database was removed in an earlier session, size won't change, no further removals are supported after that.

That said, will test Win7 WinSxS Store removal on a full updated ISO and report back, thanks for the feedback to all.
 
nuhi, the captured image was a default iso, updated with intel usb3 driver into boot and install wim, no tweaks or removals, updated post install with kb3125574, ie11 and net 4.8, sysprepped then captured, no wimscript used, only gimagex's own default settings. install not cleaned up or modded in anyway manually or by ntlite or any other tool. i tried to upload the captured wim to media fire, 5 hours to upload 1.7gb of a 5gb plus wim file :(. not in any rush at all :) , just helping tharri at this stage but will be doing a full wotsit for myself later. :)

if you would prefer my wim to remove any variables i could upload it for you, it will take a while though :rolleyes: :D

edit - i dont like to process the image more than once(except for adding a needed driver like usb), i do all the hocus pocus at the end :)
 
Last edited:
nuhi while i think of it, X:\Recovery was present but empty(removed component) and there were a number of empty folders in winsxs.
 
OK, replicated and fixed for the next version. It was an overblown protection for IE in Win7 due to some old fix.
I removed just WinSxS (remains ~300MB) and no issues installing that otherwise full Win7 ISO.
We'll see if the old bug from 2019 resurfaces after this but I don't see how, tested with all the updates integrated and intentionally triggered all of the feature configs enable/disable in that one session.

Will release the fixed version these days, trying to finish up something else first, latest by Tuesday.

Thanks.
 
OK, could you clarify what you are fixing? Was it, in fact, not working as it should have? Will the new version remove more of (if not all) the WinSxS folder?
 
windows doesnt report the actual size of winsxs for "reasons", its not as big as you think it it. clean windows update will clean the superceeded files.
 
tharri said:
OK, could you clarify what you are fixing? Was it, in fact, not working as it should have? Will the new version remove more of (if not all) the WinSxS folder?
Click to expand...
Yes, the main issue in this topic is the WinSxS (Component Store) removal not removing enough in Win7, as far as I understood.

Next version will leave only ~300MB of it on full Win7 SP1 updated ISO after removal of that component, there was gigabytes of accidental leftovers since the overreacted fix - you can see the results of the fix on the public version by removing Internet Explorer (64-bit) at the same time, then that issue won't trigger.
Next version will be able to keep IE and still remove WinSxS.
 
Clanger said:
nuhi nice one :) hope it wasnt too hard to find. bug from 2019? doesnt ring a bell. next week is good for me, will run the fix and report :)
Thank You :) tharri
Click to expand...
IE wasn't registering after setup, throwing an error if WinSxS removed in Win7 image only.
Now I cannot replicate the issue, the underlying issue must have been fixed better by now with constant improvements...or someone will come with a preset that proves it wrong but I'll then invest more time in filtering what is needed, not keep too much like last time.
 
nuhi thank you :) . i am 99% certain an (really)old version only left something like 4 folders(for some reason i have 4 in my head) in winsxs. i think i know which version it was and i might still have it, if i have i will tinker and pm the findings.
 
Last edited:
nuhi said:
Next version will leave only ~300MB of it on full Win7 SP1 updated ISO
Click to expand...
After working with LTSC i now find 6gb installed acceptable. using the preset i uploaded and removing Natural Language tool is showing 6.2gb installed. if you eastimate 300mb left i estimate 5.7gb, very acceptable :). if i add a full c++ pack i reckon back to 6.2gb.

Updated install(no removals, just update cleanup) is usually around 7.2gb.
 
Before and after. a bit more than 4 but not too far off.
i have attached the preset used, all compatibilities Disabled, DisableProtections>true in settings.xml.

Capture01.JPG Capture03.JPG
 

Attachments

  • W7-EOL-WINSXS-TEST.xml
    18.6 KB
Last edited:
amazing, i used the pre-set and it worked for me. thanks

question... I have a software that needs to install .Net 3.0 Framework, but cant using this preset... its having trouble. what settings do i need to override on this preset to be enable to install .NET 3.0? thanks
 
You must log in or register to reply here.
Back
Top