The BITS bandwidth limitation transitions are not applied to the ongoing transfers in Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1

Applies to: Windows 7 Service Pack 1Windows 7 EnterpriseWindows 7 Professional


Assume that you configure bandwidth throttling settings by using a Background Intelligent Transfer Service (BITS) Group Policy in an Active Directory domain environment. Then you perform transfers on a computer that is running Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1.

In this situation, when the second and subsequent transitions to a new bandwidth limit occur, these transitions are not applied to the ongoing transfers. Therefore, the transfers continue by using the previously specified bandwidth limitation until the process is complete.

You can observe this behavior by monitoring the network traffic in Performance Monitor by using various counters in the following performance objects:
  • Network Adapter
  • Network Interface
  • BITS

Note Network-related performance counters cannot differentiate between the traffic that is produced by BITS and other generic network traffic. Therefore, to ensure reliabilitythe measurement must be made by configuring a minimal usage of network bandwidth for other network services. For example, no large file transfers should occur while the measurement is performed.


This problem occurs when during a bandwidth limitation transition because a work-item is scheduled in an internal queue that is handled by BITS. Work items are marked by using a time stamp. If the indicated time is checked during a particular time interval, a problem in BITS code causes the work item to mistakenly be considered as expired. The work item is then discarded. After this occurs, all subsequent transitions experience the same problem because each work item posts another work item for the next scheduled transition.


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 Web site: 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.


To apply this hotfix, you must be running one of the following operating systems:

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.


To work around this problem, stop all ongoing transfers, and then restart them in order for the current bandwidth limitation to be applied correctly. You must continually apply this workaround because each transition will experience the same problem.


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