Microsoft has just released Windows XP x64 Edition SP2, currently available for all architectures (x86, x64, & Itanium) in English and German.
Before installing Windows XP x64 Service Pack 2, you must first ensure that you uninstall Internet Explorer 7 before installing the update, or else Internet Explorer will fail to work, since SP2 will reinstall IE6 for you.
Download Links:
Integrating the Service Pack
You can slipstream SP2 into your Windows XP x64 Edition CD by copying the contents of your CD to a folder on your hard-drive, and issuing the following command:
WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe /integrate:C:\XP64\
In the example above, this is the x86 installer being used and the Windows XP x64 CD has been copied to C:\XP64\
After the process completes, download Microsoft Corporation.img and use it as the bootsector for your CD.
If you’re using Nero, it’ll look something like this:
- Choose CD-ROM (Boot) from the New Compilation’s Boot page.
- Under Source of boot image data choose “Image file” and Browse to the Microsoft Corporation.img.
- Select Enable expert settings (for advanced users only) and set the following: Kind of emulation – No Emulation
Number of loaded sectors – 4
Load segment of sectors – 07C0 - Click NEW.
- File Browser area, navigate to c:\xp. Select all of the files inside of that directory and copy them over to the left side for burning.
- Click BURN and you’re done once the CD is complete.
The Microsoft Corporation.img link doesn’t work
Thanks for the heads-up, Robbie.
That was an IIS security module kicking in, since this is the first time we host a .img file on NeoSmart.net. You can download it now via the link above though.
Cheers!
You could just use Slipstream XP. I use it to slipstream my XP and Office service packs. It will make a bootable ISO with SP2 slipstreamed in.
Link
http://www.flexbeta.net/slipstreamerxp/
Yeah, SlipstreamerXP is a nifty program – but if you only do this once every 5 years, it’s not too difficult a task.
Where did you get that info about IE7 and x64 SP2? I am running Windows XP Pro x64 with IE7, and I was able to install x64 SP2 fine, and my IE still works …
Yep, that’s true.
Per our post, we just upgraded the NST server to SP2, and we didn’t experience the IE7 issue. The information regarding the IE7 uninstallation requirement was posted on Microsoft’s website yesterday, however, it’s no longer there now.
Sorry for the confusion.
Do you have to be running x64 to perform this operation? Try to build my CD in XP 32bit – I am getting:
Kind of pointless to install x64 just to create an x64 slipstreamed CD for a fresh install.
Yeah, you do.
But you don’t need to do that, here’s a pre-patched ISO file: http://www.microsoft.com/downloads/details.aspx?FamilyId=18261B5B-58D4-4146-A358-B78404EC640C
Guru,
This is simply an iso of the service pack – not a complete OS image. The normal OS image is like 572 MB…this item is only 450MB.
Thanks anyway…
Does SlipstreamerXP take care of it?
Computer Guru,
Even with SlipstreamerXP you need to do the slipstream in a 64bit environment. It will not work with a 32bit OS
The command Doesnt work :(, I am running Windows XP x64 under VMware, there /intergrate just gives me a Window which tells me about all the switched :(, That’s it, no installation happes 🙁
/integrate
Check your spelling… tsk tsk
I figured out how to slipstream SP2 for an x64 XP CD fileset while from 32bit Windows. Download the Windows2003 SP2 32bit version (WindowsServer2003-KB914961-SP2-x86-ENU) and the x64 SP2 (WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU) files from MS. Extract them both with your favorite compatible file archive util ( I used Uniextractor ). Copy the binary files (dll/exe/msi) from the 32bit version’s ‘update’ folder into the ‘update’ folder on the 64bit version. I used nlite 1.3.5 to do the integration but I suspect the appropriate commandline execution of ‘update.exe’ would also work.
-felipe
Brilliant tip, FelipGeek!
Good work figuring that one out.
@FelipeGeek
You could just keep the SP2 installer on your hard drive, install XP x64, then install SP2 from the installer (first thing you do)
Then while you’re in XP x64, you create your slipstreamed CD.
Then you won’t have to download two service packs
Apokalipse, while that is good in theory, it’s not as practical as it sounds. Slipstreaming a service pack is a much more effective and bug-free method of installing it than creating a new install then putting that on top – plus a much cleaner route.
Even Microsoft recommends for those that have issues upon installing SP2 to slipstream it, then perform an in-place upgrade (i.e. repair install) with the new slipstreamed media.
“Apokalipse, while that is good in theory, it?s not as practical as it sounds.”
I’ve just done what I described yesterday, and I’ve had absolutely no problems.
It is faster to install service pack 2 from the hard drive, as a hard drive is faster than a CD (especially for me, since I have a 10,000RPM Raptor hard drive)
Plus, it’s not installing the entire operating system again.
I do understand your point, but I think it is fine, and you won’t experience issues, as long as installing the service pack is the first thing you do after installing Windows.
I haven’t had much success. The SP2 loaded OK but IE7 ran like a dog and several processes kept at 100%. I gave up and uninstalled it. I use an ACER with Turion64 and 2Gb RAM.
Derek, when things like that happen it means you need to slipstream it and perform an in-place upgrade or even a clean install.
I’m just curious myself. I did this back last yr but in a S2K3 x86 and it came out as described here with the i386 folders and I had to integrate it next. However this time I’m on my XP Pro x64 and it seamed to do it all in shot. Also, if I extracted the sp2.exe file the i386 is now a amd64 folder. It worked but was just curious why the folder difference and why it didnt leave the extracted folder to the C:\sp2 folder like last time. It showed as coping to c:cd something (to fast to read) and was done. I press OK and the xp CD folder is now bigger by a few.
Well, the folder-naming descrepancy is easily explained away:
i386 is a computer architecture, used to refer to the current generation of x86-compatible processors.
Amd64 is the term used to describe the x64-capable computer architecture (now used by both AMD and Intel – the latter is called “EMT64” but is fully compatible).
So on an x64 installer, you’ll have Amd64 instead of i386 and vice-versa.
As for c:\sp2…. I’m not sure of what exactly you typed in the command prompt, but I don’t see a reason for that folder not to be there if you typed the same thing as last time…
first thx for this program
please i need the password of this win ( Service Pack 2 for Windows XP Professional, x64.
pn-OD XPP01.021
XP Pro SP2
English
plz send serial number
I did the slipstream as above. I did it to my XP x64 with SP1 cause it’s the only CD I ever had. It worked but now I don’t get the Number lock on enabled as loading, not till I actually enter a user profile. However, our profiles consist largely of numbers and would like to have number lock on when loading to log in screan. This happened to “2” different SP2 slipstreams. Is this normal I have “2” XP x64 SP1 CD’s one” ARMPXVOL_EN and other is XPMPXVOL_EN. Bothe came out withouth numberlock enabled at log in screan. How can I correct this for descktop systems with 12-key keyboards?
Thankx in advance!
I believe nlite (a program to customise a Windows install CD) gives you the option to enable or disable numlock by default.
Thankx, but I was told nKite was 32bit and am running in bothe Server and XP x64. Also, I know how to fix in regedit, but it only fixes as described above, enabled just after I enter a profile (tested when not using 10-key, to see that it does enable just as it’s loading user settings.
Did something in SP2 change this for non 10-key or notebooks? Would slpi streaming a origional CD (w/ no SP1) work the same?
nLite can be used for both x86 and x64 copies of Windows, I think. The program itself is x86, but it’s compatible with x64 versions of Windows, too.
nlite does work when modifying XP x64 edition. I tried it myself.
Though, I did modify it (XP x64) while using XP 32-bit. Did you mean that you can’t run nlite itself inside a 64-bit OS?
No, there shouldn’t be a problem with that…
Nuckin, where did you get that x64 nLite info from?
RE: “where did you get that x64 nLite info from?” XP x64 was issued Corporate CD with SP1 already added when I 1st recieved in ’05. I forget where I got nLite from but it was a free link from a site with an article for slipstreaming XP Pro (x86 at the time). Ya, ut does look like I could do it in an x86 OS.
I just wanted to know why I had Num Lock enabled before an dnot now after SP2 integration as used from this here command prompt and another one as well?
If I do get nLite to work, how do I make sure Explorer 7, Media Player 11(will this overwrite MP 10?, Media Run Time Encoder 9.5 for x64, and Net Framework 3.0 (do I need to leave 2.0 in?). I need to leave the CD in Tact except for removing old messenger and add current one.
For my own 3 workstations, I do use and the Intel RAID on ICH9R so it can bennifit me to not have to do this via (f6) floppy anymore. Where do I need to use or put that iostar sis32 driver for Intel Matrix RAID?
I’ve downloaded the file “WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe” but when I try to start it it says “WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe\ is not a valid Win32 application”. What should I do? Any kind of advice? Thank you
Sounds like your running it on x86 – this is only for x64 platforms.
I can confirm I was able to follow FellipeGeek’s instructions to slipstream an x64 setup from an x86 machine. I downloaded both the SP2 exe’s, extracted using 7zip (extract to a folder near root to avoid long filename problems), copied the exe, dll, msi files from the x86’s i386\update folder to the x64’s amd64\update and then ran the amd64\update\update.exe from the command line using /s:. eg I had copied the win server 2003 files from the iso image mounted to my z-drive using:
xcopy /E Z: C:\winsvr2003\integrated
so my update command was:
c:\winsvr2003\amd64\update\>update.exe /s:c:\winsvr2003\integrated
Now time to see how the install actually goes…
thanks FellipeGeek!
The “Microsoft Corporation.img” can be extracted from the existing CD using ISOBuster Trail version (http://www.isobuster.com/)
My scanner is a HP scanjet 4600. HP only provides basic drivers for XP X64, which work ok in SP1. After installing SP2 the PC didn’t connect to the scanner, although it “saw” it. Removed SP2, everything ok.
Which part of SP2 causes this?
I ista Business, Ultimate or Premium ista thing. also I no longer get the extract with option in the “right click” menue for the service packs like under S2K3 X64.
The cmd method still worked so now if I have them extracted, what is the manual or simpler way to update the amd64 folder? Does copy and replacing the extracts to teh CD amd64 folder count as slipstreaming?
Thankx in advance.
OK I figured it out after many trys. I had to create the shortcut and run as admin and it worked like before no probs under Vista Business x64 to create my XP SP2 x64 CD.
This shit isn´t original xp 64 sp2. Fuck you
@ joe90;
Dude, what you bitching about, or at who?
@joe90: are you high, mate?
I don’t see any reason as to why Microsoft would have a “non-original” SP2 for one of their OS’s for download.
I was able to integrate the service pack but for some reason my bootable dvd just freezes on “loading windows”, right after all the install files are copied. Any ideas?
May I suggest that you check your content before making it public. It has the effect that people believe you to be an expert when in fact there may be some doubt.
Firstly your site nerosmart.net alludes to the product ‘Nerosmart’ and you directly refer to it i.e. ‘if you are using Nero, it will look something like this..’ but in using NeroSmart it looks nothing like ‘THIS’. Every attempt I have made with Nero to produce an image, iso or any other form of bootable xp64 install disk has failed due to the confusion and ambiguity generated by Nero and sites like yours. I close by further pointing out that your recipe for slipstreaming contains a glairing error and if there is one such obvious error how many more and I quote:
‘In the example above, this is the x86 installer being used and the Windows XP x64 CD has been copied to C:\XP64\’…. then further down:
‘5.File Browser area, navigate to c:\xp. Select all of the files inside of that directory and copy them over to the left side for burning.’
Perhaps this is simply another manifestation of the hoardes on the web who are both illiterate and incompetent.
@sam hansen
May I suggest that you stop being a smug prick and use your brain for a minute or two.
The instructions tell you exactly what to do to make the disc bootable.
And anybody with a pulse would be able to figure out that you need to copy the install files, even if the directory stated is incorrect.
If you have difficulty following the instructions, then clearly you don’t have the authority to call those incompetent who do understand the process.
I just wanted to thank all of you for the great info! GURU- thanks for putting this up. Much a$$ pain was avoided.
please key for Win. xp SP2 64-bit
where can i get a bootable xp 64 bit with all procedure
plz… answer me i am in hurry !!!
@John
Go to Best Buy and buy a licensed copy, it’s bootable and everything!
Great, buy another copy even if you’ve already got a valid license.
Do I need to extract the service pack 2 before I integrate by running the update.exe from the command line integrate or can I just run the WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe directly in the command line integrate. They both seem to work but is there any difference?