Configure BITS Idle Timeout in Registry

The Background Intelligent Transfer Service (BITS) relies on specific Windows Registry keys to manage its idle timeout behavior, inactive job lifespans, and automatic service shutdown thresholds. This guide details the exact registry keys used to configure BITS idle timeout settings in the Windows Registry Editor (regedit) and explains how to modify these values to optimize network and background transfer management.


The Registry Key for BITS Job Inactivity Timeout

The primary policy key that controls how long BITS waits before canceling an idle or inactive transfer job is located under the Windows Policies path:

When a BITS transfer job is paused or remains inactive without progress, Windows tracks the idle duration. Once the idle period exceeds the specified number of days in JobInactivityTimeout, the service automatically cancels the job and deletes associated temporary files.


Step-by-Step Configuration in Regedit

  1. Press Win + R, type regedit, and press Enter to open the Registry Editor.

  2. Navigate to the following path:

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\BITS

    (If the BITS key does not exist under Windows, right-click Windows, select New > Key, and name it BITS.)

  3. Right-click the BITS key, select New > DWORD (32-bit) Value, and name it JobInactivityTimeout.

  4. Double-click JobInactivityTimeout, set the Base to Decimal, and enter the desired number of days before an idle job is canceled.

  5. Click OK to save the changes.


Service-Level Idle and Execution Settings

For core service management and parameters outside of Group Policy, the service configuration is stored at:

This key contains low-level parameters governing the service binary, service triggers, and hosting DLL configurations (qmgr.dll). In modern Windows versions, BITS is configured as a trigger-started service that automatically enters an idle state and shuts down shortly after all queued jobs complete or become idle.


Applying the Changes

After editing the registry, apply the changes immediately by restarting the service via the Command Prompt (Admin) or PowerShell:

net stop BITS
net start BITS