Windows XP SP3 Creating Havoc
ozmanjusri writes "According to Information Week, within hours of its wide availability Windows XP SP3 had drawn hundreds of complaints from users who claim the update is wreaking havoc on their computers. One user said in a Microsoft newsgroup: 'I downloaded and installed [the SP3] package for IT Professionals and Developers on one of my computers. Now I can't get the computer to boot. I don't think Microsoft should have made this a critical update.' Other sites including IT Wire are also reporting problems, which include include random reboots or the inability to boot at all." Note that XP3 won't install on systems running beta IE8; and after a successful SP3 install users will no longer be able to downgrade from IE7 to IE6.
I have installed SP3 on several systems, and I have only had problems on one. It was my laptop, and I had known there were problems with the underlying Windows installation for months but wondered if SP3 might fix them. It did not. It ended up in an endless cycle of BSoDs from which it never did recover. I ghosted the drive, wiped it clean, and installed from an XP CD with SP3 slipstreamed. Now the laptop is running better than ever. I am not sure if SP3 has anything to do with that, or the fact that it's a fresh install with new, recent drivers. (most likely the clean install.)
The BSoD/stop errors I received pointed to a driver issue with DEP, but without being able to boot even in safe mode there was no easy way to debug the problem. I could have tried a repair install, but I felt more comfortable starting from scratch.
One could make a similar statement about SP3.
Not that I'm a MS fan-boy, far from it.
Sooooo? Is there going to be an SP3a?
It may be paranoia, but I am considering that given the welcome that Vista has received, Microsoft had no choice but to do this. Producing two OSs that compete with one another is insanity... especially when the product that's winning is not the latest one.
So the solution is fairly obvious - if you can't improve Vista, you can make XP worse. That way, people know they're going to be dissatisfied with your product from the get-go, but at least they'll buy the latest one.
Maybe this was just a sneaky way of trying to get people to 'upgrade' to Vista. Then again this is probably more evidence of a broken process at Microsoft.
Jumpstart the tartan drive.
Did anyone else get this? Microsoft really screwed this one up. Not only did they release an AUTOMATIC UPDATE that cannot be installed unless you close your antivirus (which isn't possible for my company's antivirus - the only choice is to unload it from the workstation), or to run this utility that changes permissions on all registry values and windows files, BUT they ALSO provided instructions that only make sense in a VISTA environment. For example, telling people to right-click and go to Run As Administrator, or referencing "defltbase.inf", which is a file you only find in Vista.
It has a banner add at the top, but at least it doesn't have the rest of the cruft on the page.
The simple truth is that interstellar distances will not fit into the human imagination
- Douglas Adams
FTA: Typically, the glitches are due to conflicts with software, such as drivers, system files, or applications already resident on the user's PC. The machines arrive in a pristine state. Users then add, sometimes compliant sometimes non-compliant software, hardware, and modify the registry. There should be no surprise that issues will arise. There are less-popular operating systems with upgrade / driver issues way worse than this.
Cogito Ergo Sum
to all the beta testers out there. You know who you are! We appreciate all your hard work, and when we install SP3 several months from now, when it's ready for release, we'll be sure to think of you sucke^Wkind folks.
Haida Manga
Four systems and counting , including my own laptop, i have upgraded to SP3 and not any problems of any kind. Systems even seem snappier. I did have to replace the standard Windows boot screen on my lappy. SP3 would not install with a custom boot up screen. For all my bile directed at Microsoft, XP is the most stable and versatile Windows I've ever used. People don't want to switch because of that, and Vista offers nothing at all compelling. Especially since it expects you to abandon all your current hardware and peripherals.
Fiat Homos et Pereat Theos
You are an idiot for not installing SP2 as soon as it was available.
"If it ain't broke don't fix it" does not apply to computers unless you're an end user who doesnt understand how to read the technical benefits you get from a given upgrade/patch/service pack.
Well, do you consider an OS with security holes broken or not? Personally I do; I'd rather deal with MS trying to fix my computer after an SP messes something up than with a virus trojan that I may not even notice at first.
"Not that I'm a MS fan-boy, far from it."
Don't worry. I did not feel that was the message you were trying to put across at all.
Your message was clear and unambiguous. You're a fan-boy of murder for hire.
Patch size (in MB) = X
(X * 3)/100 = T
T = Time patch is ready for release to public (from microsoft release date, in months).
This puts Service Pack 3 general release for February 2009, and i'm not touching it until then.
Finally had enough. Come see us over at https://soylentnews.org/
News about XP SP3 when it's delayed, when it doesn't work with some server...
No news when it's released.
News again when some minority of systems fail the SP3 installation.
I love that Microsoft is held to 100% success rates, too. 100%. Even though there are millions of systems with trillions of potentially screwed up configurations to miss in testing, 100%.
Unless testing for SP3 was going to take hundreds of years, stuff was going to slip through.
According to Johansson, there appears to be two separate issues. One affects only AMD-equipped PCs sold by Hewlett-Packard Co. "The problem is that HP, apparently along with other OEMs, deploys the same image to Intel-based computers that they do to AMD-based computers," said Johansson. "Because the image for both Intel and AMD is the same, all have the intelppm.sys driver installed and running. That driver provides power management on Intel-based computers. On an AMD-based computer, amdk8.sys provides the same functionality."
Running the intelppm.sys driver on an AMD-powered PC isn't normally an issue, but on the first reboot after a service pack installation, it causes "a big problem," Johansson said. The machine either fails to boot or crashes and immediately reboots.
The other problem, according to Johansson, also seems to affect only AMD machines, and involves an error message indicating trouble with the PC's BIOS. Johansson said that the ensuing recommendation to update the BIOS is "most likely not your problem," but said that the problem may be isolated to a specific motherboard. "Possibly, it is related to computers with the Asus A8N32-SLI Deluxe motherboard in them," he said.
Whenever a SP/major update is released, can't you always find people who are complaining and having trouble?
-- if you mod me down, I will become more powerful than you can possibly imagine
You mean people actually install service packs? I haven't done that since... well.. since before windows 2000. I guess not everyone can just back up their files, slipstream the latest service pack and do a clean install. OK, just kidding thats not practical at all, but that's a shame, cause everyone would benefit from a clean install of XPSP3.
My XP vm has never been smoother.
Modding Trolls +1 inciteful since 1999
I just bought a Lenovo laptop with XP Pro for my wife that came yesterday. The first thing I did after all the initial registration, etc. was to run Windows update. To my surprise, SP3 was available so I installed it. After the install, TCP/IP would not work at all. I called Lenovo and they told me to reload from restore partition - SP3 wipes out TCP/IP for that laptop. After the reload, I updated individual fixes (64 of them) and turned off Automatic Updates so it won't try to slip in SP3 again.
If they released this as a critical update, wouldn't it be picked up by auto-update if you have that turned on?
The rest of the people can't send in a complaint because their only computer won't boot.
So the point is, make sure you have your linux bootable cd available when you install the XP3 patch, so that if this is the issue you can successfully boot up, go in, delete that offending file, and you'll be good to go!
-Styopa
At the risk of getting flamed to hell (this is /.)
SP3 actually improved my old thinkpad. The XP copy on it was really struggling after years of being used as the 'windows toy'. No media (my bad) so I've never reinstalled it. I allowed SP3 on with some trepidation, but the end result is that the machine is a darned sight more spry (fast and responsive) than it was before. I think the installer basically did a good job of repairing the OS while patching it.
I was pretty surprised.. it's pretty rare that anything from Redmond makes me feel that it's an improvement..
"Oops, I always forget the purpose of competition is to divide people into winners and losers." - Hobbes
Not being able to downgrade to IE6 is a bad thing?
I'm glad MS figured out how to secure Windows totally.
I am Bennett Haselton! I am Bennett Haselton!
...and on another note, has anyone noticed that 99% of wikipedia's screenshots of windows apps have gone from XP to Vista? It's almost as if something, some...strange force, is trying to convince me that anything less than Vista will get me laughed at...
No they are not.
You should wait to see what happens on other computers before doing any OS upgrade.
If you are a single user, wait, if you are a company put it on test machines.
Your an idiot for not understanding the the PC upgrade history is far from stellar. Yes, SP2 was fine, but that's hind sight.
"If it ain't broke don't fix it"
That's exactly how you should deal with computers.
The Kruger Dunning explains most post on
Downloaded and installed on my six year old ThinkPad A31 last night -- everything works fine. Didn't even take all that long.
Might be redundant, but I think its become important for people not having problems to report on that now too, considering the heat M$ takes on just about everything these days. If my old computer can handle the process of upgrading to SP3, not sure why its "wreaking havoc" with so many others...
Here's my theory, they did this on purpose to make everyone hate XP so we will now flock to vista... They can even say.. hey look it's an old OS it's going to have problems like this, that's why you need to buy Vista.. Then you'll have the same problems because you moved to a new OS, which is better because it's new...
Now Kathleen Turner is as bloated as XP is, good comparison
Success is not the result of spontaneous combustion, you must set yourself on fire.
I wouldn't really apply a Service Pack on a live system. Integrate the Service Pack 3 to your installation CD, and install a clean OS. There are so much different configurations that a Service Pack, which deeply modify the operating system, it's almost impossible it might not cause issues on a running operating system. I've installed a slipstreamed Windows XP Service Pack 3 without any problems.
...when I attempted to install it on a standard Compaq Evo N610c laptop. Other than a 2nd NIC installed in a card slot, this is a vanilla machine with IE7 and Office 2003.
The SP downloaded and began the install just fine. Ran all the way to the end, which took over 2 hours, and then popped up a dialog after reboot that the installation "...has failed and will be rolled back. This is a two-step process..."
Pressed OK and it took about 45 minutes and a reboot to finish. After boot, I got the "your system has encountered a serious error" dialog. So far, everything SEEMS normal, but I haven't done much as this is my 3rd PC, hence his starring role as "SP3 sacrificial lamb".
Disappointed, but not particularly surprised this SP has issues.
I am my own gestalt.
so botching as many XP installs to make people shift to Vista is in Microsoft's and their shareholders best interest.
I see this as nothing more than business as usual, bate and switch.
A casual yum update has broken various Linux servers of mine over the years. I'm usually a lot more careful doing yum updates than I am with Windows updates - not because one is inherently more destructive than the other, but because there's almost always a variety of one-off packages that it can break. Microsoft's casual [security] updates are usually fine, but even their service packs don't seem to break too much.
As usual, a couple XP installations get broken and there's mass histeria.
My system is working very well after the upgrade. XP feels better with XP SP3. I can imagine though that lots of XP users have all kinds of stuff installed over the years and this SP is a major update that can have many side effects.
"It's funny that to fix Microsoft Windows, it's faster to just wipe and re-install from scratch rather than try to fix the issue."
Have you read some of the news reports about foreclosed home being stripped of plumbing, wiring, appliances, fixtures, even doors and windows? Some (many?) of these are proving to be cheaper to just rip it down and build new when the market comes back. Maybe even cheaper than waiting for someone to start up a meth lab and blow the whole thing to toothpicks.
It's *usually* faster and easier to rebuild a Windows XP/2K machine than to fix any of so many nasty malware infestations. And '9x/ME machines need to be removed from the 'Net and recycled. Ask Microsoft. BTW, tag that admission *honest*. A rarity for Microsoft, and typical that they would exercise it in an admission of OS security failure.
But that's just the way it is. I started spending my anti-malware research time optimizing data recovery and reinstallation, rather than disinfection. So much more effective to nuke the site from orbit.
deleting the extra space after periods so i can stay relevant, yeah.
This is the status quo. How many times have you called the help desk to report a problem, only to have them tell you to reboot? When you call the company that made your computer, and you're in the queue waiting to speak to someone, in their litany of instructions you will hear the following: "Please reboot your computer".
When did the "Microsoft Solution" become commonplace? When Microsoft managed to convince the people who use their software that the expectation that their information technology infrastructure will be reliable is unreasonable.
Several factors contribute to this problem: disclaimer of fitness for an intended purpose, lack of liability, a software ecosystem that has relied for far too long on "experts" who haven't read the book that came with their certification, and a lack of any real measure of lost productivity due to poor information technology decisions, in general. And Microsoft has been able to use its dominant position to stave off market forces. The market isn't making Microsoft's software better, and neither is Microsoft.
But good luck getting management or anyone else making a purchasing decision to embrace the idea that a software company should be at least as responsible as any company that manufactures a real, physical product for the quality of their product.
Slashdot is my Mercer Box.
it totally thrashed my computer, now won't start at all - constant BSOD's. Also, there's a burning smell coming from the back of the tower; I could swear its killed the fan on the cpu too. Oh, and it constantly leaves the toilet seat up now when it goes to the loo, and keeps looking at my girlfriend's ass.
Fucking Microsoft.
*shakes fist*
throw new NoSignatureException();
Usually, you know what hardware you have and you apply the correct drivers. Also, many setup programs have safety checks built in, as in "stop installation when correct chipset is not detected".
In this case it seems that HP and others took disk images from Intel machines and copied them onto AMD machines. That circumvents any test the driver developer might have implemented in the setup program. At best, the driver will re-check for the correct chipset at startup (and what then? Refuse to run and leave the OS minus an important driver? Almost as bad).
In short, the really surprising thing is that the computers did NOT fail under SP2. The OEMs made a pretty stupid mistake here and deserve to be bashed.
C - the footgun of programming languages
Better application compatibility. Some of my older games worked in Windows XP right out of the box. In Windows 2000, you would have to download some toolkit and mess with some settings before they ran properly.
If you can't fix vista...Break XP
That is one way to boost Vista adoption rates.
Can't make Vista better ? No problem. Lets just screw Windows XP.
No problems with my Intel processor based systems, but blue screens at bootup on all of my HP and AMD processor systems. The fix is to boot into safe mode, change one value in the registry, reboot and viola! I'm back in business. Even granny could do it. That's probably why Microsoft failed to mention it. ;) Oh, my Vista SP1 install on HP took six reboots and about two and a half hours. It failed the first three times. I'm going to make some money from these service packs!
-- Wondering how long until the internet becomes fully corporatist, like television.
Yes, obviously they do. The technologies in Vista are key to their leveraging their desktop monopoly into other areas like entertainment.
However -- this is NOT the way they want to do it. Especially now.
Microsoft is a big picture, global strategy kind of outfit, and right now several of the underpinnings of their grand strategy appear cracked.
IE, while still the dominant browser, has lost significant market share for the last four years running. MS is a perennial nobody in online services, something the Yahoo acquisition was supposed to fix. They'll be back, but with every month their ability to execute a dramatic turnaround using their browser and desktop monopoly drops. While arguably the office monopoly is more important than the desktop monopoly, the desktop monopoly is the fulcrum and DRM is the lever by which they hope to become the dominant player in digital entertainment. That's why they aren't hot and bothered about Blu-ray; they don't envision a future where people access information by any old third party hardware.
Why was Vista such a dog, after they'd delivered two successive solid releases in the Windows franchise (2000 and XP)? Because they had too many agendas; too many strategic partners to keep happy. Vista is not architecturally worse than its predecessors, in some ways it is better. It's just unfinished; MS had too many strategic imperatives to satisfy, imperatives that were useless or meaningless to customers.
I think what we're seeing is a world of technology that is too complex and dynamic to be orchestrated by the strategic plans of any single company. But MS is a big picture, grand strategy kind of company. There's lots of valuable pieces in that company too.
The irony is we may look back in ten years time and conclude that MS shareholders would have been better if the anti-trust case had resulted in a court-ordered breakup. Since MS dodged the break-up bullet in 2001, its stock price has lagged the NASDAQ as a whole.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
I hate all those companies that sell non free crap. Why should I pay them for the decades of developer time that they pay for when creating their software? Grrrrrrr
which is totally what she said
Thank you for both warning and revenue.
Signed, the participants of the SP2 public beta.
I just read Slashdot for the articles.
Microsoft is telling people that the problem has to do with script blocking by various security/anti-virus/ad-malware products that are installed.
...) BEFORE you install SP3. Then, you may reinstall your security software. While on the phone with one of their Indian or Pakistani speaking reps, they never once mentioned anything about network card, adaptors, drivers, .net, etc. It was all security product related.
They say you need to uninstall your security software (McAfee, Norton, Symantec,
Banjo - The more I know about Windoze, the more I love *nix
There is an issue with XP Service Pack 3 when installing on a Mac with BootCamp. During the free disk space check, the SP3 installer reports that there is not enough free diskspace.
The fix is a quick registry edit:
Create a regkey(REG_SZ) (String Value) called BootDir under HKLM\Software\Microsoft\Windows\CurrentVersion\Setup and set the value to C:\
Reboot, and then proceed with the SP3 install. That little bit of knowledge cost $295.00 and 3 hours of my time.
-ted
It doesn't matter if we're talking about OS, tools, Office, or service packs. You should *always* let somebody else go first, and wait for an "x.1" version.
What do you expect if you try and install SP3 over a machine thats been running SP2 for god knows how long and picking up gunk from the internet etc, slowly corrupting drivers etc.
Any sane person, and im one of them, would slipstream SP3 into the original release and install that fresh....
So after doing this i have:
The one thing i had to do was download IE7 off the net, i tried using the one from AutoPatcher (how i loved thee), but it wouldnt install. Other than this its been brilliant.
So the person who started this topic and the pages around the net are proof that a certain segment of people will always try and do things the hard. I never thought id say this, but stop blaming Microsoft, they did their job and SP3 is fine. Again some people just like the sound of their own voice in internet forums, and for once its not me, its the incompetent whingers that post this crap about SP3, take some ownership you mental midgets....i suspect most of the whingers are also the ones without valid product keys too................