bit-tech.net

Microsoft withdraws Windows patch over crashing bug

Microsoft withdraws Windows patch over crashing bug

The patch for a security flaw in the Windows kernel has been found to crash Windows 7 systems, and has been withdrawn from Windows Update until a fix can be found.

Microsoft has withdrawn one of the security updates it released on Tuesday, following reports of crashes on Windows 7 systems.

Patch MS13-036/2823324, a fix for a critical-rated security flaw in the Windows file system kernel-mode driver ntfs.sys, was part of a bundle of software updates released by Microsoft earlier this week as part of its regular 'Patch Tuesday' scheduled update cycle. Unfortunately, it seems the cure is worse than the disease: while the hole it patches may or may not ever be exploited on your system, the chances are good installing the patch will crash your computer hard.

With the patch installed, affected systems - thus far seemingly limited to Windows 7 machines - will crash on reboot, with some reports claiming that the system will see the hard drives as uncleanly mounted and run CheckDisk on every boot. While this is not thought to put any data at risk, it's certainly annoying - and doubly so when the crashes continue to mount, causing delays as you wait for yet another disk check to complete.

Microsoft has confirmed that there is something seriously awry with the update, posting a knowledge base entry claiming it is investigating the issue. 'Systems may not recover from a restart, or applications cannot load, after security update 2823324 is applied,' the company admitted in the posting. 'We recommend that customers uninstall this update.'

To prevent any further mishaps, Microsoft has removed the patch from Windows Update until a fixed version can be released - but with most users installing updates as soon as they are released by the company, the damage is likely already done. For those who do uninstall the patch, or who never installed it in the first place, the race is now on for Microsoft to release a fixed version before ne'er-do-wells take advantage of the opportunity to attack systems through the vulnerability.

This most recent Patch Tuesday is doubly embarrassing for the software giant: as well as releasing a broken patch, it also failed to fix a major security hole highlighted at the Pwn2Own event earlier this year, leaving its customers vulnerable to attack.

18 Comments

Discuss in the forums Reply
erratum1 12th April 2013, 10:09 Quote
Oh I have that installed haven't noticed anything stange happening if they recommend uninstalling it i'll get rid.
Corky42 12th April 2013, 10:20 Quote
Yea same, not had any problems.
Would last known good role back the update if you got hit by this ?
Griffter 12th April 2013, 10:23 Quote
Ironically those ppl who get the restart crash bug will never see this post and most likely reinstall and some maybe just dump all data for a fresh install on their single HDD just to download the update again lol

shame...

M$ tsk tsk tsk
lp rob1 12th April 2013, 10:23 Quote
I think I have experienced this bug. Shutting down works fine, but pressing restart causes the system to hang just before starting up again, requiring a hard reset.
k4p84 12th April 2013, 10:24 Quote
add and remove programs / view installed updates (top left) / uninstall the update. if you can't boot see if you can get in via safe mode
erratum1 12th April 2013, 10:30 Quote
Quote:
Originally Posted by k4p84
add and remove programs / view installed updates (top left) / uninstall the update. if you can't boot see if you can get in via safe mode

Thanks wasn't quite sure how to remove an important update.
Bob Andersson 12th April 2013, 12:49 Quote
Hmm, uninstalled the update, although I hadn't seen any errant behaviour, and rebooted, Checked for updates and 2823324 was offered (file date April 9th) so I installed it without issue. So what gives? Has Microsoft already fixed the problem?
Griffter 12th April 2013, 14:08 Quote
Shaun Sparg
Gareth Halfacree 12th April 2013, 14:27 Quote
Quote:
Originally Posted by Bob Andersson
Hmm, uninstalled the update, although I hadn't seen any errant behaviour, and rebooted, Checked for updates and 2823324 was offered (file date April 9th) so I installed it without issue. So what gives? Has Microsoft already fixed the problem?
Not so far as I'm aware: the knowledge base entry still lists it as having been removed pending investigation. That said, I don't have a Windows box I can check on. It's possible that Windows Update has cached the update - did it seem to take little to no time to download the second time you installed it?
Tyinsar 12th April 2013, 15:20 Quote
It's already been installed on several machines both at home and at work. No issues so far. I see no point in removing the patch from those machines.

I suspect such issues are relatively rare otherwise they wouldn't get through Microsoft's testing. The possible variations in hardware and software in Windows PCs has got to be some mind-numbingly massive number.
Corky42 12th April 2013, 16:02 Quote
From what i have read it seems this maybe caused by Kaspersky.
LordPyrinc 12th April 2013, 16:06 Quote
Thanks for the info Bit-Tech! That faulty patch would've loaded on my next reboot. I've removed it from the list for now.
Tyinsar 12th April 2013, 16:11 Quote
Quote:
Originally Posted by Corky42
From what i have read it seems this maybe caused by Kaspersky.
Good to know. ;) (rep added)
This is part of why my machines don't all run the same anti-virus.
Woodspoon 12th April 2013, 17:55 Quote
Can't even get the update on if I wanted to.
kb2808735, kb2813170, kb2823324, kb2799926
updates keep failing getting error code: 800736B3
Only on those 4, uninstalled all of the previous months updates that went back on fine, just the most recent 4 didn't.
Anyone else had this?
Corky42 12th April 2013, 18:10 Quote
Quote:
Originally Posted by Woodspoon
updates keep failing getting error code: 800736B3
Anyone else had this?

No, but have you tried resetting windows update or re-running the System Update Readiness Tool
Woodspoon 12th April 2013, 18:25 Quote
Quote:
Originally Posted by Corky42
Quote:
Originally Posted by Woodspoon
updates keep failing getting error code: 800736B3
Anyone else had this?

No, but have you tried resetting windows update or re-running the System Update Readiness Tool
Yes, tried both the MS fixit thing and the System Update Readiness Tool, the fixit tool says it fixes something until I restart and it fixes the same thing again :s
Don't really fancy poking around in my registry to do it manually either.
cnyrsitizin 12th April 2013, 20:59 Quote
Hmm. Running both Kaspersky IS2013 and the patch (file date 10/4) on Windows 7 64 bit no problems at all.
RichCreedy 12th April 2013, 23:01 Quote
disable automatic updates, then re-enable via windows update cpl
Log in

You are not logged in, please login with your forum account below. If you don't already have an account please register to start contributing.



Discuss in the forums