SP1 rc1 will not download/install on Vlited installs

[jamieo]

jamieo, because this way there is no risk for the real data and I have a template to easily make sp integrations on the fly.

Make sense... I haven't installed on a VM since I got my C2D but on my Pentium M it was sloooow....

I have my system set up so I can easily reinstall without fuss, plus it's (so say) better to use a second partition anyway. I also took an image of RTM after entering audit mode to make things easier next time. Everyone has their favorite way to do things.

[razormoon]

SP1 seems to be working. Wasn't there a recovery image feature of sorts imbedded into service pack? Could I have possibly removed that with vlite? haha

[dexter.inside]

This method is viable, but slow even on my Phenom / 3 GB memory virtual machine server. I'd suggest you stick with the integrated SP1 RC1 ISO from Connect, unless you are really desperate (a.k.a. you also want a role or feature installed, like IIS on lite SP1 or lite Server 2008)

[daroga]

This method is viable, but slow even on my Phenom / 3 GB memory virtual machine server. I'd suggest you stick with the integrated SP1 RC1 ISO from Connect, unless you are really desperate (a.k.a. you also want a role or feature installed, like IIS on lite SP1 or lite Server 2008)

There's an SP1 ISO out there? Is that available to the general public or only to people within a certain Microsoft program? You can then rip it in vlite? That'd be slick.

[Arneh]

There's an SP1 ISO out there? Is that available to the general public or only to people within a certain Microsoft program? You can then rip it in vlite? That'd be slick.

Yes, there is an SP1 RC1 ISO from Connect however it's only available to those in the actual Vista SP1 Beta program.

The general public only got the WU choice or the standalone .exe packages.

[daroga]

Yes, there is an SP1 RC1 ISO from Connect however it's only available to those in the actual Vista SP1 Beta program.

The general public only got the WU choice or the standalone .exe packages.

Ah, ok, I figured it was something along those lines. Oh well. Maybe we'll get easy access to something once the SP gets a final release.

[MFCK]

Hi all !

I've made my own Vista SP1 x64 reverse integration and after i've Vlited it.

All is perfect for me, Vlited Vista rocks and i have no problem.

Removed the biggest component like "Natural language, Chinese fonts, DVD-Maker, ..."

My Vista start in 20sec and the system is more responsive than ever.

The copy file problem is solved and all HDD operations are faster.

But in the winsxs directory some components remains duplicated (all these updated by SP1 integration):

for example:

amd64_microsoft-windows-s..oxgames-purbleplace_31bf3856ad364e35_6.0.6001.17052_none_621621beb6f5fa8a

--> 36.4 Mb

and

amd64_microsoft-windows-s..oxgames-purbleplace_31bf3856ad364e35_6.0.6000.16386_none_60135802b9e444f4

--> 36.4 Mb

By removing these duplicated files, is possible to gain more space again and reduce the "component hive in registry"

RTM size = 9 Mb, after SP1 = 27 Mb, after reverse integration and vlite = 18 Mb

Is there any way to remove these duplicated files?

THanks in advance for your reply !

Good job Nuhi ! (I hate the winsxs dir and all these backup files !!)

Edited December 19, 2007 by MFCK

[dexter.inside]

amd64_microsoft-windows-s..oxgames-purbleplace_31bf3856ad364e35_6.0.6001.17052_none_621621beb6f5fa8a

--> 36.4 Mb

and

amd64_microsoft-windows-s..oxgames-purbleplace_31bf3856ad364e35_6.0.6000.16386_none_60135802b9e444f4

--> 36.4 Mb

One of these can be removed only if both share the same Class IDs in the registry (in which case, remove 6.0.6000.16386). The purpose for both of them being present is the ability to uninstall SP1 and/or rollback a particular component (like a driver), and/or future functionality for Application Compatibility.

One of the new "under the hood" concepts in Vista is that it keeps all previous versions of all registered DLLs in the system. In theory, applications having passed the Windows Logo Certification should comply with this rule.

Thus, users should be warned... if vLite includes such a function, it will prevent SP1 or a particular hotfix from being uninstalled.

[jamieo]

Thus, users should be warned... if vLite includes such a function, it will prevent SP1 or a particular hotfix from being uninstalled.

That's true - but if you wouldn't want to uninstall it nuhi put me on to a utility that m$ includes in the new sp1 waik so you can free up that disk space.

From Microsoft Technet

• Windows Vista SP1 File Removal tool (Vsp1cln.exe).

Vsp1cln.exe is an optional tool that you can run after you install SP1 to remove older versions of components that have been upgraded to new versions in SP1. You may want to run this program because installing SP1 increases the amount of disk space that is used by the operating system (because the older versions of components are stored in case you need to uninstall SP1). Typically, you should run Vsp1cln.exe if you want to reclaim this disk space after applying SP1 and if you will not need to uninstall SP1. You can use this file both online and offline, but you must have SP1 installed. You cannot uninstall SP1 after you run this tool on an image.

