Microsoft to reissue faulty “critical” patch


Microsoft to reissue faulty “critical” patch

Tash Shifrin

Microsoft is to issue a new version of a critical security patch for Windows Explorer, after admitting that the original fix could crash Office applications or prevent access to files and folders.

The MS06-015 security patch released last week caused problems for users of Hewlett-Packard scanners, cameras, Deskjet printers with card readers and HP’s Share-to-Web and Photosmart software.

Affected users found that Office applications crashed or were unable to access or save Office files in special folders, including the "My Documents" folder. Users of Sunbelt Kerio Personal Firewall also experienced problems with Windows.

Microsoft’s security programme manager, Stephen Toulouse, has now confirmed that the software giant had “re-engineered” the MS06-015 update to avoid the software conflict.

In a message on the Microsoft security response centre blog, he said the new patch would be released on Tuesday 25 April. “What the new update essentially does is simply add the affected third party software to an ‘exception list’ so that the problem does not occur.”

Microsoft is also investigating problems in Outlook Express caused by a separate security patch, also issued last week. Security update MS06-016 was released to patch a vulnerability that could allow hackers to take control of users’ computers.

But problems with Outlook functions were reported in postings on Microsoft’s help and support messageboards, including address books disappearing, disabled “send” functions and template problems.


Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting your personal information, you agree to receive emails regarding relevant products and special offers from TechTarget and its partners. You also agree that your personal information may be transferred and processed in the United States, and that you have read and agree to the Terms of Use and the Privacy Policy.

COMMENTS powered by Disqus  //  Commenting policy