cgthamm

KB2528984 - Functionality issues on USB devices that are connected to a Windows 7-based computer that has an Intel platform
 
NOTE: This is version 2 of the hotfix, and replaces the original version that was previously uploaded.
 
NOTE: This hotfix has been replaced by the following update:
 
KB4041686 - October 10, 2017—KB4041686 (Preview of Monthly Rollup)

KB2990941 - Update to support NVM Express by using native drivers in Windows 7 or Windows Server 2008 R2
 
NOTE: You must follow the instructions in the aforementioned Knowledge Base article to apply this hotfix to the boot.wim image.

KB3087873 - "0x0000007E" Stop error after you install hotfix 2990941 in Windows 7 SP1 or Windows Server 2008 R2 SP1

KB2921916 - The "Untrusted publisher" dialog box appears when you install a driver in Windows 7 or Windows Server 2008 R2

KB2851149 - "0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL" Stop error on a Windows 7 SP1 or Windows Server 2008 R2 SP1-based computer

KB3125574 - Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
NOTE: You MUST install KB3177467, available from the Microsoft Download Center, before installing this rollup update.
 
NOTE: You may want to download and install KB3139923-v2, available from the Microsoft Download Center, after installing this rollup update. Its original version is included in the rollup update, and it has since been updated to version 2. You can alternatively have Windows Update install it for you.
 
NOTE: There are several known issues with this rollup update, for which Microsoft has now provided resolutions. Please refer to the aforementioned Knowledge Base article for details and instructions.
 
 
Additional Known Issues:
 
1. Windows Update may return error 0x80240019 the first time you check for updates following the installation of this rollup update. Should this happen to you, simply wait a few minutes and check for updates again.
 
2. Windows Update may not be able to successfully finish checking for updates, no matter how long you let it run. Should this happen to you, temporarily disable automatic updating, restart your computer, and manually download and install the following update (available from the Microsoft Download Center):
 
KB3161608 - June 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Don't forget to re-enable automatic updating afterwards.
 
3. Microsoft Office 2010 doesn't start when EMET is enabled. The solution is to download and install the June 2016 update follup for Windows 7 SP1 and Windows Server 2008 R2 SP1 (the same one as for Additional Known Issue 2, above). This Known Issue is documented by Microsoft here:
 
KB3163644 - Microsoft Office 2010 doesn't start when EMET is enabled in Windows 7 or Windows Server 2008 R2
 
4. Configuring updates may hang at 13% if certain USB devices (e.g. headsets) are connected when you install the rollup update. If this happens to you, let it timeout and roll back (this will take time -- be patient). Worst case, Configuring updates may freeze, in which case you'll have to power down your computer to have it roll back successfully. Once it has rolled back, unplug all USB devices except for mouse and keyboard, and re-install the rollup update. (Alternatively, you can remove any unnecessary USB devices before installing the rollup update and avoid this issue altogether.)
 
 
Additional information regarding Microsoft's change in servicing model for Windows 7:
 
Microsoft has changed the servicing model for Windows 7 to make it more like the servicing models it introduced in Windows 8, 8.1, and 10. Specifically, this means that instead of releasing hotfixes, Microsoft will be releasing monthly update rollups that contain all the fixes that would have been released as individual hotfixes.
 
(Editorial: In general, this is a good thing, as it makes it easier to build and maintain OS deployment images. On the down side, if there is a bug in an update rollup, you are stuck uninstalling the entire rollup, as opposed to just the hotfix with the bug.)
 