I couldn't get it to work on an online (installed) vista and kept getting a message prompting me to use some switch, both from within the install and from winpe. Eventually it 'just worked' after using it on an offline install (mounted wim) as follows...

vsp1cln /o:<path to offine windir>

Removes almost 1.4GB leaving winsxs about 700MB heavier than rtm and looking very similar to the 16659 ISO m$ put out a while ago. I vlited the same preset on different versions, here's the sizes of install.wim:

390 MB	- 6000.16386 (From RTM ISO)
470 MB	- 6001.16659 (From Microsoft ISO)
639 MB	- 6001.17052 (Reverse Integrated)
474 MB	- 6001.17052 (after vsp1cln)

Just google 'vsp1cln.exe' or get hold of the latest WAIK. I used build 17051 and a much earlier one (16659 I think) - both produced the same results with SP1 RC1, not everything removed but perhaps the stuff left behind is needed for compatibilty or may eventually be removed when SP1 is final.

[sp00f]

Google for vsp1cln.exe only finds chinese sites ,cant read chinese

[dexter.inside]

I will phone Microsoft to get more info. 10x for the hint.

[MFCK]

Thanks Jamieo !

I've downloaded Vsp1cln.exe and Vsp1cln_x64.exe and i've cleaned the offline image !

Perfect ! Vista winsxs size is decreased again but the registry hive "component" remain always 18mb (9mb RTM) .

With reverse integration and SP1 cleaner i have a vLited Vista like with the RTM.

[dexter.inside]

Thanks Jamieo !

I've downloaded Vsp1cln.exe and Vsp1cln_x64.exe and i've cleaned the offline image !

Perfect ! Vista winsxs size is decreased again but the registry hive "component" remain always 18mb (9mb RTM) .

With reverse integration and SP1 cleaner i have a vLited Vista like with the RTM.

So that means it only cleans files and not their entries in the registry?

[MFCK]

So that means it only cleans files and not their entries in the registry?

Yes, totaly true here you can see an example from HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\ :

[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adpu320.inf.resources_31bf3856ad364e35_6.0.6000.16386_en-us_6838883b0cbd6434]

"identity"=hex:61,64,70,75,33,32,30,2e,69,6e,66,2e,52,65,73,6f,75,72,63,65,73,\

2c,20,43,75,6c,74,75,72,65,3d,65,6e,2d,55,53,2c,20,56,65,72,73,69,6f,6e,3d,\

36,2e,30,2e,36,30,30,30,2e,31,36,33,38,36,2c,20,50,75,62,6c,69,63,4b,65,79,\

54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,\

72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,\

34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53

"c!microsoft-w..anguagepack_31bf3856ad364e35_6.0.6000.16386_5be770887b0a0d38"=hex:

"f!adpu320.inf_loc_5b2580bad93d2573"=hex:61,00,64,00,70,00,75,00,33,00,32,00,\

30,00,2e,00,69,00,6e,00,66,00,5f,00,6c,00,6f,00,63,00

[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_adpu320.inf.resources_31bf3856ad364e35_6.0.6001.17052_en-us_6a3b51f709cf19ca]

"identity"=hex:61,64,70,75,33,32,30,2e,69,6e,66,2e,52,65,73,6f,75,72,63,65,73,\

2c,20,43,75,6c,74,75,72,65,3d,65,6e,2d,55,53,2c,20,56,65,72,73,69,6f,6e,3d,\

36,2e,30,2e,36,30,30,31,2e,31,37,30,35,32,2c,20,50,75,62,6c,69,63,4b,65,79,\

54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,20,50,\

72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,61,6d,64,36,\

34,2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53

"S256H"=hex:ff,9d,18,2d,9e,6e,b5,b8,03,37,e1,21,00,48,3e,ef,b9,78,21,b5,06,b2,\

ea,56,11,e5,c9,28,f0,dc,8d,19

"c!ec81b081eec..29f7a2cffee_31bf3856ad364e35_6.0.6001.17052_3194f30ffd67a538"=hex:

"f!adpu320.inf_loc_5b2580bad93d2573"=hex:61,00,64,00,70,00,75,00,33,00,32,00,\

30,00,2e,00,69,00,6e,00,66,00,5f,00,6c,00,6f,00,63,00

Thanks again Nuhi for the new version !

Excellent Christmas gift for us !!!

Edited December 24, 2007 by MFCK

[cdo5]

"You can also rebuild the ISO using vLite by extracting the contents of the Vista RTM ISO to a temporary directory, replacing the install.wim and using vLite's Vista Burning/ISO creation features. One can also use vLite to remove unwanted features in Vista SP1 even though vLite was primarily designed/tested on Vista RTM."

Does this mean that, after creating a new install.wim, and copying files from original install disk to a temp file, one can just delete the install.wim from the source folder and coopy/paste the new one in there - then vlite???