Windows Server 2019 — BITS service stuck queueing transfers after WSUS sync — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

The Background Intelligent Transfer Service on Windows Server 2019 enters a state where downloads queue but never complete. Windows Update, WSUS, and other BITS-aware clients stall, and the server falls behind on patch downloads or deployment payloads.

Environment & Reproduction

Often appears after a long WSUS catalogue sync or a network change. Inspect the BITS state log and System log for BITS-Client events.

Get-Service -Name bits
Get-WinEvent -LogName System -MaxEvents 40
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

Root Cause Analysis

Causes include a corrupted qmgr.db job database, a stalled job state file, proxy misconfiguration, or BITS dependencies not initialising correctly.

Quick Triage

Capture the BITS job list and the recent BITS-Client error events before any reset.

sc.exe query bits
Get-Service -Name bits | Select-Object Status,StartType
Get-EventLog -LogName System -Newest 30 | Where-Object {$_.Source -match 'bits'}

Step-by-Step Diagnosis

Enumerate active and suspended BITS jobs and read recent BITS error events.

Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.ProviderName -match 'bits'} | Select TimeCreated,Id,LevelDisplayName,Message
sc.exe qfailure bits
sfc /verifyonly

Solution — Primary Fix

Stop BITS, remove the corrupted qmgr database files, then start BITS and let it recreate the job store cleanly.

Restart-Service -Name bits -Force
Get-Service -Name bits | Select-Object Status,StartType
Get-WinEvent -LogName System -MaxEvents 20 | Where-Object {$_.ProviderName -match 'bits'}

Solution — Alternative Approaches

If the issue persists, reset WinHTTP and BITS proxy and reauthenticate against the WSUS endpoint.

sc.exe config bits start= auto
sc.exe failure bits reset= 86400 actions= restart/60000/restart/60000/run/1000
Restart-Service -Name bits -Force

Verification & Acceptance Criteria

BITS runs, new test transfers complete, and the WSUS or Update agent resumes downloading without long stalls.

Get-Service -Name bits
Get-WinEvent -LogName System -MaxEvents 25 | Where-Object {$_.ProviderName -match 'bits' -and $_.LevelDisplayName -eq 'Error'}
Test-NetConnection -ComputerName localhost -Port 

Rollback Plan

Restore the previous qmgr database files from the most recent system state backup.

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
wbadmin get versions
# Restore previous configuration export if available

Prevention & Hardening

Monitor BITS job count, set job age limits, and avoid storing oversized payloads on the BITS spool drive.

Get-Service -Name bits | Export-Clixml C:/Temp/bits-baseline.xml
Get-WinEvent -LogName System -MaxEvents 50 > C:/Temp/bits-events.txt
Get-ScheduledTask | Where-Object {$_.TaskName -match 'bits'}

Related Errors & Cross-Refs

Linked to events 16403, 16392, and 16415 from BITS-Client.

Related tutorial: View the step-by-step tutorial for Windows Server 2019.

View all Windows Server 2019 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for BITS troubleshooting on Windows Server 2019.