Don't slipstream XP SP3 on Windows Vista!

This just in from Bink, seems he had a pretty interesting weekend attempting to Slipstream XP SP3.

"So I build a new Windows XP ISO with SP3 integrated, this is a Volume License editions (VOL) which only accepts Volume License Keys (VLK). When I want to install it on a clean machine, I noticed that setup prompts for a product key and it does not allow me to continue, which should be a new feature in XP sp3. OK so I fill in the VLK but it does not accept it, I try another one from a customer of mine, does not work either. Angry

I found out that the problem is when you do the XP Sp3 slipstream process on a WIndows Vista machine, the API gives a different response and screws up the PID process. This is a bug and Microsoft knew about this in December, still the bug remained and made it all the way to RTM, nice work Microsoft.

So XP SP slipstream only on XP or 2003 machines!!!"

News Source: Bink

Report a problem with article
Previous Story

Xbox 360 Finally Getting Blu-Ray Drive

Next Story

New Nine Inch Nails Album Available For Free Download

60 Comments

Commenting is disabled on this article.

I'm not sure if there is anything wrong with my attempt to slipstream SP3 into a VL XP/SP2.

The slipstream was done on a thinkpad running XP/SP3 (yes, SP3 already) and it went well. However, I tried the slipstreamed CD in a virtual machine for installation, it did not take my VL key (tried with two keys). And, strangely, it DID take a non-VL key that I obtained from MSDN subscription. I noticed on the window where it asked for the key that it says key is optional.

It appears to me that the slipstream has turned my VL CD into a non-VL XP CD.

This has nothing to do with the Vista as mentioned in this article.

I am thinking if it is the problem to slipstream on a machine running SP3 already. Please also note that my thinkpad is not running a VL license (instead, an OEM from IBM).

The other difference is that I put a answer file into the CD for unattended installation.

I am pretty sure the original CD that I used for slipstream a VL CD. I just used it to install a few weeks back.

Anyone has tried with a similar combination like above?

Hi,

you can slipstream your VLK-CD in Vista, if you are using the "XPslipper" tool in compatibility mode of Windows XP how the picture shows.

www.winsupportforum.de

Actually there is a german version only, but we plan to release an english version soon. Sorry, you have to register for viewing pictures and download the tool, but it works too with windows 2000!

I had the same problem at work. Fortunately i had an XP virtual machine, so I simply slipstreamed it on there using nLite of course and then it worked fine.

