Why BITS Reaches 99 Percent Disk on Idle on Windows 11

You open Task Manager on a quiet Windows 11 PC and see the Background Intelligent Transfer Service using 99 percent disk activity. The system feels sluggish even though no files are being actively downloaded or uploaded. This behavior occurs because BITS is processing a large queue of pending file transfer jobs during system idle time. This article explains the root cause of BITS high disk usage, provides steps to identify and manage the jobs, and shows how to prevent it from interfering with normal system performance.

Why BITS Drives Disk Usage to 99 Percent During Idle

The Background Intelligent Transfer Service is a Windows component designed to transfer files between machines using idle network bandwidth. It operates as a background process and uses disk I/O to manage job queues, metadata, and temporary file storage. When BITS reports 99 percent disk activity on an idle system, the root cause is almost always a large number of queued or stuck transfer jobs.

BITS jobs are created by Windows Update, Microsoft Store updates, and third-party applications that use the service for download or upload operations. Each job creates a temporary file in the BITS cache folder, typically located at C:\ProgramData\Microsoft\Network\Downloader. When many jobs accumulate, the service must read and write metadata for each job, causing sustained disk I/O. The disk usage spike is most visible on systems with hard disk drives because HDDs have lower random I/O performance compared to SSDs.

The service uses idle detection logic. When the system is idle, BITS resumes paused jobs, processes new jobs, and cleans up completed jobs. If a job is stuck in a transferring state because the remote server is unreachable or the file is locked, BITS retries the job repeatedly. Each retry generates disk writes for the temporary file and metadata updates, creating the 99 percent disk usage pattern.

Common BITS Job Types That Cause Disk Spikes

Windows Update jobs are the most frequent cause. A single failed or incomplete update can generate multiple BITS jobs that remain in the queue. Microsoft Store application updates also create BITS jobs. Third-party backup software and system management tools may use BITS for file transfers. In each case, the common factor is a job that cannot complete but is not automatically removed from the queue.

Steps to Identify and Stop BITS Jobs That Cause High Disk Usage

Method 1: List All BITS Jobs Using Command Prompt

1. Open Command Prompt as administrator
   Press the Windows key, type cmd, right-click Command Prompt, and select Run as administrator. Click Yes in the User Account Control dialog.
2. List all BITS jobs
   Type bitsadmin /list /allusers and press Enter. The command displays a table showing each job ID, display name, transfer type, job state, and the number of bytes transferred and remaining.
3. Identify stuck or large jobs
   Look for jobs in the TRANSFERRING or QUEUED state that have a large number of bytes remaining. Jobs in the TRANSIENT_ERROR state indicate a temporary failure that BITS will retry.
4. Cancel a specific job
   Type bitsadmin /cancel {job_id} and press Enter. Replace {job_id} with the GUID shown in the list. Confirm by checking that the job no longer appears in the list.

Method 2: Temporarily Stop the BITS Service

1. Open Services console
   Press Windows key + R, type services.msc, and press Enter.
2. Locate Background Intelligent Transfer Service
   Scroll down the list and double-click Background Intelligent Transfer Service.
3. Stop the service
   Click the Stop button. The service status changes to Stopped. Disk usage should drop immediately in Task Manager.
4. Restart the service after cleanup
   After you cancel or complete the problematic jobs, right-click the service and select Start to resume normal BITS operation.

Method 3: Clear the BITS Queue Using PowerShell

1. Open PowerShell as administrator
   Press Windows key, type PowerShell, right-click Windows PowerShell, and select Run as administrator.
2. Get all BITS jobs
   Type Get-BitsTransfer | Format-List and press Enter. This lists all active BITS jobs with detailed properties.
3. Cancel all jobs
   Type Get-BitsTransfer | Remove-BitsTransfer and press Enter. Confirm the action by typing Y and pressing Enter. This removes all jobs from the queue.
4. Verify the queue is empty
   Type Get-BitsTransfer and press Enter. No output means the queue is empty. Check Task Manager to confirm disk usage has returned to normal.

If BITS Still Shows High Disk Usage After Cleaning the Queue

BITS Service Fails to Stop or Start

If the service does not stop in Services console, open Command Prompt as administrator and type net stop bits. If the command returns an error, run taskkill /f /im svchost.exe but note this may affect other services running in the same host process. A safer approach is to restart the system, then immediately stop BITS before other jobs are queued.

BITS Queue Rebuilds Immediately After Clearing

If Windows Update or Microsoft Store recreates BITS jobs seconds after you cancel them, the underlying application is actively queuing new jobs. Run Windows Update troubleshooter by going to Settings > System > Troubleshoot > Other troubleshooters > Windows Update. This tool resets the update components and clears the BITS queue. After the troubleshooter completes, restart the system and check BITS disk usage.

BITS Uses 99 Percent Disk on an SSD

SSDs handle random I/O much better than HDDs, but a BITS job that repeatedly writes to the same cache folder can still show high disk usage in Task Manager. The percentage reflects the service active time, not the actual data transfer rate. If disk usage stays at 99 percent for more than 10 minutes, follow the cleanup steps above. The cache folder may also contain corrupted temporary files. Delete all contents of C:\ProgramData\Microsoft\Network\Downloader after stopping the BITS service. Restart the service to recreate the folder structure.

BITS Idle Disk Usage vs Windows Update Disk Usage

Item	BITS Idle Disk Usage	Windows Update Disk Usage
Primary cause	Queued or stuck transfer jobs	Downloading and installing update packages
Network activity	Low or none	High during download phase
Disk I/O pattern	Sustained random reads and writes to job metadata files	Sequential writes to download cache and system files
Duration	Minutes to hours depending on queue size	Minutes to hours depending on update size
Fix method	Cancel or complete BITS jobs	Run Windows Update troubleshooter or install updates manually

You can now identify and resolve BITS high disk usage on your Windows 11 system by listing active jobs, canceling stuck transfers, or temporarily stopping the service. For persistent issues, run the Windows Update troubleshooter to reset update components. As an advanced tip, configure BITS group policy settings to limit the maximum number of simultaneous jobs and reduce the retry interval to prevent queue buildup in the future.