Digital Paint Discussion Board
Digital Paint Community => Other Stuff => Topic started by: KnacK on May 09, 2008, 12:05:46 PM
-
"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.
http://www.informationweek.com/news/windows/operatingsystems/showArticle.jhtml?articleID=207600950
-
Ya know, I wish you had told me this before. >.<
But I haven't had any issues yet, and beta IE8 needs LOTS of work so I'm not too worried about that.
-
They're making IE8 already? IE7 isn't even stable yet...
-
SP3 for Professional? Because after reading that I really can't b intercoursed screwing the computer up again. Just reinstalled XP.
-
They figure eventually they'll accidentally make something stable.
Microsoft is really going down the tubes. If 7 is as bad as Vista, they're done in my eyes.
-
I actually don't know why anyone would want Vista. I'm not prepared to upgrade my whole friggen computer (motherboard, harddiscs, and CPU just to get more RAM into my computer. I calculated it at one point, $1500 AUD + Vista.
Holy excrement its got Vista crap in it.
-
There are allot of die hard Vista fans out there. I don't know why, but there are. And from what I hear, the version with the less bugs is Ultimate (figures the most expensive).
-
When I'm ready to install Vista, I'll be running server 2008 instead.
http://www.win2008workstation.com/wordpress/
http://blogs.msdn.com/vijaysk/archive/2008/02/11/using-windows-server-2008-as-a-super-desktop-os.aspx
-
There are allot of die hard Vista fans out there. I don't know why, but there are. And from what I hear, the version with the less bugs is Ultimate (figures the most expensive).
Rofl. Ultimate costs 2 much for what its worth.
-
There are allot of die hard Vista fans out there. I don't know why, but there are. And from what I hear, the version with the less bugs is Ultimate (figures the most expensive).
Maybe another reason is cause theres some games that on vistas instead of XP's, Like Halo 2 :o
-
Halo 2 is one of the worst PC ports I've ever seen. Ever.
ShadowRun is one of the best FPSs I've played-- but has no userbase because of the darn Vista-only thing. I really hope that's undone or patched out in the future. :(
-
So here is my tale of how I went about setting up Windows Server 2008 to look and fell like its desktop counterpart Windows Vista.
How Freudian...
-
http://msinfluentials.com/blogs/jesper/archive/2008/05/08/does-your-amd-based-computer-boot-after-installing-xp-sp3.aspx
This is a blog maintained by a M$ insider that has a lot more information regarding the SP3 issues.
If you are having problems, this is a must-read.
-
Microsoft blames computer makers for some of the problems users have encountered after updating to Windows XP Service Pack 3 (SP3), according to a company support document.
The document also showed that the "endless reboot" problem some users have reported after installing XP SP3 was neither unanticipated or new; Microsoft updated the document the same day it released the service pack, and indicated that the same thing happened nearly four years ago when it rolled out Windows XP SP2.
Knowledge Base document 888372, last updated May 6, spelled out an error message that stops a PC's boot process -- and, depending on the machine's settings, may make it repeatedly reboot -- after installing SP3. The fault, said the Microsoft document, is in the Windows XP image originally installed on the PC by the computer manufacturer, or OEM.
"The problem may occur if the original Windows XP Service Pack 1 (SP1) Sysprep image is created on an Intel-processor-based computer and if the Sysprep image is then deployed on a non-Intel-processor-based computer," said Microsoft.
"Under this configuration, after the computer is upgraded to Windows XP SP2 or SP3, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image," the document continued. "This issue may also occur if the original Windows XP SP2 or Windows XP SP3 Sysprep image is created on an Intel-processor-based computer and if it is then deployed onto a non-Intel-processor-based computer. Again, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image."
A day after Microsoft added XP SP3 to Windows Update, users began reporting that their machines processors from Advanced Micro Devices (AMD) were rebooting endlessly. Many of them said that the crippled systems were from Hewlett-Packard.
"I too have an HP Pavilion with an AMD Athelon [sic] processor," said a user identified as "jrednasnh" in a message posted Saturday to a Microsoft support forum. "I find it discouraging that HP may be partially at fault and did not attempt to notify us AMD customers, nor attempt to fix the issue."
Jesper Johansson, a former program manager for security policy at Microsoft and currently an MVP (Microsoft Most Valuable Professional), worked with others to identify some of the reboot issues as involving PCs running AMD CPUs. Johansson, who said one of his HP PCs repeatedly rebooted after installing XP SP3, traded accounts with several other users on the newsgroup and summarized the results on his blog.
"The problem is that HP, and possibly other OEMs, deploy the same image to Intel-based desktops that they do to AMD-based desktops," Johansson said. "Microsoft points out in a Knowledge Base article that installing both drivers on the same computer is an unsupported configuration, putting the blame on the OEM that deploys the image. The article in question was written when the same problem occurred after installing Service Pack 2 for Windows XP." Microsoft unveiled XP SP2 in August 2004.
According to Johansson, only HP desktop models are affected. "It also appears that this is unique to their desktop image, and any HP AMD-based laptops are unaffected by the problem," he said.
As Johansson mentioned, Microsoft has dubbed the practice "unsupported" in KB888372. "We do not support using Sysprep to install an operating system from an image if the image was created by using a computer that has a different processor," said Microsoft. "For example, you cannot create a Sysprep image on a computer that has an Intel processor and deploy the image to a computer that has an AMD processor."
KB888372 instructed users how to modify the Windows registry to disable the errant Intel driver, assuming users could regain control of their PCs long enough to boot into Safe mode.
The company has also listed several other scenarios that OEMs should avoid in another support document.
Microsoft and Hewlett-Packard did not immediately respond to questions Sunday.
-
They added it to Windows Update? I think I should check what I do from now on. I warned my friend yesterday, he went and installed it and he called me up and it was a reboot loop. He will probably kick me 2day cos i just kept laughing on the phone :P
-
See?
My post was useful!
I also denied it for now on my WSUS server
-
I was kicked :P. Also my computer hasn't got SP3 yet so it must not be in Windows Update for Australia yet (is there one?). My cousin called me in the middle of class and asked wtf SP3 did to his computer :P. I hate being teh only knowledge of computers in the family.
-
So I have automatic updates set up on one computer to download, but not install unless I say so. I went to shut it down (don't keep that one running all the time), and it brought up the little thing saying I have new updates and to "click here to shut down without installing these updates" or whatever. How do I actually tell what updates it wants to install? I want to make sure SP3 didn't sneak in there.
-
Click on teh windows update icon in your system tray and it should come up with a list.
-
Click on teh windows update icon in your system tray and it should come up with a list.
There wasn't one. That's the weird thing. Maybe it will magically reappear later.
-
That is interesting.....
-
Heh, this topic id is "13337".
-
that's nota good sign.
Get y00tz to provide some sort of ex0rcism.....
-
Try to start it through the start menu. Start > Programs > Windows Update
-
Also, check the windows update service in admin tools > services.
-
Post removed
-
Try to start it through the start menu. Start > Programs > Windows Update
Huh? Nope. I actually now want to stop it from installing because my Dad shut it down and it installed SP3. It intercoursed up. So I had to go to a backup image, again. Wouldn't they take it out with all of the bloody problems with it?
-
I set it up to ask before downloading or installing, and the next time I booted, it had the little yellow shield thing so I could check what it wanted to install. It wasn't SP3, so I let it do its thing.
-
Huh? Nope. I actually now want to stop it from installing because my Dad shut it down and it installed SP3. It intercoursed up. So I had to go to a backup image, again. Wouldn't they take it out with all of the bloody problems with it?
If you run that, you can uncheck things you don't want to install (basically).
-
If you run that, you can uncheck things you don't want to install (basically).
But will it stay like that or will it check itself when teh computer is rebooted. Because half the time my dad shuts the computer down because I like to torrent when I go to bed and he turns it off by hitting the shutdown button and i've seen heaps of updates sitting there recently.
-
Looks like we have a fix!!
http://redmondmag.com/news/article.asp?editorialsid=9865
Ex-Microsoft Employee Takes Lead on XP SP3 Reboot Problem, Offers Free Fix
May 15, 2008 • by Becky Nagel
A former Microsoft employee appears to be coming to the rescue of those suffering from the XP SP3 endless reboot cycle that can happen on computers with AMD processors -- a problem for which Microsoft has yet to announce a solution.
As first noted by Computerworld, on Wednesday author and Microsoft MVP Jesper Johansson -- who until 2006 was a senior security strategist at Microsoft -- released a home-spun tool that automatically checks for a configuration error that may be the cause of the reboot problem.
"If you have an AMD-based computer, and all you want to do is prevent the problem before installing Service Pack 3, then try the new tool I just wrote," he stated in this blog post yesterday. "It will first check whether you have an AMD-based computer. If you do it will check whether the IntelPPM driver is set to load. If it is it will offer you an option to disable it." Johansson also offers instructions for using the tool on multiple computers simultaneously.
Johansson started blogging about the endless reboot issue last week when he encountered it, and has been sharing his troubleshooting process on his blog since then. In the absence of extended technical information on the issue from Microsoft, his extremely detailed post is quickly becoming the definitive technical source for both IT professionals and end users looking for a possible work-around.
Johansson states that the reboot issue appears to be happening on both Intel-based and AMD-based machines and can be caused by a number of factors. While the errors that start the reboot process appear to relate to XP SP3, the effect -- endless reboots -- ties back to how Windows XP itself was designed to react to crashes.
"With some configurations, SP3 causes the computer to crash during boot, and Windows XP, by default, is set up to automatically reboot when it crashes," he explained in his post. "That is why you end up in the endless rebooting scenario."
Johansson hypothesized -- and Microsoft has since echoed -- that many of the errors are being caused by OEMs installing the wrong operating system image on certain desktops.
"The problem is that HP, and possibly other OEMs, deploy the same image to Intel-based desktops that they do to AMD-based desktops," he wrote. "The image for both Intel and AMD is the same all have the intelppm.sys driver installed and running...Ordinarily, having intelppm.sys running on an AMD-based computer appears to cause no problems. However, on the first reboot after a service pack installation, it causes a big problem. The computer either fails to boot, as in my case, or crashes with a STOP error code of 0x0000007e. If you see that error code you almost certainly have this problem."
HP is blaming the upgrade itself, saying that even if an OEM doesn't install intelppm.sys, XP SP3 does.
In his post, Johansson details how to manually disable the intelppm.sys driver on AMD PCs; the tool released Wednesday automates this process. The posts also offers other solutions if the tool doesn't work, and refers readers both to Microsoft's article on uninstalling XP SP3 and Microsoft technical support (currently free for XP SP3).
***
See the article at the link at the top for all of the url's to the fixes.
***
-
Thanks a ton KnacK :)
-
Anything for my fellow brethren.
-
After I used the work around you linked and upgraded my HP with an AMD, I finally got an email from HP support with a link to the fix they're providing now: http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=pv-60484-1&lc=en&cc=us&dlc=en&product=1843651&os=228&lang=en
-
i think microsoft is trying to destroy the world be realeasing poor products. the 360 wasnt so bad but it has its share of major flaws. RROD!
-
i think microsoft is trying to destroy the world be realeasing poor products. the 360 wasnt so bad but it has its share of major flaws. RROD!
You obviously have not read all of the articles that I have posted......
-
nope. not at all
-
not supposed to admit it haha.
-
Well, at least he's honest. :P
-
and its honesty that counts (^_^)
-
Still More Issues:
http://blogs.techrepublic.com.com/window-on-windows/?p=698&tag=nl.e019
Another problem with Windows XP Service Pack 3 has reared its ugly head, this time causing headaches for users of Symantec products. Unfotunately, it appears that other users are being affected as well and that the problem appears eerily similar to an issue that Microsoft had with Service Pack 2. The two processes to watch for processor hogging on are fixccs.exe and cscript.exe. The problem can cause Device Manager to appear blank and can also produce thousands of errant registry entries.
Symantec blames Microsoft for XP SP3 registry corruption (Infoworld)
The service pack also appears to have caused issues with Windows Home Server’s remote access feature. Thankfully, there are some people diligently looking out for XP users, even though it appears that Microsoft is being a bit slow to correct the latest problems. All of this is in addition to the initial reports of endless reboot loops on some AMD based machines, an issue that HP blamed on Microsoft.
Users Report More Trouble With Windows XP SP3 (PC World)
Windows XP SP3’s Aches, Pains, and User Complaints (PC World)
Windows XP Service Pack 3 still rocky, reboot loop (Slipperybrick)
I blogged the day after XPSP3 released that I had installed it without error and since then, everything seems to have gone well for the Dell Inspiron laptops that got the install. I was able to image them with LanDesk and get them deployed, where they have been successfully used for their end purpose. Still, it seems like Microsoft should have the resources to get these bugs tested out by the time they call their patches “final.” Have you had issues with SP3?
-
Well my boss brought me his personal pc this morning. It was hanging at mup.sys in safe mode then doing the endless reboot dance.
Sure enough, he isntalled SP3 last night.
I'm in the process of removing it through the recovery console.
-
Eww.
Oh, my computer just started doing that the other day (freezing at mup.sys) after I told it to run chkdsk on reboot. Do you think it could be related to SP3?
(I've made some progress, btw. But I still cant boot windows normally)
-
I had to boot to an install disk, run the recovery console, then remove sp3 via the console.
http://support.microsoft.com/kb/950249
Good step by step.
SOme people claim thatthe mu.sys hang could be caused by hardware error.
Do this:
Reboot your pc, as soon as it hangs at mu.sys, pull all of your usb devices from the pc and see if it continues. Some guys say that works, then they reboot again and all is fine.
-
All I have plugged in is the power and ethernet. I've had SP3 installed sense shortly after it was released, and this is just happening now.
-
So this excrement still isn't fixed yet? I keep getting Windows Update asking and asking to install it. Sadly any update I do requires SP3 so I'm not exactly happy. Don't know why.
-
All I have plugged in is the power and ethernet. I've had SP3 installed sense shortly after it was released, and this is just happening now.
If you try to start in safe mode, does it stop at mu.sys?
So this excrement still isn't fixed yet? I keep getting Windows Update asking and asking to install it. Sadly any update I do requires SP3 so I'm not exactly happy. Don't know why.
Do you have an Intel or AMD pc, is it home brew, and where did you get your version of XP from?
Also, if installing SP3 does bomb. removing it is straight forward using the directions above.
-
It was freezing at mup.sys, until I booted off my XP CD and ran a chkdsk (what i had told it to do in the first place), then I could boot into safe mode. I uninstalled SP3, and it booted up ok. Some errors, mainly visual, but it worked. Tried to reinstall it (my virus scan software requires SP3), and it runs out of disk space while downloading (via windows update). I try to restart and it wouldn't start up normally. Booted up into safe mode, and started a "Disk Cleanup".
-
Intel Pentium 4, uhh, XP was an upgrade from 2000, but fresh installed. And the computer came from some store, except for the graphics card.
-
You *should* be fine cameron. If not, its easy to back out of.
-
Don't let XP Service Pack 3 hose your system
By Scott Dunn
From the moment Microsoft released it, Service Pack 3 for Windows XP has been the subject of almost daily reports of bugs, incompatibilities, and general headaches.
You can install SP3 with confidence — providing you take certain precautions — or, if you prefer, use Windows' Automatic Update settings to keep the service pack off your system.
Multiple problems plague SP3 adopters
Windows Secrets has been reporting problems with Windows XP's Service Pack 3 almost from the instant the patch collection was first distributed. In fact, so many readers have contacted us with questions or complaints about SP3 — the last major update to Windows XP — that we've synthesized everything you need to know about this update in a single column.
Here are the most glaring SP3-related problems:
• Internet connectivity fails when using black hole routers, which drop packets (see Susan Bradley's May 1 column in our paid content and Microsoft's Knowledge Base article 314825).
• False positives are generated by Norton Internet Security and other security applications (see my May 2 Top Story).
• Device Manager settings go missing, especially in connection with using Norton Antivirus (see Susan Bradley's column in the May 29 newsletter as well as KB 953791).
• Repeated rebooting occurs on machines using an AMD processor (see Susan Bradley's May 22 column and KB 953356).
• You can't install any new updates (see KB 943144).
• Third-party visual styles encounter problems (see the Support Alert Newsletter of June 19).
Making an upgrade decision that works for you
In light of these and other problems, you may wonder whether you ever want SP3 at all, especially given that many of its enhancements focus on networking and IT-level administration. Here's the case for SP3:
Think security: In addition to new features, SP3 — like most service packs — includes numerous security updates that were available individually in the past.
Consider support: If you think you might require Microsoft's assistance to install SP3, you need to add the service pack before April 2009, when the company will end such support. And because overall support for SP2 expires in early 2010, you'll need to have SP3 installed by that date if you want general support for XP.
Be prepared: Before you install SP3, take a few precautions. First and foremost, perform a full system backup. Microsoft has digested all recommended pre-install steps in KB 950717, which also includes troubleshooting information if all does not go well.
How to remove SP3 from your Automatic Updates
If you decide you don't want SP3, Microsoft offers a tool for suppressing the automatic installation of the service pack. The Service Pack Blocker Tool Kit won't prevent you from downloading SP3 manually from the company's site, nor will it stop you from installing the patches from a CD or DVD. All it does is stop the service pack from being installed via Windows' Automatic Updates.
In addition, the Service Pack Blocker postpones the installation for only a year from SP3's release date last April.
Surf over to Microsoft's Service Pack Blocker download page and click the Download button for SPBlockerTools.exe. Click Yes to accept the license agreement and type in the path to the folder where the files will be stored (click the Browse button and navigate to the folder if you want to avoid typing).
Now open the folder containing the extracted files and double-click SPBlockingTool.exe. A command prompt window appears for a few moments and displays the statement "Action successfully completed." Unfortunately, that doesn't tell you very much. The action the message refers to is the addition of a Registry entry instructing Windows Update not to send you SP3. (The same setting on Vista blocks SP1.)
If you want to see the code that is added, do the following:
Step 1. Choose Start, Run. Type regedit and press Enter.
Step 2. In the Registry Editor, navigate in the left pane to this entry:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Policies \ Microsoft \ Windows \ WindowsUpdate
Step 3. With the WindowsUpdate icon selected in the left pane, look in the right pane for a key named DoNotAllowSP.
If you later decide you want Automatic Updates to offer you Service Pack 3, simply select the DoNotAllowSP key and press Delete (or click Edit, Delete).
If you're concerned about editing the Registry (which involves risks of its own), the Service Pack Blocker can also undo the block:
Step 1. Choose Start, Run. Type cmd and press Enter.
Step 2. At the command prompt, either type the path to the SPBlockingTool.exe file, or drag the file into the command prompt window and let Windows do the typing for you.
Step 3. At the end of this command, type a space followed by /U and press Enter.
Once again, you'll see the "Action successfully completed" message and Windows Automatic Update will no longer be blocked from installing the service pack on your system.
The other tool included with the download, SPreg.cmd, is a batch file useful for administrators who want to block the service pack on remote computers; this utility requires that the machine name be specified in the command line.
Even though most of SP3's problems should now be in the past, these precautions can help ensure that you aren't one of the service pack's installation victims.
-
I honestly think that sp3 was released screwed up intentionally to try to make people go ahead and do the Vista switch. They don't feel the need to keep working on it. They would rather people spend the money to switch to the greatest and latest. boo.
-
weird. i haven't had even the slightest hiccup from sp3. not on any pc i've installed it on.
-
I have the little yellow sheild icon sitting on my taskbar, and its the SP3 update, how can I make the icon go away and reject the update for good?
-
You can't. SP3 is largely harmless, it's just that there was a big deal made about it's incompatibility with certain processors or whatever it was. :P
-
So is it ok to go through with?
-
Sadly any update I do requires SP3 so I'm not exactly happy.
actually i think if you go to http://update.microsoft.com/ and let it check for updates, then you can tell it to disregard sp3 and look for any other available updates. i could be wrong tho.
So is it ok to go through with?
i would, and then if you have problems, try one of the solutions posted here.
-
lol, so basically if it effs up I just set fire to my tower....
-
yep, that's the idea. i've never seen that solution fail. ;D
-
yep, that's the idea. i've never seen that solution fail. ;D
I have. I had a xps laptop from dell with vista on it. After weeks of it annoying me I took it out to the garage, hit it about a hundred times with a hatchet, threw it in a hole in the back yard, poured a half of a can f gas on it and lit it. The darned thing was sitting on my kitchen table the next morning like something from Stephen King's pet cemetery.
-
lolwut... thats hilarious.
-
lol
-
Ok so I just installed SP3 and I'm just waiting for something to go wrong, when I restartedit, it wouldn't boot up so I had to reboot, and now I'm paranoid. If you dont see me for awhile you'll know why.