MS on WinXP: We fix one leakage, only to break other pipe causing further problem

G

Gaurish

Level F
MS on WinXP: We patch, only to break other pipes leading to BSODs

Microsoft patched vulnerability but later discovered they caused another *bigger* problem with their patch -- BSODs(thus, risking user data) :P then hurriedly, withdraw; previously issued patch. leaving original issue unfixed & End users clueless. Now its going more messy, even Microsoft engineers scratching their heads. nobody knows, what the hell is happening :rofl::rofl:

Way to Go, Microsoft! :@

If you ever needed a reason to go Linux, here you go. The noise surrounding this patently obscure Windows XP bug / patch fiasco has just reached a fever pitch, and now we've got engineers within Redmond scratching their heads, too. As the story goes, Microsoft recently patched a security hole that took care of an antediluvian DOS vulnerability, and in doing so, some users began to see BSODs and endless reboots. Today, we've learned that the patch has been yanked, and Microsoft is suggesting that malware is to blame. But here's the skinny -- the patch simply disturbed the malware, which called a specific kernel code that directs your PC to keel over; in other words, any application that calls that same code could theoretically leave your machine in dire straits.
Click to expand...

Windows XP patch fiasco gets even crazier, Microsoft now scrambling for solutions -- Engadget
 
Back
Top