Feeds

MS kernel patch skirts infected machines

Damage control bypasses pwned PCs

Secure remote control for conventional and virtual desktops

Microsoft's latest batch of patches contains a kernel update designed not to install on machines infected with a rootkit.

The move is designed to prevent the confusion that occurred when one of the patches released in February resulted in a Blue Screen of Death and continuous reboot cycles on some Windows XP machines.

Microsoft copped a fair bit of criticism for the incident before the cause was pinned down to the interaction between the hard-to-detect Tdss rootkit and a Windows kernel security update. Rootkits are a type of malware that attempt to avoid detection by anti-virus scanners by burying themselves in the likes of Windows kernel code.

Redmond's April patch batch also contains a Windows kernel patch. In an effort to prevent the same snafu as February, Microsoft is using technology designed to prevent the update from installing onto malware-compromised machines.

"This security update includes package-detection logic that prevents the installation of the security update if certain abnormal conditions exist" Microsoft explains in the FAQ for its MS10-21 patch.

"These abnormal conditions on a system could be the result of an infection with a computer virus that modifies some operating system files, which renders the infected computer incompatible with the kernel update."

The same technology was used in a modified version of the MS10-15 update, which was initially released as part of February's Patch Tuesday and revised with an "avoid infected systems" add-on in mid-March.

Users who attempt to install either the revised MS010-15 package or the new Ms10-021 kernel update on infected machines ought to get an error code.

Possible error codes (such as 0x8007F0F4) fail to explain what might have gone wrong, but a bit of judicious searching ought to direct sys admins or regular users who hit the snag to this advisory here. This notice explains that users who run across problems installing the patch are probably dealing with a malware-infected machine.

Microsoft's April patch batch included 11 bulletins along with an update to the software giant's Malicious Software Removal Tool. The idea is that this tool will remove malware and clean up systems which can then by safely patched at the second time of asking. ®

Secure remote control for conventional and virtual desktops

More from The Register

next story
'Regin': The 'New Stuxnet' spook-grade SOFTWARE WEAPON described
'A degree of technical competence rarely seen'
You really need to do some tech support for Aunty Agnes
Free anti-virus software, expires, stops updating and p0wns the world
You stupid BRICK! PCs running Avast AV can't handle Windows fixes
Fix issued, fingers pointed, forums in flames
Regin: The super-spyware the security industry has been silent about
NSA fingered as likely source of complex malware family
Privacy bods offer GOV SPY VICTIMS a FREE SPYWARE SNIFFER
Looks for gov malware that evades most antivirus
Patch NOW! Microsoft slings emergency bug fix at Windows admins
Vulnerability promotes lusers to domain overlords ... oops
HACKERS can DELETE SURVEILLANCE DVRS remotely – report
Hikvision devices wide open to hacking, claim securobods
prev story

Whitepapers

Why and how to choose the right cloud vendor
The benefits of cloud-based storage in your processes. Eliminate onsite, disk-based backup and archiving in favor of cloud-based data protection.
Getting started with customer-focused identity management
Learn why identity is a fundamental requirement to digital growth, and how without it there is no way to identify and engage customers in a meaningful way.
10 threats to successful enterprise endpoint backup
10 threats to a successful backup including issues with BYOD, slow backups and ineffective security.
High Performance for All
While HPC is not new, it has traditionally been seen as a specialist area – is it now geared up to meet more mainstream requirements?
The hidden costs of self-signed SSL certificates
Exploring the true TCO for self-signed SSL certificates, including a side-by-side comparison of a self-signed architecture versus working with a third-party SSL vendor.