Forbes Blasts Latests Windows 7 Patch as Malware
Forbes contributor Jason Evangelho has nothing good to say about a recent Windows 7 patch that's causing a range of trouble for some users. He writes:
If you have Windows 7 set to automatically update every Tuesday, it may be to permanently disable that feature. Microsoft has just confirmed that a recent update — specifically KB 3004394 — is causing a range of serious problems and recommends removing it.
The first issue that caught my attention, via AMD’s Robert Hallock, is that KB 3004394 blocks the installation or update of graphics drivers such as AMD’s new Catalyst Omega. Nvidia users are also reporting difficulty installing GeForce drivers, though I can’t confirm this personally as my machines are all Windows 8.1. Hallock recommended manually uninstalling the update, advice now echoed officially by Microsoft.
More troubles are detailed in the article; on the upside, Microsoft has released a fix.
Ah yes, one bad patch and we should all NEVER PATCH AGAIN BECAUSE THE SKY IS FALLING! Perhaps he will take personal responsibility the next time a patched vulnerability launches a new botnet? Nah, just write inflammatory rubbish, it's easier.
According to my update history they automatically uninstalled it the next day (via a new update). So the auto updates worked - no drama.
---- Den ene knappen er powerknapp, den andre er Bender voice knapp "Bite My Shiny Metal Ass"
I think calling something "Malware" implies malice, something that's not indicated here as I see it. This is probably a case of incompetence, releasing poorly thought out, poorly written, and/or poorly tested code. Maybe we need a term for that - "bugware". (Or, for the cynics in the audience, we already have a term - "software".)
It doesn't hurt to be nice.
Several readers have pointed out that disabling automatic Windows Updates is bad advice, and while thatâ(TM)s a fair argument I have to disagree.
It is really a BAD advice. The average PC user is not an ops person. If an update bricks his PC, he will notice and can get help. If his PC is insecure, he will notice nothing and help (if ever) will be asked for much too late.
His arguments amount to one thing: avoid changes. Any change is a risk. But so is crossing the street. In the long run, a change-averse strategy will lead to worse results than the occasional botched change (exceptions apply, but those are rare). And the only way for the average user to do changes is to automate them.
Ah yes, one bad patch and we should all NEVER PATCH AGAIN BECAUSE THE SKY IS FALLING!
Did he actually say that?
Or did he say turn off *automatic* patching?
It seems reasonable to always be 1 week behind in patching your systems - let someone else be the lightning rod for goofs and mistakes. I know some sysadmins patch "test" systems and try things out to see if the patches break their currently-running code. They don't seem to mind a certain time lag in patching.
While your steps work, you can also just focus on the desktop (by clicking the background, for example), then press ALT+F4. You will then be presented with the shutdown menu which includes the same options you cited, but without the need to log off first.
After the patch my box started complaining endlessly that it was not genuine windows, but when I went to activate Windows page it said I was already activated and just told me all of the great benefits of having genuine Windows and that I should install MS Defender.
It non-activated dialog box wanted me to install some application to double activate it or something? I've had a tough time figuring out exactly what's up with it. The links all point to genuine microsoft.com websites, so it doesn't appear to be malware, but I'll be damned if it's not acting like malware.
I read the internet for the articles.
the problem that I have with this isn't this particular patch, but the pattern.
Microsoft over the last 6 months have not had a patch cycle that didn't have major widespread issues with a patch that was eventually recalled. The last time they had problems this bad was sometime around 2002-2003, and back then they claimed that they changed their testing criteria to prevent major patch issues from happening, And it worked for a good while. At least I only had to worry about 1-2 bad patches a year at most.
This patch botch, however, takes the cake. There is absolutely no way this patch should have been able to pass a competent Q/A test. Every single windows 7 machine that got this patch through our test systems (which is about 100 PC's spread across multiple vendors and OS images) popped up a "you are a conterfeit victim" message within 24 hours of receiving the patch. There is no way they couldn't have run into this unless they are doing short term checks for patch related issues.
"The Patch Installed without crashing" is Not Good enough Q/A when you are rolling out a patch to millions of potential customers. Someone in MS Q/A Needs to get fired over these issues before it causes more damage (IE: People taking Forbes stupid advice, disabling critical updates and getting infected by some cryptovirus that wipes out all of their company files that could have been prevented by a patch install.)
In Soviet Russia, Trojan exploits YOU!
Forbes faithfully parroted every Gartner study fully bought for by Microsoft, like the Total Cost of Ownership. It claimed Microsoft has reached a "utility" status and it should be considered a "widows-and-orphans" stock. It actively contributed to the culture of lazy CIOs choosing Microsoft because no one got fired for choosing Microsoft. It turned a blind eye to every illegal maneuver by Microsoft. Now, suddenly, it is blasting Microsoft? I think Microsoft is a lesser evil than Forbes.
sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
So Microsoft starts laying off 18,000 employees in several waves starting in July this year. One of the first groups that was hit hard by layoffs was QA (mostly contract workers so they are easy to let go.) Within that, the QA department responsible for testing OS security patches was hit the hardest...
So now we are having a bunch of problems with botched updates that weren't tested sufficiently, go figure!