..MS state that affected users should update to Vista - and it won't be long before many more problems rise to the surface - somewhat suspiciously - for XP, causing people to upgrade to Vista out of shear frustration with XP.

62 of my companies Dell AMD machines are all working fine since SP3. A mixture of Precision M65's, Latitude 110L 120L & 131L's, Precision 370 & 360's, Optiplex GX280's etc. ALL AMD ALL 100% working on XP SP3 :)

...No problems for me when I installed it via Windows Update (well, Microsoft Update) on my Intel P4, or since then for that matter.

"Because the image for both Intel and AMD is the same all have the intelppm.sys driver installed and running. [...] On an AMD-based computer, amdk8.sys provides the same functionality."

Windows Update is normally quite willing to replace device drivers and surely amdk8.sys is a better match to AMD hardware than intelppm.sys? If we accept the story that OEMs cut corners on their disc images, it still doesn't explain why WU didn't offer to repair the mis-match as soon as the machines were connected to the net.

I thought that would get your attention. Although on a serious note, I've installed SP3 successfully on our MD's home AMD based PC, which has the bog standard HP factory image on it (of course I tested it on a image of the PC before hand). So I wonder if the problem lies with users that have installed any of the recommend hardware driver updates within Windows Update?.

Well, f*ck me, it's nearly time for a beer, who's round is it?.

"We also asked AMD to give us its views on the XP service pack debacle, however, at time of writing it is yet to provide comment"

They're probably still trimming the expletives out of it :D

What has happened at Redmond recently, XP SP3 reboot infinity, Vista SP1 reboot infinity. WTH The fix needs a fix, which will probably need a fix also ad infinitum. So glad I didn't press that install button after I downloaded it, have now pressed the delete button instead.

No explanation necessary with the icon ;)

I think he meant downgrade to vista. I can't see any "up" side to a remake of the windows ME fiasco which Vista is turning out to be.

To all else, I downloaded the 500 meg ISO image and have isntalled it on both intel and AMD chipsets with no problems. The 2 AMDs I've tested on were a XP2800 Athalon and XP3200 Barton.

No spontaneous reboots or instabillaty detected as of yet.

Improved system performance and memory usage is down though which can't be a bad thing.

If you install the SP manually then I don't think you will have many problems. It seems to be the automatic update which is causing most of the problems.

I have installed SP3 on my own and some friends' systems, which included two HP AMD PCs, and no problems. In fact, of six systems so far, I only had one Pentium system that had an issue, and that was caused by MSN Messenger! Bizarrely, it first complained about Live Messenger being open during the update (kicked off from the Update webby), then wouldn't complete the update until I'd uninstalled Messenger completely. After that, the SP went on fine and then I could re-install Messenger. Most weird!

I had a hell of a job installing Vista on my Intel-based laptop. It would generally freeze about 5 seconds into setup unless I started it in safe mode. That was fine except it wouldn't let you continue in safe mode after the first reboot. I can't even remember how I figured it out because there was practically no information about the problem online but disabling intelppm.sys with the help of BartPE after every reboot allowed me to finish the installation. I don't entirely blame Vista though. It was probably some fault with the machine because enabling the processor driver in Linux also caused random crashes but those only occured about once a day, not once every five seconds!

I have an HP Pavillion Ze2000z with a Mobile AMD Sempron 2800+, and it went through the manual AU just fine.

System Information shows the power management is controlled by amdppm.sys and that file is 33k and dated 4/17/2007. A copy of it (with the same time stamp) is also in the SP3 "ReinstallBackups" area, which means its the same driver as before SP3.

A search of the hard drive found that amdk8.sys was in the Windows\system32\drivers area but that it was zero bytes long and a date stamp of 4/13/2006. A subsequent search of the hard drive found intelppm.sys at 32k in the same directory, with copies in the Windows\ServicePackFiles\i386 area and also in the Windows\SoftwareDistribution area. All intelppm.sys are date stamped 4/13/2008.

"If we accept the story that OEMs cut corners on their disc images, it still doesn't explain why WU didn't offer to repair the mis-match as soon as the machines were connected to the net."

Windows Update didn't do the update in this case. The downloader and updater in XP SP3 did. We're also talking about a processor update. Ever hear of downloading a new driver for your CPU?!

Microsoft made Sysprep's limitations quite clear -- oh, for those who don't know, Sysprep is the utility that permits mass duplication of an installed Windows 2000 or Windows XP machine -- and an important limitation is that the target machines' processors must be the same type. This was more obvious back in the day when Windows NT supported four unique processors, but it's still relevant today when switching between Intel x86 and AMD x86 processors.

