all updates worked after installing kb947821.

Hmm well I didn't try updating again after the initial failed attempt, so I'll load up my virtual box and try again and see what happens.

Yep, installed that update first and after that it all worked great. Weird thing I noticed though, just after installing that one update my winsxs folder had already grown by like 100 mb *cry :.(

*edit*

Reinstalled again and watched the winsxs folder while the hotfix was processing and it was adding folders to their like crazy, I'm guessing that update fixed whatever we did the the winsxs folder that it didn't like.

*edit* *edit*

I think I'll integrate that hotfix with DISM and see how that goes.

Edited February 5, 201016 yr by zebus

Yep, installed that update first and after that it all worked great. Weird thing I noticed though, just after installing that one update my winsxs folder had already grown by like 100 mb *cry :.(

*edit*

Reinstalled again and watched the winsxs folder while the hotfix was processing and it was adding folders to their like crazy, I'm guessing that update fixed whatever we did the the winsxs folder that it didn't like.

*edit* *edit*

I think I'll integrate that hotfix with DISM and see how that goes.

gr8 try use kb947821 and then install the updates

lets see if aelibey is right

if yes i will remove Extreme tag

Okay, so in the end this is what I ended up doing to make my install disc perfect.

1) Loaded virtual machine, manually applied kb947821 to repair winsxs folder, integrating it as a hotfix didn't work, had to be done after install.

2) After the update installed and the winsxs folder was fixed I shut down the VM, and extracted the winsxs folder off it.

3) Mounted my install.wim I had been working on, deleted the winsxs folder in it, and replaced it with the now fixed winsxs folder I pulled off the VM.

4) Made a new iso with vlite, installed, and everything worked right off with no need to apply the hotfix and the winsxs folder was still as small as it originally was!! YAY!!

I'll try to make a new .bat file to save people the trouble, because I'm pretty sure in doing this I've found the absolute minimum (or very close to it) the winsxs folder can be and still work, pretty much everything in there is 100% necessary for windows update to function meaning you can't get any smaller without breaking windows update or having to run the hotfix.

Here is a log of the directory structure if anyone wants to check it out before I get to writing a .bat file for it,

http://www.mediafire.com/file/mzewi2zwino/winsxs.txt

The txt file was so big I had to host it on mediafire

*edit*

Forgot to mention was on ultimate x64, and the end size ended up being 169mb

Edited February 5, 201016 yr by zebus

zebus disclosed the secret of winsxs before I posted it! And it was enough only to mention it is possible! Guys, you are incredible!

All the best,

Alex

hi aviv00,

is it possible to install Visual C++ Redistributable Package (2005 or 2008) if winsxs is removed?

Some programs like ATI Catalyst, Logitech Setpoint and visual studio are dependant on it.

hi aviv00,

is it possible to install Visual C++ Redistributable Package (2005 or 2008) if winsxs is removed?

Some programs like ATI Catalyst, Logitech Setpoint and visual studio are dependant on it.

hey

yes i success to install that :

http://www.microsoft.com/downloads/details...;displaylang=en

edit

i install successfully .NET4 beta 2 too

Edited February 7, 201016 yr by aviv00

@aviv00

Thanks for your effort for the guide, I have tried your method and get the windows to boot without WinSxS (with 2.66GB size) - but unfortunately I cannot install Live messenger because of C Runtime Error (something related to CRT assembly blah blah blah) am i doing something wrong???

please help - i have attached my vlite.ini file in case you want to take a look. BTW, can you share yours?

Works.ini

@aviv00

Thanks for your effort for the guide, I have tried your method and get the windows to boot without WinSxS (with 2.66GB size) - but unfortunately I cannot install Live messenger because of C Runtime Error (something related to CRT assembly blah blah blah) am i doing something wrong???

please help - i have attached my vlite.ini file in case you want to take a look. BTW, can you share yours?

np

i just tested it and its working

here my ini test it

7_new.ini

Edited February 14, 201016 yr by aviv00

@aviv00

Thanks for your effort for the guide, I have tried your method and get the windows to boot without WinSxS (with 2.66GB size) - but unfortunately I cannot install Live messenger because of C Runtime Error (something related to CRT assembly blah blah blah) am i doing something wrong???

please help - i have attached my vlite.ini file in case you want to take a look. BTW, can you share yours?

np

i just tested it and its working

here my ini test it

Thanks - testing now.

Edit:

Sorry - you .ini did not contain removal of WinSxS - is that correct?

Edited February 14, 201016 yr by nant15

yea its ok just add winsxs

i just remove winsxs after applying this ini that why its not appear

Edited February 14, 201016 yr by aviv00

yea its ok just add winsxs

i just remove winsxs after applying this ini that why its not appear

No luck does not work for me..

will try with kb947821 again tomorrow

u did install kb947821 ? and then try install msn ?

Thanks for this aviv does this mean removal of IE8 via vlite is do-able now ?