Windows 7: List of Available Hotfixes for Windows 7

NoN · 16 Jan 2013

Thought those codes might help some of you facing troubleshoot Windows 7 Activation error codes.

Infos: Microsoft Technet: Volume Activation

-Article ID: 938450 - Last Review: September 26, 2012 - Revision: 13.0
How to troubleshoot Volume Activation error codes in Windows 7, in Windows Server 2008, and in Windows Vista.

Introduction:
When you try to use a Multiple Activation Key (MAK) or the Key Management Service (KMS) to perform Volume Activation on one or more computers that are running Windows 7, Windows Server 2008, or Windows Vista, you receive error messages that contain specific error codes. This article discusses how to troubleshoot these errors.

More Information:
How to troubleshoot Volume Activation error codes in Windows 7, in Windows Server 2008, and in Windows Vista

-Article ID: 2230957 - Last Review: February 17, 2012 - Revision: 1.0
Error code 0x8007000D when trying to activate a Windows server 2008 or Windows 7 machine using any type of product key.

Symptoms:
You try to activate a Windows Server 2008 or Windows 7 machine using any type of product key.
Running slsmgr -dlv or slmgr -ato from a command line generates the following:

The data is invalid. Error code 8007000d.

Cause:
The System account by default has Full Control permissions to the registry path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root and any subkeys.
If those permissions have been altered for the 'Root' key or any subkey(s), we would see the error code 0x8007000D

Fix This Problem:
Error code 0x8007000D when trying to activate a Windows server 2008 or Windows 7 machine using any type of product key.

This could be useful for some but was first intended to be applyed on Windows 7 Enterprise based system.
-Article ID: 2736303 - Last Review: December 27, 2012 - Revision: 2.0
How to rebuild the Tokens.dat file when you troubleshoot Windows activation issues.

Summary:
When you troubleshoot Windows activation issues, you may have to rebuild the Tokens.dat file. This article lists the steps to rebuild the Tokens.dat file.

http://support.microsoft.com/kb/2736303/en-us

NoN · 22 Jan 2013

-Article ID: 2794119 - Last Review: January 22, 2013 - Revision: 2.0
Israel and Libya time zone update for Windows operating systems.

Summary:
This update contains time zone changes that were recently announced in Libya and Israel.

We recommend that you deploy the most current Windows cumulative time zone update (KB2779562) before installing this to guarantee the consistency of the time zone database on all systems.

Israel and Libya time zone update for Windows operating systems

Note: The Kb Article ID: 2779562 is required before this install.

NoN · 10 Mar 2013

System Update Readiness Tool for Windows 7 x32bits & Windows 7 x64bits (KB947821) [February 2013]

http://support.microsoft.com/kb/947821/en-us

Overview:
This tool is being offered because an inconsistency was found in the Windows servicing store which may prevent the successful installation of future updates, service packs, and software. This tool checks your computer for such inconsistencies and tries to resolve issues if found.

x64: Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [February 2013] from Official Microsoft Download Center

x32: Download System Update Readiness Tool for Windows 7 (KB947821) [February 2013] from Official Microsoft Download Center

DavidW7ncus · 10 Mar 2013

Thanks NoN!

Is it advisable to install/run this tool even if I haven't had any problems installing updates so far?
Or, is it better to NOT use this tool until/if a problem with updates happens?
To me it sounds like a repair tool to check for issues and try to fix them, similar to SFC /scannow.
And, part of me thinks "If it ain't broke, don't fix it".

NoelDP · 11 Mar 2013

The tool is basically a huge funpack of the manifests and MUM/CAT files present in Windows - it won't do any harm to run it, but if you're not seeing any problems, then it won't do anything for you.

The x64 version now approaches 375MB before unpacking - and up to 3.5GB after! (just for fun I started doing the relevant ones for Windows 7 x64 Client last night.... got as far as 1.93GB before I called it a night, and was less than 1/2 way through - 170,000+ files involved!!)

DavidW7ncus · 11 Mar 2013

Thanks Noel for the explanation!
+1

Teerex · 12 Mar 2013

There's some kind of an update roll-up for Windows 7 SP1. I self-volunteered my system as a guinea-pig, it installed fine, and I've seen no issues so far.

Quote:

An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

This article describes a hotfix rollup for Windows 7 Service Pack 1 (SP1)-based and Windows Server 2008 R2 SP1-based computers. This hotfix rollup contains 90 hotfixes that were released after the release of SP1 for Windows 7 and Windows Server 2008 R2. These hotfixes improve the overall performance and system reliability of Windows 7 SP1-based and Windows Server 2008 R2 SP1-based computers. We recommend that you apply this hotfix rollup as part of your regular maintenance routine and build processes for Windows 7 and Windows Server 2008 R2 computers.

This hotfix rollup includes the following improvements:•Improves the Windows Client Remote File System components. These components include the following:◦Web-based Distributed Authoring and Versioning (WebDAV)
◦DFSN client
◦Folder Redirection
◦Offline Files and Folders (CSC)
◦SMB client
◦Redirected Drive Buffering Subsystem (RDB)
◦Multiple UNC Provider (MUP)

•Improves the SMB Service and TCP protocol components. These improvements work together with other improvements to help improve the overall networking performance on Windows 7 SP1-based and Windows Server 2008 R2 SP1-based computers.

Notes◦To take full advantage of this improvement for Windows 7 clients that log on to Windows Server 2008 R2 servers, install this rollup update on Windows 7 clients. Additionally, install this rollup update on the Windows Server 2008 R2 servers that clients authenticate and retrieve user profiles, policies and script data from during the startup and logon process. You can update your environment by installing this hotfix rollup on both clients and servers in no particular order.
◦Network improvements can be installed on the client or server. You may not notice any changes in performance until this update is installed on both client and server computers.