And now we know why.

Come to think of it, I always wondered why my XP SP2 image wouldn't boot on an Acer AMD laptop. To think I blamed Acer, when the fault was mine. And this had nothing to do with SP3.

As for the SP3 ISO working better than the download, I'd believe Gary's story since the "full file" kit would contain the AMD driver code by default. The online version would only download updates for files it saw, and if there wasn't an amdk8.sys file, it's not going to waste time downloading it.

Sounds like the bug is in the online version of the SP3 installer. And it seems like a simple enough fix -- make sure it downloads all processor-related drivers anyway, regardless of what files it sees.

What about the full-file installer? We see that the ISO download works. What about the huge update you'd download to install to multiple PCs, without needing a CD burner?

My one and only attempt at contacting Microsoft support had me first on hold for 2 hours and then got me to scan disk my hard drive. A task taking over 4 hours on that particular drive before they would even try to help diagnose my problem.

The fact that I am now a happy Linux user is driectly due to the lack of support the support line gave.

Cos she's the only thing I know of that goes down more often than an SP3 update..

It borked my Celeron based Maxdata PC this morning with the repeated re-booting problem. Luckily it would still come up in Safe Mode (although not with networking, which might be a clue?) so I was able to uninstall SP3 and get on with something more productive.

Tux cos that's the OS on all the other PCs in the house.

No problem on my Athlon 2600 using WU although I built it myself so there's no chance of a shonky OEM build getting in the way. Much as I like most MS products (excluding FrontPage, Sharepoint, Vista and Office 2K7), it sounds suspiciously like someone didn't do enough real-world type testing and is now hurriedly trying to wriggle out of it.

Question: in light of these recent problems with Vista, it's service pack and now the XP service pack, will anything change with, or at, Microsoft.

By the looks of it there are a few folks at Microsoft needing their asses fired straight out of the door never to work again. Not least Mr Gates for letting his company name be tarnished by idiots, slackers and hangers-on.

Hey Bill, start firing people (yes firing, NOT asking to resign) big title, big salary managers first, you'll soon get the rest showing some pride in their work for a change.

Ummm,

Vista sales are down and lots of people and companies are holding on to XP and everyone expects XP SP3 to be good? The only reason any machines are working so well after SP3 is probably because Microsoft made a mistake :-)