Since this Convenience update rollup was released, there has been a correction to one of the hotfixes included in it (kb3139923-v2). Microsoft also released the May 2016 update rollup (KB3156417). Beginning with the June 2016 update rollup (KB3161608), Windows 7 update rollups became cumulative (i.e. the July 2016 update rollup (KB3172605) includes all the fixes in -- and replaces -- the June update rollup.
 
Updated 2016-08-17: Microsoft has released the August 2016 hotfix rollup (KB3179573). In yet another case of the right hand being clueless as to what the left hand is doing, this hotfix rollup (like the May hotfix rollup) is NOT cumulative, and must be installed in addition to the other post-KB3125574-v4 updates. Here is the Knowledge Base article for KB3179573:
 
KB3179573 - August 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Further, this hotfix rollup corrects a problem in SMB, so I took a look around for other recent Knowledge Base articles that discuss SMB issues, and found this:
 
KB3181029 - SMB file server share access is unsuccessful through DNS CNAME alias
 
In the Troubleshooting section, Microsoft still recommends applying KB2775511 and its post-requisite hotfixes. To do this successfully, you should apply them before KB3125574-v4.
 
Updated 2017-02-28: Since I last updated this article, Microsoft released a servicing stack update for Windows 7:
 
KB3177467 - Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: September 20, 2016
 
Servicing stack updates should always be deployed as soon as possible after they are released. Microsoft also released an additional non-cumulative update rollup:
 
KB3185278 - September 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Starting in October, 2016, update rollups for Windows 7 became cumulative. As a hotfixer, I am interested by the cumulative updates that include both security updates and hotfixes. Microsoft has designated these as Security Monthly Quality Rollups. The most recently released one is:
 
KB3212646 - January 2017 Security Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Microsoft initially had a few problems making the update rollups cumulative. Of particular note, there were issues with supersedence. These now appear to be resolved, and hotfixers can keep their systems up-to-date by installing the most recent Security Monthly Quality Rollup.
 
-----
 
What does all of this mean in practical terms? Say you wanted to streamline your Windows 7 installation process. If you choose to follow Microsoft's new servicing model (including its ongoing recommendation to install KB2775511) for Windows 7, start with Windows 7 SP1, and install all of the following:
 
KB3177467 (the most recent Servicing Stack for Windows 7)
KB2775511 (the enterprise hotfix rollup)
+KB2581608 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)
+KB2752259 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)
+KB2732673 (a post-requisite for the enterprise hotfix rollup)
+KB2728738 (a post-requisite for the enterprise hotfix rollup)
+KB2878378 (a post-requisite for the enterprise hotfix rollup)
KB3125574-v4 (the April 2016 Convenience update rollup)
+KB3139923-v2 (a hotfix that was included in KB3125574-v4, but that has updated since its release)
KB3156417 (the May 2016 update rollup)
KB3172605 (the July 2016 cumulative update rollup)
KB3179573 (the August 2016 update rollup)
KB3185278 (the September 2016 update rollup)
KB3212646 (the January 2017 Security Monthly Quality Rollup)
 
With 14 updates/hotfixes, you get a basic up-to-date Windows 7 installation that will work well for many users. You could then install additional updates and hotfixes that you want that are not included in KB3125574-v4. (For example, I install the security updates for Internet Explorer and the hotfixes for Remote Desktop.)

KB2922790 - Some software products function incorrectly in Windows 7 and Windows Server 2008 R2

KB2528984 - Functionality issues on USB devices that are connected to a Windows 7-based computer that has an Intel platform
 
NOTE: This is version 2 of the hotfix, and replaces the original version that was previously uploaded.
 
NOTE: This hotfix has been replaced by the following update:
 
KB4041686 - October 10, 2017—KB4041686 (Preview of Monthly Rollup)

KB2921916 - The "Untrusted publisher" dialog box appears when you install a driver in Windows 7 or Windows Server 2008 R2

KB3125574 - Convenience rollup update for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
NOTE: You MUST install KB3177467, available from the Microsoft Download Center, before installing this rollup update.
 
NOTE: You may want to download and install KB3139923-v2, available from the Microsoft Download Center, after installing this rollup update. Its original version is included in the rollup update, and it has since been updated to version 2. You can alternatively have Windows Update install it for you.
 
NOTE: There are several known issues with this rollup update, for which Microsoft has now provided resolutions. Please refer to the aforementioned Knowledge Base article for details and instructions.
 
 
Additional Known Issues:
 
1. Windows Update may return error 0x80240019 the first time you check for updates following the installation of this rollup update. Should this happen to you, simply wait a few minutes and check for updates again.
 
2. Windows Update may not be able to successfully finish checking for updates, no matter how long you let it run. Should this happen to you, temporarily disable automatic updating, restart your computer, and manually download and install the following update (available from the Microsoft Download Center):
 
