The WinReducer Forum
Would you like to react to this message? Create an account in a few clicks or log in to continue.

The WinReducer ForumLog in

FORUM

descriptionuse of RS5 17663.1 or 17663.107 + lastest CU Emptyuse of RS5 17663.1 or 17663.107 + lastest CU

more_horiz
I notice that the resulting .iso is bigger if I use 17663.107 + Windows10.0-kb4467708-x64 -CU.134.msu
both lead to .134 but with my .wccf it goes from 6 054 036 Kb to 6 199 698 Kbuse of RS5 17663.1 or 17663.107 + lastest CU Screen12

descriptionuse of RS5 17663.1 or 17663.107 + lastest CU EmptyRe: use of RS5 17663.1 or 17663.107 + lastest CU

more_horiz
sorry I forget to put my question
does the result .iso install the same updates? 
If not, can I use some Winreducer actions to have the same size (almost the same …)

THanks for the help

descriptionuse of RS5 17663.1 or 17663.107 + lastest CU EmptyRe: use of RS5 17663.1 or 17663.107 + lastest CU

more_horiz
Hey Smile

I'm not sure to understand correctly because each time you integrate updates, net framework 3.5 or drivers in your ISO, the ISO size will grow according the amount of new files you integrate Smile

descriptionuse of RS5 17663.1 or 17663.107 + lastest CU EmptyRe: use of RS5 17663.1 or 17663.107 + lastest CU

more_horiz
But the only difference is the .iso the .wccf is the same for both reduction.
As the Initial .iso's are different size I can imagine that the result will be according to the initial size.
But my question is the reduced .iso's will install Windows in the same state?
privacy_tip Permissions in this forum:
You cannot reply to topics in this forum