Resetbase can only be utilized in windows 8 and above. I would strongly urge not to use this command. It does not shrink the footprint of windows on the contrary it has the opposite affect. If one uses NTlite for a customization of windows install using resetbase will return all the removed components and you would most likely be looking at a fresh install.
ResetBase on Windows 7
- Thread starter Bournesup
- Start date
Think of resetbase as the default component store in the winsxs folder. When resetbase is initiated it will talk to micrsoft update to ensure that the base components are stored in the winsxs folder. The smartest way to remove all superseded components is to use the cleanmgr tool.
Initiate cmd.exe (adm mode) and type the following command (cleanmgr sageset:50). The value of 50 is just an arbitrary number use anything you like. Check all the boxes then close cleanmgr. Next type the following command in the cmd window.
Cleanmgr sagerun:50; This command will remove all superseded updates and remove redundancy in the winsxs folder.
I stopped using the ntlite's cleanup; Let windows OS do the work for you it is safer.
Initiate cmd.exe (adm mode) and type the following command (cleanmgr sageset:50). The value of 50 is just an arbitrary number use anything you like. Check all the boxes then close cleanmgr. Next type the following command in the cmd window.
Cleanmgr sagerun:50; This command will remove all superseded updates and remove redundancy in the winsxs folder.
I stopped using the ntlite's cleanup; Let windows OS do the work for you it is safer.
If you host refresh, you should import preset as well. Host refresh does not reset the winsxs folder if you imported the preset for a custom install. The updates that are applied are cumulative. And you should run cleanmgr as I described above to clean the winsxs folder afterwords.
I'm not sure but I think Disk Cleanup is equivalent to the command Dism /Online /Cleanup-Image /StartComponentCleanup (without the /ResetBase switch) so it doesn't remove the superseded components but does a delta-compress. And even with the /ResetBase switch this will not be effective since ResetBase was disabled in Windows 10 from version 1607 onwards:
https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-209#post-1356912
Therefore to make the ResetBase effective it is necessary to make the reg tweak mentioned in the link above. This is the same tweak that NTLite uses to enable ResetBase and is the subject of the first post on that topic.
NTLite's Cleanup is similar to ResetBase but much faster and removes more things but is probably less compatible and can occasionally cause problems with Windows Update.
ResetBase breaks the Reset PC feature so maybe that's why Microsoft has disabled it.
From version 1903 onwards ResetBase breaks future cumulative update installations as well. But in this and other newer builds it is no longer necessary to do the ResetBase for cumulative updates but it is necessary for the other updates. More details can be found here:
https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-419#post-1532957
So if Windows Update is important you can't use ResetBase in version 1903 and newer ones instead use the normal cleanup that will compress the superseded components (it won't make much difference since the other updates are relatively small).
So resetbase doesn't work in Windows 7? How on earth do those TeamOS guys get their 64-bit Windows 7 Pro iso's down to 750mb then? I saw one with just 39 folders in the winsxs folder. My full install with a dozen updates has over 9000 -- and that's after doing the update cleanup / remove reinstalls.
I couldn't believe it would work but it did. The final installed Windows folder on a vm was a little over 2gb -- and 4 different spyware, malware, and virus checkers found no issues whatsoever. I'm still afraid to use it though. I want to learn how to do what they did.
I couldn't believe it would work but it did. The final installed Windows folder on a vm was a little over 2gb -- and 4 different spyware, malware, and virus checkers found no issues whatsoever. I'm still afraid to use it though. I want to learn how to do what they did.
tharri i have got windows 7 64bit installed at 1.16 or 1.26gb installed(confirmed) which would be close to 750mb as an iso. i did barebone the boot.wim aswell, but that was a long time ago and nuhi has added a lot more removals since then. only worry about iso when buring it to cd/dvd. Final Installed Size is what matters most.
if i am correct i did get a w7 pro(ult?) 64bit iso to just under 600mb(or maybe a bit over but it would fit on a cd) which is practically the same size as an xp pro 32bit iso.
if i am correct i did get a w7 pro(ult?) 64bit iso to just under 600mb(or maybe a bit over but it would fit on a cd) which is practically the same size as an xp pro 32bit iso.
Last edited:
That's what I don't understand. I wish the component list had more details about the size of the components removed. Many of the components have no information about the size, so it's often difficult to tell if removing a component is worth it or not. I just know that I've tried to make a minimal, but still usable for gaming, Windows 7 iso and I can't get it even close to 2gb.
Thanks for the offer, but it would be too much of a pain for both of us. For gaming compatibility, I have to use about 12 updates. It's also not consolidated into one preset. My work typically involves doing several presets separately (I've run into problems when combining them), installing and booting in system audit mode, adding .NET 4.8, Visual C++ redistributables, drivers, and DirectX, recreating the wim, and them trimming fat with DISM++ and the cleaning functions in NTLite. I know .NET 4.8 adds around 1gb, and that other stuff adds a few hundred megabytes. I just feel like it could be a lot smaller.
ResetBase is done by Dism an official Microsoft tool and was only implemented from Windows 8 onwards. They must have used NTLite's update cleanup which manually removes files without relying on Dism which is why it is possible to remove backups of updates on Windows 7. In addition they removed the Component Store (WinSxS) so there are so few folders left in WinSxS.
This is the best thing to do. Not only because of the risk of malware but also because this ISO was probably made to meet the needs of those who made it and may not be suitable for your use. If they removed the support for printing and bluetooth for example and you need these things you will have a useless OS. Some people apply tweaks found on the Internet blindly without worrying about the consequences and can end up with a less stable OS and even worse performance.
More important than image size is usability, stability and performance. You can sacrifice size a little for more usability and stability with optimized performance. For me if it has the best performance I don't care much about the size of the image.
the ntlite "clean update backup" is different for w7. ive got a sysprepped install on a offline drive that i need tocapture again, i mislaid the original . it has 3125574, ie11 and net 4.8. i'll post before and after screen shots.
ive said it before and i will say it again, there is no 1 size fits all approach in this lark. you have to cherry pick other peoples work. and aiming for Xmb/gb isnt the way to go about get, its like children, you get what you are given and am grateful. if i get 5 to 6gb on any os, latest ie and nets i amhappy. stopped caring about size long ago.
. it has 3125574, ie11 and net 4.8. i'll post before and after screen shots.ive said it before and i will say it again, there is no 1 size fits all approach in this lark. you have to cherry pick other peoples work. and aiming for Xmb/gb isnt the way to go about get, its like children, you get what you are given and am grateful. if i get 5 to 6gb on any os, latest ie and nets i amhappy. stopped caring about size long ago.
That's what I don't understand. I remove the Component Store with NTLite and there are still over 8000 folders in my WinSxs folder, not 40. It drops the total size of that folder from about 4.8gb to 3.8gb. Is that a bug?