KB3161608 - June 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Don't forget to re-enable automatic updating afterwards.
 
3. Microsoft Office 2010 doesn't start when EMET is enabled. The solution is to download and install the June 2016 update follup for Windows 7 SP1 and Windows Server 2008 R2 SP1 (the same one as for Additional Known Issue 2, above). This Known Issue is documented by Microsoft here:
 
KB3163644 - Microsoft Office 2010 doesn't start when EMET is enabled in Windows 7 or Windows Server 2008 R2
 
4. Configuring updates may hang at 13% if certain USB devices (e.g. headsets) are connected when you install the rollup update. If this happens to you, let it timeout and roll back (this will take time -- be patient). Worst case, Configuring updates may freeze, in which case you'll have to power down your computer to have it roll back successfully. Once it has rolled back, unplug all USB devices except for mouse and keyboard, and re-install the rollup update. (Alternatively, you can remove any unnecessary USB devices before installing the rollup update and avoid this issue altogether.)
 
 
Additional information regarding Microsoft's change in servicing model for Windows 7:
 
Microsoft has changed the servicing model for Windows 7 to make it more like the servicing models it introduced in Windows 8, 8.1, and 10. Specifically, this means that instead of releasing hotfixes, Microsoft will be releasing monthly update rollups that contain all the fixes that would have been released as individual hotfixes.
 
(Editorial: In general, this is a good thing, as it makes it easier to build and maintain OS deployment images. On the down side, if there is a bug in an update rollup, you are stuck uninstalling the entire rollup, as opposed to just the hotfix with the bug.)
 
Since this Convenience update rollup was released, there has been a correction to one of the hotfixes included in it (kb3139923-v2). Microsoft also released the May 2016 update rollup (KB3156417). Beginning with the June 2016 update rollup (KB3161608), Windows 7 update rollups became cumulative (i.e. the July 2016 update rollup (KB3172605) includes all the fixes in -- and replaces -- the June update rollup.
 
Updated 2016-08-17: Microsoft has released the August 2016 hotfix rollup (KB3179573). In yet another case of the right hand being clueless as to what the left hand is doing, this hotfix rollup (like the May hotfix rollup) is NOT cumulative, and must be installed in addition to the other post-KB3125574-v4 updates. Here is the Knowledge Base article for KB3179573:
 
KB3179573 - August 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Further, this hotfix rollup corrects a problem in SMB, so I took a look around for other recent Knowledge Base articles that discuss SMB issues, and found this:
 
KB3181029 - SMB file server share access is unsuccessful through DNS CNAME alias
 
In the Troubleshooting section, Microsoft still recommends applying KB2775511 and its post-requisite hotfixes. To do this successfully, you should apply them before KB3125574-v4.
 
Updated 2017-02-28: Since I last updated this article, Microsoft released a servicing stack update for Windows 7:
 
KB3177467 - Servicing stack update for Windows 7 SP1 and Windows Server 2008 R2 SP1: September 20, 2016
 
Servicing stack updates should always be deployed as soon as possible after they are released. Microsoft also released an additional non-cumulative update rollup:
 
KB3185278 - September 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Starting in October, 2016, update rollups for Windows 7 became cumulative. As a hotfixer, I am interested by the cumulative updates that include both security updates and hotfixes. Microsoft has designated these as Security Monthly Quality Rollups. The most recently released one is:
 
KB3212646 - January 2017 Security Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
Microsoft initially had a few problems making the update rollups cumulative. Of particular note, there were issues with supersedence. These now appear to be resolved, and hotfixers can keep their systems up-to-date by installing the most recent Security Monthly Quality Rollup.
 
-----
 
What does all of this mean in practical terms? Say you wanted to streamline your Windows 7 installation process. If you choose to follow Microsoft's new servicing model (including its ongoing recommendation to install KB2775511) for Windows 7, start with Windows 7 SP1, and install all of the following:
 
KB3177467 (the most recent Servicing Stack for Windows 7)
KB2775511 (the enterprise hotfix rollup)
+KB2581608 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)
+KB2752259 (to automatically apply a required registry entry, which is not included in the enterprise hotfix rollup)
+KB2732673 (a post-requisite for the enterprise hotfix rollup)
+KB2728738 (a post-requisite for the enterprise hotfix rollup)
+KB2878378 (a post-requisite for the enterprise hotfix rollup)
KB3125574-v4 (the April 2016 Convenience update rollup)
+KB3139923-v2 (a hotfix that was included in KB3125574-v4, but that has updated since its release)
KB3156417 (the May 2016 update rollup)
KB3172605 (the July 2016 cumulative update rollup)
KB3179573 (the August 2016 update rollup)
KB3185278 (the September 2016 update rollup)
KB3212646 (the January 2017 Security Monthly Quality Rollup)
 
