14 DAY TRIAL // This month, Microsoft and the Windows user community are celebrating the 10th anniversary of Patch Tuesday, an updating cycle started in 2003 and supposed to provide consumers across the world with fixes aimed at the most recently found vulnerabilities in a number of products such as Windows and IE.
As we wrote in our cover story on this important milestone in Patch Tuesday’s cycle, Microsoft was often forced to deal with botched updates that caused quite a lot of problems to Windows users, with some people even asking CEO Steve Ballmer to step in and revamp quality control within the company.
Now, it would be naturally to expect Microsoft to treat with extra care the month marking the 10th anniversary of Patch Tuesday. It would be not only common sense, but also probably the only thing you need to do in order to make sure that Patch Tuesday updates do not break down any other computers.
Redmond, on the other hand, has failed to do so, and some of the updates delivered on October 8 are still causing BSODs to a number of Windows 7 computers around the world.
The interesting fact is that nobody says a word about this. A topic posted on Microsoft’s Community forums now counts 9 nine pages, while some of our reports on the error have tens of comments from users confirming that the KB2862330 Windows 7 update is breaking down their PCs.
Microsoft hasn’t launched any public statements on what seems to be another botched updates, saying that some users might be asked to reboot their computers twice after deploying the KB2862330 fix.
Guess what? It’s a lot worse. Lots of users are getting BSODs, while some claim that the update fails to install every single time. While it’s easy to imagine how this is becoming frustrating, it’s also impossible to understand how come that Microsoft hasn’t said anything for almost a week even though more users are confirming the issue.
Keep in mind that no workaround is available for the time being and the only statements posted on the Microsoft Community forums is that the company is now investigating the issue. Of course, lots of users are outraged with this lack of reaction from Redmond and it’s easy to see why.
It’s pretty obvious that whoever takes over from Ballmer has many, many problems to tackle on the short term.