- Bank Web sites full of security holes
- SCO Group: Its future is all used up
- Maligned feature being added to IPv6
- I returned my iPhone 3G after six days!
- VPNs: Six burning questions
News | Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:App Performance | On Demand Security | Networking Solution | SOA | Value of WDS
A former Microsoft security manager has published a tool designed to detect and fix PCs that may be susceptible to "endless reboots" if updated to Windows XP Service Pack 3 (SP3).
Jesper Johansson, once a program manager for security policy at Microsoft and currently an MVP (Microsoft Most Valuable Professional) who works at Amazon.com, posted a link to the tool on his blog Wednesday, beating his former employer and Hewlett-Packard Co. to the draw. Neither company has yet come up with a fix or patch for the week-long snafu.
Johansson's small, 16K VBScript (Visual Basic Scripting Edition) file checks whether the PC is running a processor from Advanced Micro Devices (AMD), and if so, examines the Windows registry to see if a device driver meant for Intel-based machines is set to load.
"If it is, it will offer you an option to disable it," said Johansson in an update to a blog post where he has been summarizing reports of Windows XP SP3 problems and offering solutions.
Users can run the script from the command line to check multiple machines on a network, Johansson added. The command is:
removeIntelPPMonAMD.vbs ...
"The only caveat is that the tool will prompt you several times for each computer," Johansson added.
The free-of-charge VBScript file is available for download.
The tool is the latest in the week-long problem some users have encountered after upgrading Windows XP to the new service pack. Last week, just a day after Microsoft added XP SP3 to Windows Update, reports accumulated of "endless reboots" crippling machines running AMD CPUs. Many of the users said that the out-of-control PCs were from HP.
According to users, Johansson and most recently, Microsoft itself, the problem can be traced to the disk image that HP used to factory-install Windows XP on AMD-based machines. HP, said everyone concerned, used an image created on an Intel-powered PC to install XP on AMD systems; Microsoft had advised computer makers against doing that as long ago as 2004.
Microsoft was not immediately available for comment on Johansson's detection tool, but traditionally the company has taken a dim view of unsanctioned, unofficial fixes to its software.
Rss FeedRss Feed
14 years ago, I dealt with somebody like Childs. I was the new manager and the veteran techie knew it...- Anonymous
| NetworkWorld, Inc. | About Network World, Inc. | Advertise | Careers | Contact us | Terms of Service/Privacy | Reprints and links | Partnerships | Press room | Subscribe to NW |
| IDG, Inc. | CIO | Computerworld | CSO | Demo | GamePro | Games.net | IDGconnect.com | IDG World Expo | Infoworld | JavaWorld.com | LinuxWorld.com | MacUser | Macworld | PC World | Playlistmag.com | The Industry Standard | IDG List Services | IDG TechNetwork |
 |
Copyright © 1994-2008 Network World, Inc. All rights reserved. |
Partner Content
Brilliantly simple security and control solutions for email, web and endpoint
www.sophos.com
Stopping data leakage
Learn how to exploit your current security investment to control the information that flows into, through and out of your network.
Download the white paper.
Why detection rates aren't enough
Evaluating endpoint security products is a time-consuming and daunting task. Learn the six critical questions you need to ask to prospective vendors to get the right endpoint solution.
Download the white paper.
Unauthorized applications: Taking back control
Employees installing and using unauthorized applications like IM, VoIP, games and peer-to-peer file-sharing applications cause many businesses serious concern. How do you control these applications?
Download the white paper.
Comments (16)
Microsoft is at fault since they should have tested it on AMD maBy Anonymous on June 28, 2008, 12:40 amIs anyone so foolish to think that MS gives an ounce of care? Thier history is a long string of blunders that repeatedly cost the end-users precious time and money....
Reply | Read entire comment
Intel Pentium III also reboots endlessly after SP3 updateBy Anonymous on June 11, 2008, 7:19 pmI have an Intel Pentium III and after teh SP3 Windows update my computer went into emdless reboots. Microsoft never told me that other customers had similar problems....
Reply | Read entire comment
your're an idiotBy Anonymous on May 21, 2008, 12:05 amIf m$ stes, use AND image for AMD PC's and HP goes and use an Intel image, thus causing the glitch. How is M$ responcible exactly? I hate M$ but HP is at fault...
Reply | Read entire comment
Microsoft's fault??? HP should have followed directions.By james_c on May 20, 2008, 12:25 pmFollowing specs to the letter would mean that HP built their AMD image on an AMD based PC, NOT on an Intel based PC. They didn't follow Microsoft's "specs", directions...
Reply | Read entire comment
It is the fault of HP, no question.By SystemBuilder_x on May 19, 2008, 9:41 amAs a product manager for a large OEM system builder, I am very familiar with the problem that HP caused. We have caused similar issues here and it's all due to...
Reply | Read entire comment
View all comments