With 14 updates/hotfixes, you get a basic up-to-date Windows 7 installation that will work well for many users. You could then install additional updates and hotfixes that you want that are not included in KB3125574-v4. (For example, I install the security updates for Internet Explorer and the hotfixes for Remote Desktop.)

KB2920188 - Update to add support for TPM 2.0 in Windows 7 and Windows Server 2008 R2

KB2815853 - RPC service crashes on a Windows 7-based or Windows Server 2008 R2-based COM client

KB2775511 - An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
 
NOTE: After this hotfix rollup is installed, you must create/update registry keys to enable two of its features. Refer to the aforementioned Microsoft Knowledge Base article for details and instructions. Alternatively, you may install hotfixes kb2581608 and kb2752259 after installing this hotfix rollup to accomplish this.
 
NOTE: After installing this hotfix, you must also install kb2732673-v4 to fix a regression in Rdbss.sys.
 
NOTE: After installing this hotfix, you must also install kb2728738-v3 to fix a regression in Profsvc.dll.
 
NOTE: After installing this hotfix, you must also install kb2601014-v2 to fix a regression in Mrxsmb10.sys.
 
NOTE: After installing this hotfix, you must also install kb2878378-v2 to fix a regression in Advapi32.dll.

KB2726399 - You cannot change the DPI setting through a Remote Desktop session on a computer that is running Windows 7 or Windows Server 2008 R2
 
NOTE: This is version 3 of the hotfix, and replaces the previously uploaded versions.
 
NOTE: This hotfix is included in hotfix rollup 2775511.

KB2920188 - Update to add support for TPM 2.0 in Windows 7 and Windows Server 2008 R2

KB959542 - A warning event is logged repeatedly on a member computer that is running Windows Server 2008 or Windows Server 2003 R2 when you configure read-only replicated folders on a computer that is running Windows Server 2008 R2

KB2731284 - "33" DOS error code when memory memory-mapped files are cleaned by using the FlushViewOfFile() function in Windows 7 or in Windows Server 2008 R2

KB961799 - Une erreur d’arrêt se produit sur un serveur Windows Server 2003, lorsqu’un utilisateur accède à des fichiers partagés sur le serveur à l’aide d’une connexion SMB

KB2982006 - IIS crashes occasionally when a request is sent to a default document in Windows 8.1 or Windows Server 2012 R2

KB959252 - Error message when you switch the operating system from a dual monitor setting to a single monitor setting on a Windows XP-based computer or on a Windows Server 2003-based computer that has the security update 954211 installed: "Stop 0x0000008E"

KB982867 - WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1 or in .NET Framework 4

KB2990941 - Update to support NVM Express by using native drivers in Windows 7 or Windows Server 2008 R2
 
NOTE: You must follow the instructions in the aforementioned Knowledge Base article to apply this hotfix to the boot.wim image.

KB979744 - A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application
 
NOTE: This is version 2 of the hotfix, and replaces the original version that was previously uploaded.

KB2846340 - Duplicate friendly names of network adapters are displayed in Windows 7, Windows 8, Windows Server 2008 R2, and Windows Server 2012
 
NOTE: This is version 2 of the hotfix. This version is specifically to be installed in the case of an OEM vendor instructing you to install hotfix 2846430 before upgrading your networking drivers. All other users should install hotfix 2846340-v3 instead.

KB2820470 - Delayed error message when you try to access a shared folder that no longer exists in Windows Server 2012
 
NOTE: After this hotfix is installed, you must create/update a registry key to enable it. Refer to the aforementioned Microsoft Knowledge Base article for details and instructions.