New Windows 7 Updates (Non-Security, But Important)

Users of Windows 7 that don’t have automatic updates turned to force feed (all of you, I hope) may have missed the updates that Microsoft released for Windows 7 and all related operating systems. The helpful guys at Ars Technica were on the stick, though, and have a list of the things that you might need to download, as you will never be notified otherwise.

Monday night, Microsoft released a slew of updates for Windows, the majority of which were targeted for the latest versions of the client and server operating systems. None of these are security updates: this wasn’t Patch Tuesday and Microsoft is not yet ready to address the 17-year-old Windows flaw. The most important update is just like the first stability and reliability update for the OSes, but smaller: Windows 7 32-bit (1.2MB), Windows 7 64-bit (1.7MB), Windows Server 2008 R2 64-bit (1.7MB), and Windows Server 2008 R2 Itanium (2.1MB).

The patch resolves issues that affect some computers that use the Error Reporting service or Microsoft Customer Support Services. Microsoft plans to regularly release Windows 7 and Windows Server 2008 R2 stability and reliability updates, and this one builds on those that preceded it, adding the following fixes:

• Keyboard function keys or keyboard shortcuts, such as mute or calculator, may not work correctly
• The notification icon for an application may be moved or lost when the executable application is update
• On a computer that is running Windows 7, you configure the Screen Saver Settings to display the logon screen on resume. Additionally, you configure the computer to go to sleep. However, the computer may not go to sleep after the screen saver starts. Instead, a black screen is displayed. This problem causes the operating system to stop responding. You must restart the computer by holding down the power button.

If you’re experiencing the issues described, you can download the updates from the Microsoft Download Center. Otherwise you can just wait till they trickle down via Windows Update—or until Service Pack 1 arrives.

The next update is for an issue that occurs in a very specific scenario: your Windows 7 or Windows Server 2008 R2 computer has an NVIDIA USB Enhanced Host Controller Interface (EHCI) chipset, at least 4GB of RAM, and while performing general I/O operations on an external USB device, such as copying data from the computer, either your computer stops responding or the copy operation stops abruptly. The fix is available for Windows 7 32-bit (449KB) and Windows 7 and Windows Server 2008 R2 64-bit (516KB). Microsoft plans on including this update in SP1.

Microsoft also released updated versions of the System Update Readiness Tool for Windows Vista and Windows Server 2008 32-bit (104.1MB), Windows Vista and Windows Server 2008 64-bit (142.0MB), Windows Server 2008 Itanium (32.2MB), Windows 7 32-bit (28.9MB), Windows 64-bit (93.8MB), Windows Server 2008 R2 64-bit (93.8MB), and Windows Server 2008 R2 Itanium (16.3MB). The tool was originally released in September 2009 to resolve certain conditions that could cause installing updates and other software not to work. Typically you do not have to manually run this tool (it is offered automatically through Windows Update to computers that have a condition that the tool could resolve). It runs a one-time scan for inconsistencies that might prevent future servicing operations and usually takes less than 15 minutes (though it has been known to appear as if it’s stopped at 60 percent when run from Windows Update).

The Windows NT Backup Restore Utility has also been updated for Windows 7 32-bit (599KB), Windows 7 64-bit (669KB), Windows Server 2008 R2 64-bit (669KB), and Windows Server 2008 R2 Itanium (1000KB). The tool was originally released in November 2009 and notably no longer included Removable Storage Manager (RSM), used for restoring backups from tape devices. Microsoft has no plans to include this update in SP1.

Some may wonder why I don’t allow the people in Redmond to push things on my machine by using the automatic option, as I have nothing on the machine that is of a nature that would need to be secured or hidden. The answer is that, on several occasions with Windows XP, the automatic download took place, and after the required reboot, the machine was pretty well hosed. On one of the occasions, the machine was completely without possibility of salvation. On a couple of others, the machine took two to three hours of my time I could have otherwise avoided, because when doing the manual method, it is possibly to install the updates one at a time, thereby avoiding one problem with updates – one update trashing another; also having only one possibility to play detective with at a time makes the repairs go much, much faster.

§

Be vewwy, vewwy careful, we’re updating Windows…ha,ha,ha,ha    Wouldn’t this make automatic updates much more entertaining?

⌘