Servicing Stack and Servicing Stack (WOW64)

[Clanger]

I noticed Servicing Stack and Servicing Stack (WOW64) in the newer betas. I saw DISM was mentioned in their notes. If i remove these(from w7 x64) will i have any DISM functions at all and would NTLite run?

How would it affect removals from custom captured wim files with all updates and .nets fully integrated on a system with those 2 components removed?

 

[nuhi]

If you remove DISM, DISM is removed, self-explanatory

NTLite uses it for integrations and feature config, while Components removal, Update cleanup, Tweaks, Unattended and Post-setup do not need it.
UI will automatically hide the affected pages.

 

[Clanger]

Just as i thought,Removals only if they are removed. Im going to use a custom captured wim with all updates added, .net462. Features? there aint no features left when ive done with it . I wont need dism functionality when using captured wims, GImageX, just removals, so NTLite should still be very usable.

 

[ahazuarus]

Pretty sure windows still uses dism to apply updates. I'm curious to find out of WU still works without it.

 

[Clanger]

Strip out WU, DISM, BITS, MS dont stand a chance in hell of slipping one in do they?

I hope the install is stable with the Stacks removed.

 

[ahazuarus]

Update windows by monthly reimage only, not even a bad idea. Actually, thats literally how VDI environments work by design.

 

[Clanger]

Update windows by monthly reimage only, not even a bad idea. Actually, thats literally how VDI environments work by design.

You only need to constantly update for security porpoises, if you are on a private network(no internet) or not networked at all, you get your image stable and stick to it for 6 months(or longer). I have heard of users installing os and setting it up, imaging the drive then wipe and redoing the image every month, a bit excessive mebbe but the www is the www.