I downloaded the full .exe (not the .iso one), didn't use windows update because it sat there for 20 mins doing nothing (preparing to download). Ran .exe, no issues whatsoever, and no difference to speed, etc, either. I'm running an old Xp2600, a home-built machine which I won't go into the "specs" of (it was a high-end machine *ahem* years ago) so I'm guessing that either there is an issue with WinUpdate (doubtful after seeing, for example, Steve Pettifer's reply) or something is up with certain OEM installs as suggested. If it was an AMD issue, surely every AMD system would be affected? Which manufacturer will get officially named and shamed first?

(Linux Pingu since there ain't a "brown trouser syndrome" icon, as I haven't had a single issue with my Vista box, and now SP3 works perfectly. Bet I'll have a mare with a Linux install......

My IBM T41 (only machine on Win as my wife *NEEDS* Outlook, you know those anti-IT people) worked fine till SP3. Not it drops 'Net connection after about 1-5h. I heard the same from some of my friends.

Accepting it's probably the most bog-standard laptop out there, how could it pass through Q&A?

As I was unable to get onto a WU server, I downloaded the full file (not the ISO), and manually updated. No probs at all for my venerable Evesham P4.

Why do people always blame Microsoft ....

Think of all the 3rd party software/drivers out there that interacts with the OS!!!!

"Ever hear of downloading a new driver for your CPU?!"

Yup. Used to download new PowerNow! drivers for my laptop all the time. ;-)

I tried the update, then I downloaded the ISO and burned to disc and got a nice shiny welcome screen and a help document about SP2 (!)

At first I though I'd wasted a disc downloading the wrong file, but Micro-pull-a-fast-one-soft just couldn't be arsed to update the "read me first" file.

Anyway, after installing, same result with both the download via Windows Update and the ISO version. I am running XP Pro SP2 on an AMD powered crate with Asus MB.

XP Pro installed off a proper XP CD and update to SP2 via another proper CD , bla de bla.

(Paris - cos' she wants me)

And is MS going to provide these users a free-of-charge upgrade key to allow that?

It's high time that doing so became the law -- and not just when an upgrade fails, but whenever a company withdraws support for any program less than 10 years old.

My AMD PC nearly died because of SP3. At fist I thought it was because of Spybot blocking some registry change, several hours for trawling through restricted lists came up with nothing, then I noticed the blogs. D'oh. I only got away with it because my PC is so slow at booting I managed to open and activate system restore before it realised what was happening. Take that SP3 evilnesses!

Thanks for the tip off about the ISO, will be trying it. Once it d/ls.

Runs fine on my Vic20... Going to try it on the ZX81 next!

I'd just like to say that my Mandriva system is in full working order

"Windows Update didn't do the update in this case. The downloader and updater in XP SP3 did."

Yeah but my point was why WU didn't resolve the problem on these machines long before SP3 came along. Presumably it just didn't notice the mismatch.

"We're also talking about a processor update. Ever hear of downloading a new driver for your CPU?!"

A fair point. I *have* heard of motherboard upgrades, but they aren't common and I don't know if anyone ever expects to run the unmodified OS image straight off the hard disc. It wouldn't surprise me if switching between AMD and Intel hardware just isn't on Microsoft's test plan for Windows.

OTOH, if all this theorising turns out to be true, you can be fairly sure that future versions of WU *will* check for abuses of sysprep. Microsoft may not be the guilty party here, but it is Microsoft customers who are getting grief and MS generally take the view that Windows should try to work around common cases of cretinism in OEMs and applications programmers.

I slipstreamed SP3 into WinXP by downloading the .exe file. I then installed WinXP-SP3 using VMware 5.5. Ran fine. I'm wondering if it will work if installed as the real OS (no vm). (I have an AMD X4)

Paris-cause anything with "service" in it's title has to be sexy!

Updated 4 computers with it. the P4 at work was done last week when I it came out. Still running fine. 3 of my 4 at home are AMDs (2 are dual core), and worked without a hitch. Thinking about switching my EEEPC over to windows to see how it looks, and it might get SP3 too.

Think the main issue is folks with bad installs to begin with. I've built 3/4 of the systems I work on, and the others were fresh installs *not* using OEM discs.

My homebrew AMD box has a MSDN sp2 install. SP3 killed it stone dead, batching spuninst.txt from the recovery console has made no difference whatsoever. Reboot city with a different bugcheck nearly every time. time to go hackintosh with this one, methinks.

Yes, I tried Penguin (after removing Vista nuked my XP partition and the partition tables on most of my different drives), and even got 3 of the 5 extra drives fixed with it, but Adobe have cacked up the latest version of Flash, rendering the BBC iPlayer vaguely unusable. Couple of issues with the nVidia drivers also (slight tearing when watching HD videos fullscreen) means that Linux still can't compete with XP yet.

Fresh nLite'd install of XPSP3 later, and everything is working fine, even the 2 drives that Ubuntu refused to acknowledge the existence of (other than an excessively long loading time when they were plugged in)

So yeah. SP3 good, Penguin bad, at least for the moment.

After many hours of secret research by my cat and aging incontinent dog I am pleased to confirm the following:

A PC that has never had an Intel CPU near it had not even a sniff of "Intelppm" in the registry pre SP3 install.

After installing SP3 and getting the bsod, we proceeded to paw in a top secret registry change after finding that the evil boffins at Micro-I-want-to-shag-your-mother-soft(ly) had added "Intelppm" into the registry during the SP3 process.

After following the top secret (you can find it anywhere) registry tweak the system has booted up into SP3.

Questions need answering as to why Micro-I-want-you-vista-longtime-soft have seen it upon themselves to contaminate perfectly happy AMD powered systems with Intelppm.

I think this is one of many possible fixes to many different problems.

If I never write again it is because the cursed thing died after the first reboot and I will be taking an axe to my research team!

(Paris - because she thinks I look good in y-fronts)

It seems the problem was caused by not by the windows service pack, but by windows vista itself, after having the install of SP3 fail and rolling it back to SP2, i received an error message which asked me to send a report to microsoft, being an adventurous person, i click the send button. the response i got back from microsoft was helpful...

http://www.azitspecialist.com/image1.jpg

Are you sure they're all AMD? The M65 is a dual core Intel, the Precisions are P4 or Xeon, the GX280 is either P4 or dual core Intel, in fact, off the top of my head, the only one you named that I think has an AMD self destruct device^H^H^H^H^H^H^H processor is the 131L. Perhaps that might explain why the majority of your machines are reliable?

Paris. Because she doesn't know what processors in her box either.

The problem occurred "...within hours of XP SP3 being released as an automatic update ...". Says it all really. Why would anyone let anyone else do something this important to their machine automatically?

Let someone else go first. Unless you needed SP3 to fix a specific problem ... wait until its proved safe.

D

All I can say is that the guy in the posting named "Gary" would be fired for not even reading things correctly.

Of course his ISO image install fine on systems. It's installing SP3 on a system that has SP2 on an AMD system that is the problem as it's OEMs like [it seems primarily] HP who screwed up their customers by dumping an Intel image on an AMD system - against Sysprep "rules".

BlueR@nger - See above. Only affects updating SP2 to SP3.

Gordon Fecyk - You're missing the point. HP dumped an Intel image on an AMD system. It's not Microsoft's fault that HP people are incompitent.

re: "affected users should update to Vista" - Ya right. Microsoft will give free upgrades because of Hp's incompitence. More like Hp should do so. Of course who ever originated this quote must be a good dream!

I remember when I was a Banyan Vines engineer and when we got new patches for Banyan servers they would often create worse bugs than they fixed... It was not uncommon to patch the patch before you applied it to the server... I even remember one instance where instead of rolling out a whole new patch, we had to patch the patch for the patch for the server...

Most of Active Directory was designed based off of Banyan's Streettalk Directory which Microsoft licensed...

Banyan use to be a fairly popular network operating system... Where are they now? Microsoft might want to take note...

What kind of idiot company would apply a week-old service pack to all their machines?

I mean, what if the problem *had* affected you...?

1) Download and burn the ISO

2) STFU

