Winbeta reports that complaints from users of the 32-bit version of Windows 7 began to arise after installing a security fix during April 2013 Patch Tuesday. This security patch, KB2823324, updated the Windows 7 file system kernel-mode driver. However for some, this resulted in an infinite reboot loop cycle, blocking users from fully loading into Windows 7. Fun stuff.
For now it seems that the issue is only affecting Windows 7 users in Brazil, but it's possible the update is plaguing other customers as well. To prevent further damage, Microsoft has halted the distribution of this specific patch while the company investigates the issue.
"Microsoft is investigating behavior where systems may not recover from a restart, or applications cannot load, after security update 2823324 is applied. We recommend that customers uninstall this update," the company stated. It's suggested that the problem stems from third-party software, but it's currently unknown which app is causing a conflict.
Given that Microsoft has pulled the security fix in question, it should no longer be necessary to turn off automatic updates. However if the security fix is installed and causing problems, then users are suggested follow one of three options if the PC has not been restarted: manually uninstall the security update via the Control Panel, to incorporate a command line uninstall in a custom script, or run removal script remotely by using PSEXEC.
If the PC has been restarted after the update and Windows 7 fails to load, users are suggested to hit the F8 key and recover the last restore point via System Restore or via the Command Prompt using one of two commands.
"Microsoft is researching this problem and will post more information in this article when the information becomes available," the company stated in security update KB2839011. "This includes issuing a new update that resolves the issues discussed in this article."
At least it wasn't a firmware update that totally bricked the hardware.
Stay on the Cutting Edge
Join the experts who read Tom's Hardware for the inside track on enthusiast PC tech news — and have for over 25 years. We'll send breaking news and in-depth reviews of CPUs, GPUs, AI, maker hardware and more straight to your inbox.
The cynic in me says that there will be more and more stories like this that seem to be Windows 7 specific in a move to sway people to move on to Windows 8. For me though, this is just another reason to let updates rest for a month or so before downloading and installing them.Reply
Very unprofessional Microsoft. I'll just add this to my continuing demerits list...Reply
Don't think it happened to my laptop...Reply
why toms use same account system between .com and .co.uk sites but don't have single comment system for articles?Reply
"Maybe if we break Windows 7, they'll decide to buy 8"
This update messed 2 computers in my office and 6 from my friends.Reply
All issues only happened on 32-bit OS with Win 7 brazilian portuguese language.
The computer shoppings in my city were flooded with costumers complaining...really messy stuff.
It´s rather easy to repair even without a restore point, but you need to know what to do.
This just tells me Microsoft patch engineers didn't know about the kernel level spyware they put in Brazilian versions of the OS so they could help Uncle Sam monitor the drug cartels / cocaine trade.Reply
Well actually, their are a few more problematic updates, If I install IE 10 Age of conan won't start anymore, all works well when I uninstall it...Reply
What do we do if the update was installed and not causing any problems?Reply
How come only the 32bit get affected but the not the 64bit? Are the patches written differently or something?Reply