??? when using Dism, HOW to prevent overbloating of the .wim file???

[7point5]

k so that's a common problem & yet the web fails to provide a good answer, so I'll try here:

when using dism to slipstream msu updates (especially into install.wim) the wim file tends to get bloated far beyond what would be expected

googling the problem has failed to turn up consistent solutions, some say you must unmount the image then remount, others propose different dism commands (but don't specify when to run them)

so my question is simple, when disming a wim file - especially when many msu files are involved in the updating of the wim - how the f can I avoid bloating & make sure the final .wim is as small as possible? (without using any artificial compression of the wim file I mean. I also want an iso that installs as fast as possible)

do I have to unmount & remount the wim everytime I add a package? or run a special cleanup command after each package is added?

or instead is there 1 simple command I can run only after all the msu files been added, before committing the wim?



ps. don't try google, I did & it's useless for this specific problem

 

[torchwood]

Hi 7.5

My understanding is that it does need to be mounted.

All windows updates are compressed so yes they need to be expanded.

NOTE 3rd party extraction tools - ie 7Zip etc SHOULD NOT BE USED, possibly why your experiencing bloating

not entirely sure what you want to achieve, as updates are now cumulative , - and therefor HUGE

usefull reading
System Preparation Tool - Use to Customize Windows - Windows 7 Help Forums

Roy

 

[7point5]

Hi 7.5

My understanding is that it does need to be mounted.

All windows updates are compressed so yes they need to be expanded.

NOTE 3rd party extraction tools - ie 7Zip etc SHOULD NOT BE USED, possibly why your experiencing bloating

? I don't use 3rd party tools where d'you get that? :shock:

I only use dism (from a win7 recovery environment)

I start with the usual Dism /Mount-WIM /WimFile *** command
then Dism /Image: *** /Add-Package
then Dism /Unmount-WIM /MountDir *** /Commit

and in the end the update wim file is a LOT bigger than the original (more than it should be)

so what commands must be added to make the resulting wim more compact?

not entirely sure what you want to achieve, as updates are now cumulative

I know but there's a yuge problem:

the "convenience rollup" omits several important updates that came before the rollup (while including useless/harmful ones eg. telemetry)

so it's necessary to include many other updates before the rollup. starting with the KB3020369 service stack update which they didn't even include in the rollup despite its vital importance

 

[torchwood]

Hi 7.5,

In answer to this and your other thread as well

Very few people here, me included, delved further inside the the actual inards of updates.
I know how thier made up.

You could try over at Sysnative Forum.

I only mentioned the 3rd party tools as a possible reason.

Roy

Latest version iso i know of

Noticias - ISO Media Installation for Windows 7 SP1 x64 English/Spanish June 2016 Slipstreamed with NVMe, USB 3.0 y 3.1, Thunderbolt support and all updates until June 2016

 

[SIW2]

You can export the image using maximum compression to a new wimfile. Gimagex or dism++ are simple to use

 

[7point5]

actually what I ment was, without even using compression : I read that dism creates some sort of "redundant" files every time a msu package is added to a wim - my question was how to "clean up" the wim of ALL unnecessary files created by the dism update procedure -using dism itself, not 3rd party apps

 

[SIW2]

Use cab files instead.

 

[7point5]

? the cab files are the main file inside the msu file right? it almost as big as the msu file itself

so what the difference if I extract & use the cab file instead??? both msu & cab are same size

 

[SIW2]

Differ engine uses express cabs. Dism++ will do it for you.

Dism++