3) ????

4) Profit

or - use WSUS.

d0rks

We have an exclusive on the release of a patch for Windows XP SP3 - it's only a short patch, and according to Microsoft's press release it will cure all the XP problems.

Have a read of the full story at:

http://adfundum.wordpress.com/2008/05/12/microsoft-release-patch-for-windows-xp-sp3/

Hi John.

Those of us with an IQ that breaches figures normally associated with room temperature have this great trick.

It's called 'Testing'.

Hope that helps.

Steven R

I have a HP Pavillion with AMD chip. It went through the reboot process. I did the research (after the mandatory swearing and row with wife) and there is existing info about intelppm on the MS website - they describe it as an unsupported configuration.

Eventually I used the Recovery Console to disable Intelppm and all is now well.

So HP sold me a machine with a crap installation - they deserve all the grief they get.

Microsoft didn't bother to test on an HP machine with an AMD CPU or to put in code to check for unsupported configurations - what sort of test plan is that?

I don't think that AMD deserve any of the grief - shame that they are getting it. I bet Intel are loving every minute of it.

NO - NO stop I take it all back - Intel paid HP and Microsoft and it is all a cunning plan to increase market share - we need either proof or counter example but it is a great theory. The arrival of the black helicopters is all the proof I need.

Cheers

Andrew

JPEG generally is unsuitable for screenshots :-)

Just an interesting note: After checking the MD5s of the service pack's EXE in the burned ISO and the EXE downloadable for the "network" installation (316 MB exe), I found they are identical (BB25707C919DD835A9D9706B5725AF58).

Curious what the Autorun.exe on the ISO/CD is doing that the network install or Windows Update installer isn't...

Coat, because all my boxes in-house are Intel based, and now I have to go home and see if I break my AMD based PC.

Are we talking problems with clean installs? Or problems with fresh builds?

An XP SP2 PC will have over 100 critical OS updates, a variety of non-critical updates, possibly some of MSs own drivers for legacy hardware (ill-advised) and a variety of third party drivers that are probably a few revisions out of date (some for hardware designed for 98SE). There are also going to be plenty of computers with corrupt system files that havn't made themselves obvious yet.

So, it's not surprising that whacking a major rewrite of the core OS onto a old installation will cause problems for some. However, if loads of folk are having problems with fresh builds with all the latest drivers and no legacy hardware, then its open season on MS.

AMD 64, Compaq machine (aka HP) - all fine.

Paris... because I'm predictable and this joke isn't funny any more....

All ok here and on my hp6110 laptop :)

with no issue. Of course, I made full images of the program partition before I start.

Last time they pulled the plug on SP3 because it conflicted with an application that very few use. One could almost forgive them this little oversight because of the small userbase.

This time they screwed up far better than last time but don't pull the plug.

In the words of my Great Aunt Hattie: WTF?

"I installed SP3 on my pirated & cracked SP2 install, full of malware and pr0n pop-ups and now it doesn't work."