there are some conversations TechNet forums regarding this bug.
Thankfully i read them (sorry i don't the links here) minutes after making a guide for my blog.

Mm... I thought I screwed up the slipstream while updating my old XP media. Sigh... (this was with an OEM disc btw, not VLK).

This is old news for the people who have been Slipstreaming SP3 since it was leaked. OLD NEWS!

Microsoft Integrated Images:

Windows XP Professional With SP3 - Retail: Asks for a CD-key but you can choose not to enter one.

Windows XP Professional With SP3 - Volume License: Always makes you enter a CD key. Can't install without one.

For what it's worth, there may be a workaround when doing a VLK XP slipstream on Vista, in the Bink comments:

Right-click the Update Executable, then choose Properties. Click the Compatibility tab, then enable Windows XP SP2 Compatibility Mode. Click OK on the Properties window, then slipstream to your hearts content!

(from the Bink news source link above)

Figured I'd throw that out there if you *really* need to do this under Vista for whatever reason.

I can confirm this. Over the weekend i installed SP3 on my x86 xp box and it worked fine, however when i slipstreamed it on vista x64 i had this problem in a VM. It would only install if i put in a xp pro retail product key, not a volume license key. VERY annoying.

Same exact thing for me when I tried with one of the betas a while back. All I knew is that for whatever reason it seemed to convert my image to an RTM install. Nice to know more about it and that I can still do it myself if I want to at least.

(Kushan said @ #18)
You also can't slipstream a 64bit SP into a 64bit image on a 32bit OS and vice versa.

I just made a slipstreamed XP x86 SP3 disc last night on XP x64. It works fine.

I think Microsoft should seriously consider letting individuals download XP sp3 (full install) for free. It is a bit pathetic that in this day and age you actually have to make the CD yourself. Most Linux/BSD distributions have at least quarter to six month release cycles (if not weekly) builds with the latest updates applied. I also think Apple needs to get with the program as well. I don't expect either company, however, to give this option to users who do not pay significant cash for the privilege of being in an exclusive club to download the latest builds (MSDN/TechNet).

I guess I don't follow what everyone is doing here. Are we talking about installing a VL version of Windows XP SP3 (slipstreamed) on-top of a Vista install? If so, can you just format the vista drive and then install XP SP3?

Meh...I'll just keep Vista SP1. I don't have any plans on downgrading anyway.

(Shadrack said @ #15)
I guess I don't follow what everyone is doing here. Are we talking about installing a VL version of Windows XP SP3 (slipstreamed) on-top of a Vista install? If so, can you just format the vista drive and then install XP SP3?

Meh...I'll just keep Vista SP1. I don't have any plans on downgrading anyway.


Is it that hard? If you put together a VL SP3 disc on Vista, it won't work.

The disc is created, prompts for a key, and does NOT accept any key.

It doesn't matter how or where you intend on installing XP, if it was a Volume License SP3 disc put together under Vista, it will not install.

(Burned said @ #13)
This is old news. It has done this since beta.

Unbelievable...

It's 'new' news, because SP3 is no longer beta? It's 'new' news because it's 'still doing it'.

****s sake people, get a clue.

argh... so this is what went wrong last weekend. I ended out using a sp2 cd because I couldn't get a fresh sp3 cd to work

You could always use nlite. I did a slipstream of SP3 on my Dell's XP OEM CD while in Vista with nlite, and it turned out fine.

Won't work on a VL copy though. I tried it on a VL copy + Vista host system + nLite. Makes the ISO but won't accept a key afterwards. nLite does not solve the issue on a Vista host (maybe under a VM).

It took me a while to figure this out too, I was so confused at first. I was trying to make SP3 slipstreamed images for work, and it was giving me that crap. Stumbled upon this fix last weekend, and was shocked. The way Microsoft is pushing Vista, and now this?

Interesting though.

so whats going on with SP3. iam not bothered if i have to input the product key. but SP3 was suposed to allow installs with out one. so why are people who have the SP3 integrated versons from MSDN having to input the product key.?

iam buring a sp3 student version and will test it out on a VM. i wounder if it will install with out the PK

I have downloaded the ISO of XP pro and VL with SP3 integrated from MSDN, and they have the same problem... When I setup on a virtual machine (with virtual pc), I must write the product key.

Bye

I believe that all VL copies still require the key to be input, even with SP3. The keyless install option is only for non-VL copies I believe.

(ir0nw0lf said @ #7.1)
I believe that all VL copies still require the key to be input, even with SP3. The keyless install option is only for non-VL copies I believe.

That's right VL's need the key, others don't.

Depends on your take on "keyless". There's a file you can add to the XP cd that will prefill any information you want. I have this setup on a VLK copy so I don't have to input the key when installing. :P

ive also had problems slipstreaming sp3 into my slipstreamed sp2 OEM version cd. i cant install unless i put my key in.
among other bugs like during install iam asked for napclientprov.mof / and ICS/windowsfirewall service not working and refusing to start despite trying all the guides out on the net to "fix" the problem.

should we stay away from using nlite to slipstrem or has ms now made xp so we cant nlite and custommize our installations?

I slipstream SP3 into XP (OEM) in Vista and did an install using that image without a problem. The SP3 they used might not of been the real RTM, I heard somewhere there was a bug with a pre-RTM build that if you slipstreamed it, it wouldn't accept the product key (which is why I re-downloaded SP3 from MS as I acquired it early from another source)

(T.W. said @ #2.1)
It only affects Volume Licensing version. OEM version is not affected so stop sprouting nonsense.
It's not nonsense, this issue did affect the OEM version as well. MS fixed it though and obviously the problem still lingers for the Volume Licensing version. Anyway my post could still be considered useful, perhaps someone wants to know if the OEM version is affected as well, perhaps?

(BanneD said @ #1)
That's definitely something a software giant shouldn't do - let the users of his newest OS down like this...

How is that letting users down? 99% of all people installing SP3 in the world will simply have it install via Automatic Updates and don't even know what slipstreaming is.

(GreyWolfSC said @ #1.1)

How is that letting users down? 99% of all people installing SP3 in the world will simply have it install via Automatic Updates and don't even know what slipstreaming is.

That is not really relevant is it....

If Microsoft knew that the bug was present in december, it's a bad thing it made it to RTM. And it doesn't matter how many users wil use the function....

(Boogiman said @ #1.2)
That is not really relevant is it....

If Microsoft knew that the bug was present in december, it's a bad thing it made it to RTM. And it doesn't matter how many users wil use the function....

Of course it matters how many people will use the function (in this case slipstreaming an XP OS on a Vista system). Companies generally try to fix the bugs that'll affect the most people, & then work from there, it's not like they have an unlimited supply of people to work on these things. To assume that a company can fix everything regardless of the user base, sorry that's just silly.

Besides, if you're with a company who gets VLK CDs, aren't you going to end up with a XP VLK CD w/ SP3 pre-slipstreamed anyway? And, like the other poster said, the vast majority of XP slipstreamers won't be doing this on Vista. I know I didn't.

(lars77 said @ #1.3)
it's not like they have an unlimited supply of people to work on these things. To assume that a company can fix everything regardless of the user base, sorry that's just silly.

Maybe MS should take some people off the Zune, Silverlight, and Live teams, since they aren't doing anything worth a damn.

MS must be one of the most inefficient companies in the world. It blows BILLIONS on unproductive nonsense every year.

I'm starting to think that MS is some sort of fraternity where they spend 75% of their time goofing off. How does a company with tens of thousands of supposedly professional employees manage to screw things up worse than the no-budget hobbyist Linux community?

It must be the management...

(toadeater said @ #1.4)
Maybe MS should take some people off the Zune, Silverlight, and Live teams, since they aren't doing anything worth a damn.

MS must be one of the most inefficient companies in the world. It blows BILLIONS on unproductive nonsense every year.

I'm starting to think that MS is some sort of fraternity where they spend 75% of their time goofing off. How does a company with tens of thousands of supposedly professional employees manage to screw things up worse than the no-budget hobbyist Linux community?

It must be the management...

Troll much? Exactly what does ANY of that have to do with slipstreaming XP service packs?

(GreyWolfSC said @ #1.5)

Troll much? Exactly what does ANY of that have to do with slipstreaming XP service packs?

TROLL ? BS !

i enjoyed his comment even if i dont fully agree (but i do)
why can't you people leave the modding to the admins ?
The internet is about the transfer of information even if it doesn't line up with your opinions.

your comment was MORE worthless than his..
if i had to define a TROLL comment it would be yours !
he stated his opinion and you came along and crapped on em for no reason and "called troll"

we're all forever in debt for such valuable troll spotting services

and the topic ? lol

we'll old news for me but its good people are getting the news spread around
and its just one more reason why vista sux as far as im concerned

(GreyWolfSC said @ #1.1)
That's definitely something a software giant shouldn't do - let the users of his newest OS down like this...

This is nothing new, I first noticed this with slipstreaming Service Pack 2. I won't go into a lot of detail, as my post will be deleted, but it has to do with the pre 2001 release of the stolen VLK key XP version. Changes were made to prevent the use of stolen VLK, and "KeyGen" created VLK's. PIDgen.dll and a few other files were updated. Replacing with the original files and using WinNT.sif may well overcome this problem. Microsoft will not fix this. Since they have had to add a new algorithm to add more legal keys. Microsoft will just offer Volume Licensed customers a new SP3 installation disk.

(Boogiman said @ #1.2)

That is not really relevant is it....

If Microsoft knew that the bug was present in december, it's a bad thing it made it to RTM. And it doesn't matter how many users wil use the function....

i take it you know very little about software development, all software has bugs that are known to the developer, they just dont fix ones that are unlikely to occur in the wild, or that will only affect a small minority fo customers.