I do know this. I encourage my local clients to install all Microsoft updates (including KB2592664) other than for hardware, and I do it for the three computers here that run Windows 7, and so far, none of us have experienced any problems which
can be accredited to Microsoft updates..
I used the term "fix" in my last response, when I really meant "update" ... sorry for any confusion I may have caused.
You are very fortunate to not have experienced any problems that were accredited to Microsoft updates.
I realize that you stated "other than for hardware" ... but consider the update
KB2862330. This was a security update that came out as part of
MS13-081 and would have been automatically installed by anyone who had their Windows Update setting on Automatic. The description in MS13-081 does not mention hardware, but says this:
"The security update addresses these vulnerabilities by correcting the way that Windows handles specially crafted OpenType Font files and specially crafted TrueType Font (TTF) files, and by correcting the way that Windows handles objects in memory."
Many people who installed this update subsequently experienced a blue screen.
Below is an excerpt from Microsoft's description of known issues with KB2862330. While not everyone who installed KB2862330 experienced the known problems described below, many did .... my point being that someone with Windows Update set to automatic could
end up installing an update that subsequently caused a blue screen ... so before I install the monthly updates, I prefer to wait a few weeks (except for updates that address zero-day issues) and do some research to see if any of the monthly updates are known
to be causing problems after being installed.
I have used System Restore on my Windows 7 computer, but I find that mitigating a problem like the one shown below is seldom as simple as going back to the previous Restore Point ... I'd rather do my due diligence up front and avoid problems like this:
[excerpted from KB2862330]
Known issues with this security update
Symptoms
After you install this security update on a computer that is running Windows 7 SP1 or Windows Server 2008 R2 SP1, you may receive a D1 or 100000D1 stop error message that resembles the following:
*** STOP: 0x000000D1(parameter1, parameter2, parameter3, parameter4)
DRIVER_IRQL_NOT_LESS_OR_EQUAL
Cause
The installation of security update 2862330 should update all the drivers for the USB 2.0 core stack. However, in some specific computer configurations, the Usbport.sys driver is not updated. After the USB 2.0 core stack is in a partly updated state, a D1 or
100000D1 Stop error may occur.
The stop error is observed in any of the following situations:
- When the computer is transitioning to or from a lower power state (Sleep or Hibernation)
- When a USB port resumes from "selective suspend" mode
- During the installation of the update itself