Boo hoo.

My testing rig - AMD X2-4600, 4GB Ram Trusty K8N mobo - SP3 installed perfectly, no glitches, no bugs, works perfectly.

Now if Ubuntu could PLEASE write an Nvidia driver that worked I could properly dual-boot the darn thing!

My main machine? Vista SP1, has been running faultlessly now for 14 months. Maybe I'm doing something wrong?

In what way does the ubuntu nvidia driver not work? I've been using it for ages and it works fine, even to the point of running HL2 under wine flawlessly.

"Gordon Fecyk - You're missing the point. HP dumped an Intel image on an AMD system. It's not Microsoft's fault that HP people are incompetent."

Nah, everyone else blames Microsoft for this kind of screwup. Why should we stop? :-)

Seriously, this is the first time I've seen someone else post on El Reg that very phrase, "It's not Microsoft's fault." If it's already posted somewhere else, don't worry, it's just the first time I've seen it. And how true it is. Expect MS to cover for HP's mistake, and potentially the mistakes of other OEMs, however, as pointed out in other posts.

Now if only some folks would consider that the next time we see a knee-jerk article on El Reg...

@gordon RE XP images and different processors;

As long as you installed from an SP2 disc.

A little program called halfix.exe, if run as a part of the sysprep run once list will allow an XP image to run on any processor, as long as the PCI IDE patches are put into system32/drivers, and a small reg patch is run before imaging....

They're trying to avoid pulling out, putting it back in, pulling out, putting...

Otherwise, it might become a little obvious to MS's customer base exactly what the company thinks of you.

My SP3 is working though I only risked it on my works machine. So recovery time is in works time not personal time. I won't risk my home kit just yet, though they are all Intel chips. (P4s and a dual core)

@Gordon Feyck

I would be more sympathetic if this was a one off, however this is the second time SP3 was pulled and Vista SP1 (or vista in general) can't be blamed on the OEM's. Something as massive as a Service pack that will affect most of the world (lets face it most PC's in the world will be XP by now) should be thoroughly tested on everything. Not like they can't afford the virtual servers and the hardware to do the testing.

@AC Why

M$ caused the issue, so why not blame them. SP2 had all those 3rd parties working fine...

@Adrian Esdaile

You had Vista SP1 working for 14 months, with no issues. How did you get hold of SP1 that long ago, it's only been around a few months.

try linux - be free!

I use Linux - I'm typing this on an Ubuntu 7.10 system (test system updated to 8.04 yesterday)... but I still use a Mac and am required to support XP as well.... fortunately, none of my clients have drunk the Vista purple Kool-Aid yet (possibly contributing to Vista's purple screen of death? You be the judge...)

I can tolerate XPSP2; it's the closest Microsoft will ever again get to NT 3.51, which for my money was the best OS they ever shipped. I have not upgraded my XP systems to SP3 yet and have recommended to any who ask that they hold of until this shitstorm dies down... which I suspect will be sometime in the SP5 timeframe, if the company survives that long.

To say that Microsoft's best years are behind them, and receding at high warp, is to state the bluntly obvious. If they continue along the arc (death spiral) that they are presently on, sooner or later businesses will start questioning how they can get work done with systems that they have no realistic hope of supporting adequately, let alone improving. For the Linux folks (or the Mac folks) to say "Leave the Dark Side! Come use what we use!' is less than helpful, because, for better or worse, nothing else out there does what Windows does /IN THE WAY WINDOWS DOES IT/. There are millions of "support" techs, "certified" this-or-that, and managers who have drank the MS Kool-Aid for decades, have built their careers and political fortunes on being reflexively Microsoftian... and the cognitive dissonance between political survival and business necessity is going to make Y2K look like a cakewalk. The lesson we'll be able to look back on all this and understand in ten or 20 years' time is obviously "don't use single-vendor proprietary kit for critical stuff that should be standardised" - but we're VERY early in the "fear, anger, denial, bargaining, acceptance" curve.

The other part of this story, as several people have alluded to, is the rapidly, shockingly deteriorating standard of quality at Microsoft. Microsoft has always had defective software - their "Code Complete" process guarantees it - but the last five years have been stunningly inept even by Microsoft standards. Some people blame it on Microsoft's new-found process religion; others blame it on the quality of the H1-Bs they're bringing over. My strong suspicion is that they're both right - but they're both like the blind men trying to figure out the elephant by touching one small part right in front of them. The only people who can see the whole picture are in Redmond - and they're bailing. It's going to be an interesting next few years...