Bandwidth throttling reverts to the default settings after a Group Policy is updated in Windows 7 or in Windows Server 2008 R2

Article translations Article translations
Article ID: 2659493 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Assume that you configure bandwidth throttling settings by using a Background Intelligent Transfer Service (BITS) Group Policy on a computer that is running Windows 7 or Windows Server 2008 R2. Then, the Group Policies are updated on the computer. This action updates the bandwidth throttling settings. In this situation, the custom bandwidth settings that you implemented revert to the default settings when the Group Policy is updated.

Notes
  • Group Policies are automatically updated at a configurable interval (by default, this interval is 90 minutes). Or, you can manually update the Group Policies by executing the gpupdate /force command. This update does not imply any change. If a Group Policy is changed in the domain or locally, an update will apply the changes accordingly. If no Group Policy is changed, the update will reapply the original set of policies.
  • You can temporarily resolve this issue by restarting the BITS service. However, the issue occurs again when the Group Policies are next updated.
  • To implement a Background Intelligent Transfer Service (BITS) Group Policy, visit the following location in the Group Policy Management Console (GPMC):
    Computer Configuration\Administrative Templates\Network\Background Intelligent Transfer Service (BITS)

Cause

This issue occurs because of an incorrect behavior when BITS receives the Group Policy update notification after the Group Policies are updated on the computer. If the Background Intelligent Transfer Service (BITS) Group Policy is not changed since the last update, the custom bandwidth throttling settings revert to the default settings incorrectly.

Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 1 . 21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Qmgr.dll7.5.7601.21888585,72830-Dec-201105:27
Qmgr.mofNot applicable2,30210-Jun-200921:34
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Qmgr.dll7.5.7601.21888849,92030-Dec-201106:33
Qmgr.mofNot applicable2,30210-Jun-200920:53
Qmgr.mofNot applicable2,30212-Nov-201023:57
For all supported IA-64–based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Qmgr.dll7.5.7601.218881,772,03230-Dec-201105:21
Qmgr.mofNot applicable2,30210-Jun-200920:58
Qmgr.mofNot applicable2,30212-Nov-201023:57

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameX86_c915da80f2a2de00dddc55a588a680c5_31bf3856ad364e35_6.1.7601.21888_none_4273e18adbbe6d12.manifest
File versionNot applicable
File size699
Date (UTC)04-Jan-2012
Time (UTC)00:45
File nameX86_microsoft-windows-bits-client_31bf3856ad364e35_6.1.7601.21888_none_25da21237106e7a2.manifest
File versionNot applicable
File size113,723
Date (UTC)30-Dec-2011
Time (UTC)06:02
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_25fe8fcffcc25e4b5cae8c53849d4e4a_31bf3856ad364e35_6.1.7601.21888_none_49acd14d0a4b3d0e.manifest
File versionNot applicable
File size1,048
Date (UTC)04-Jan-2012
Time (UTC)00:45
File nameAmd64_microsoft-windows-bits-client_31bf3856ad364e35_6.1.7601.21888_none_81f8bca7296458d8.manifest
File versionNot applicable
File size113,729
Date (UTC)30-Dec-2011
Time (UTC)07:05
File nameWow64_microsoft-windows-bits-client_31bf3856ad364e35_6.1.7601.21888_none_8c4d66f95dc51ad3.manifest
File versionNot applicable
File size53,420
Date (UTC)30-Dec-2011
Time (UTC)05:45
Additional files for all supported IA-64–based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_08a099739854aad2419589b09b866ac9_31bf3856ad364e35_6.1.7601.21888_none_e6fb6e7145151d2a.manifest
File versionNot applicable
File size1,046
Date (UTC)04-Jan-2012
Time (UTC)00:44
File nameIa64_microsoft-windows-bits-client_31bf3856ad364e35_6.1.7601.21888_none_25dbc5197104f09e.manifest
File versionNot applicable
File size113,726
Date (UTC)30-Dec-2011
Time (UTC)10:23
File nameWow64_microsoft-windows-bits-client_31bf3856ad364e35_6.1.7601.21888_none_8c4d66f95dc51ad3.manifest
File versionNot applicable
File size53,420
Date (UTC)30-Dec-2011
Time (UTC)05:45

Properties

Article ID: 2659493 - Last Review: January 4, 2013 - Revision: 2.0
Applies to
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 for Itanium-Based Systems
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2659493

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com