already tried against 26100.863 iot ltsc and works very well theres much more packaged in as far as i remember around 2000. if you remove for example hyper-v thats lots of packages already, reboot run resetbase you likely will get error open cbs enum and again remove some remnants of hyperv then resetbase error will go away. also issues like dont remember what i removed exactly maybe something to do with defender but whatever i removed makes windows update not installing updates showing error. or maybe it was because of i disabled tamper protection dont know. best do your tests against 26100.1 do wim backups then update over wu to 26100.863 to see if windows update fails or not. also found that when tried to install chipset driver i had to wait around 3 to 5 min before it got installed vs 22h2 3sec also settings/system items are dissapearing randomly then appearing again
it would be great if @MSMG could add the removal of hyper-v 1, I hate it, 2, it's of not use to me i'm blind and it's not accessible, and 3, when msmg removes components, you know that it is far cleaner compared to when you remove packages via dism.
Just use cbsenum to remove tones of unwanted drivers, hyperv, and whatever else you don't want. It's really easy to use.
No copilot nor recall on 2024 iot ltsc that's the os people will be installing. Easy to install ms store and winget if anyone wants it there's gpedit preinstalled. Would already use it if it didn't have bugs.
Didn't use 2021 ltsc at all can't you install updates after installing windows? Then use dism++ to make install.wim out of the system, place it in your iso and job done
It wasn't my approach since it will consume more time, but that's an alternative that I didn't know about it. Thanks for the suggestion.
I always do that as I always make many more changes after tweaking iso with toolkit. After tweaking with toolkit install windows then tweak whatever you like regedit gpedit remove unwanted packages using cbsenum install apps and drivers you want etc when done run scanhealth sfc then dism++ create install.wim place in your iso and you can install exact copy on many pcs.
I want to remove some packages in windows 7 wim but Toolkit\Bin\Lists\DISM_Templates\RemovePkgsList_W7.txt file is empty. Anyone has an idea about how to fill that .txt file with the name of the packages ? Does this tool have support for windows 7?
mount the windows 7 .wim go to the folowing location in the mounted .wim location C:\Windows\servicing\Packages in there you will find a hole lot of package names like what I have on my windows 10 machine. HyperV-Compute-Host-Containers-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.867.cat HyperV-Compute-Host-Containers-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.867.mum remove the .cat and the .mum extentions from the end of the names paste in to the file you mentioned and off you go.
@mhussain , thank you for usefull information. I am really confused why MSMG did not prepare a complete list of packages for Window 7 like he did for windows 10 and windows 11 ? It would be easier for me to remove packages with the list of packages. I hope he can prepare a list for this task
My new Win11 23H2 image has "Join this device to Microsoft Entra ID" missing. I've attached a list of packages I removed, would one of them cause this?
hi all, after removeing most components, could you all tell me how much faster your installations become? I would beg you don't judge me here, but 1, i'm blind, and 2, i've not joined the ssd users out there. i'm still running on a hdd on an old intel i3 processer from 2013. not by choise, but with the money squeeze it's impossible to aquire another device. hence my question. how much more responsive are installations after all bloat and components are removed? I don't want bentchmarks, but real world usage stories. that is if you don't mind? thanks all! Majid
I haven't installed Windows on a hard drive for a very long time, only SSD drives. Even when I started using MSMG's ToolKit I was already using an SSD drive for my boot drive. You could easily find an second user SSD drive for a very reasonable price. I have a couple of second hand 64 GB SSD drives which I sometimes use for testing, these cost me less than £10 each several years ago. You could use a small 64 GB or 128 GB drive just for booting from and you would see a huge increase. Store big or infrequently accessed files on the hard drive, such as archives, documents, music, pictures, downloads. I realise cost is a challenge for you, so I won't talk any more about buying a cheap SSD, I just want to make sure that you realise they don't have to be as expensive as you think. Removing apps and unwanted services can surely only help the speed of a system. Though I would suggest not cutting too deep into the ISO and removing things you might need in the future. Also the memory saved from tweaking will help with the system's responsiveness.
I have a laptop from 2012 (Acer Aspire 5755G) with an intel 2450M processor. 6 years ago bought an ordinary 110GB Sandisk SSD and personalised LTSB 2016 to my own needs and installed. Difference is day and night. System gets ready in 5 seconds from touching power button to desktop. But I removed many apps, disabled unnecessary services, tasks and so on. You can also prepare an image to your needs and install on an SSD and enjoy the system. No need to buy an expensive one like @Feartamixg said.
Installation won't become much faster, I'm using 22h2 removed from it about everything I'm sure I won't use in the future, single hyperv that's like hundreds of packages. Defender, etc. With a 3gb gaming emulator Ms office and few other apps installation is only 17gb space used. Ram usage about 1.5gb after booting. It's worth cleaning windows a bit plus invest in ssd drive if you can. Boot time like 5sec.
This is what makes a big difference for those using large SSDs. However, for mechanical drives and small SSDs I think it is necessary to make the ISOs sanitized. For mechanical storage, it increases performance because of fewer files and. for small SSDs, just because of storage space (not speed).