•Improves the processing of Group Policies and Group Policy preferences. The performance of computers is improved after you install this rollup update on Windows 7-based computers that have several Group Policy preferences configured. Additionally, the network load and the domain controller usage may be reduced. We recommend that you install this hotfix rollup on every Windows 7 computer that has Group Policy preferences configured.
•Improves the Windows Management Instrumentation (WMI) components to reduce the CPU usage and to improve the repository verification performance.
This rollup update contains the latest version of Windows system files that are updated after the SP1 release. The following hotfixes are included in this rollup update:

NoN · 21 Mar 2013

Quote: Originally Posted by DavidW7ncus

Thanks Noel for the explanation!
+1

Yes guys, it won't hurt any running the tool!

NoN · 21 Mar 2013

A kind of Windows 7 SP2 roll-up! (This had been discuss in some sevenforums threads, a week ago)

-Article ID: 2775511 - Last Review: March 13, 2013 - Revision: 3.0
An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1.

Introduction:
This article describes a hotfix rollup for Windows 7 Service Pack 1 (SP1)-based and Windows Server 2008 R2 SP1-based computers. This hotfix rollup contains 90 hotfixes that were released after the release of SP1 for Windows 7 and Windows Server 2008 R2. These hotfixes improve the overall performance and system reliability of Windows 7 SP1-based and Windows Server 2008 R2 SP1-based computers. We recommend that you apply this hotfix rollup as part of your regular maintenance routine and build processes for Windows 7 and Windows Server 2008 R2 computers.

This hotfix rollup includes the following improvements:

Improves the Windows Client Remote File System components. These components include the following:
- Web-based Distributed Authoring and Versioning (WebDAV)
- DFSN client
- Folder Redirection
- Offline Files and Folders (CSC)
- SMB client
- Redirected Drive Buffering Subsystem (RDB)
- Multiple UNC Provider (MUP)
Improves the SMB Service and TCP protocol components. These improvements work together with other improvements to help improve the overall networking performance on Windows 7 SP1-based and Windows Server 2008 R2 SP1-based computers.

Notes
- To take full advantage of this improvement for Windows 7 clients that log on to Windows Server 2008 R2 servers, install this rollup update on Windows 7 clients. Additionally, install this rollup update on the Windows Server 2008 R2 servers that clients authenticate and retrieve user profiles, policies and script data from during the startup and logon process. You can update your environment by installing this hotfix rollup on both clients and servers in no particular order.
- Network improvements can be installed on the client or server. You may not notice any changes in performance until this update is installed on both client and server computers.
Improves the processing of Group Policies and Group Policy preferences. The performance of computers is improved after you install this rollup update on Windows 7-based computers that have several Group Policy preferences configured. Additionally, the network load and the domain controller usage may be reduced. We recommend that you install this hotfix rollup on every Windows 7 computer that has Group Policy preferences configured.
Improves the Windows Management Instrumentation (WMI) components to reduce the CPU usage and to improve the repository verification performance.

This rollup update contains the latest version of Windows system files that are updated after the SP1 release.

An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1

Important Note:
Registry information:

This enterprise hotfix rollup package contains two individual hotfixes that are not enabled by the enterprise hotfix rollup installer. To enable these two hotfixes, there are two options:

1) Logon scripts take a long time to run in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2.
Logon scripts take a long time to run in Windows Vista, in Windows Server 2008, in Windows 7 or in Windows Server 2008 R2

2) An update that improves the performance of the Printbrm.exe command-line tool in Windows 7 or in Windows Server 2008 R2 is available.
An update that improves the performance of the Printbrm.exe command-line tool in Windows 7 or in Windows Server 2008 R2 is available

Or, you can manually or programmatically set two registry keys by using the following steps:

To enable update 2581608, configure a REG_DWORD Value named RunLogonScriptsNormally under the following path, and set the value to a decimal value of 1:HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
To enable update 2752259, configure a REG_DWORD Value named BrmDisableOpc under the following path, and set the value to a decimal value of 0:HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Print

Direct Download link:Microsoft Update Catalog

NoN · 28 Mar 2013

-Article ID: 973817 - Last Review: March 18, 2013 - Revision: 4.0
The Reg.exe utility does not compress a registry key when the utility saves a registry key to a hive file.

Symptoms:
Consider the following scenario:

You try to make copies of the registry or of the registry keys on a computer that is running one of the following operating systems:
- Windows Vista
- Windows Server 2008
- Windows 7
- Windows Server 2008 R2
- Windows 8
- Windows Server 2012
You use the reg save command to export the registry key into a hive file.

In this scenario, the reg save command does not compress the registry key during the exporting process. Therefore, the size of the hive file may be larger than expected.

Resolution:
A hotfix is available to resolve this issue. After you install this hotfix, you can use the /c switch in the reg save command to compress the registry key. For example, the following command compresses the HKLM\System subkey:reg save hklm\system %windir%\system32\config\system.lkg /y /c.

Request Hotfix:
The Reg.exe utility does not compress a registry key when the utility saves a registry key to a hive file

Workaround:
To work around the issue, you can manually export a registry key into a hive file by using the Registry Editor (Regedit.exe) utility. The Registry Editor (Regedit.exe) utility exports a compressed registry key into a hive file.

Windows 7: List of Available Hotfixes for Windows 7

List of Available Hotfixes for Windows 7 problems?