# backgroundTransferHost.exe

Windows Process: Microsoft Corporation

Also called backgroundtransferhost, background transfer host, bits host

Windows, System Component

Background Transfer API host. Store and some apps use it for BITS-style transfers. It is not the Delivery Optimization service.

## What you need to know

Background Transfer API host.

backgroundTransferHost.exe hosts Windows.Networking.BackgroundTransfer work for Store and some desktop apps. Delivery Optimization (DoSvc) is a separate peering service for Windows Update and Store packages. Ending this host cancels those Background Transfer jobs, not DoSvc peering.

- **Safe?**: Yes, during a transfer

  **Same as Delivery Optimization?**: No. DoSvc is a different service

  **Should I end it?**: That download can fail

Feex says

If I see backgroundTransferHost while the Store is downloading, I wait on that transfer. I do not disable Delivery Optimization to stop this host.

## What is backgroundTransferHost.exe?

backgroundTransferHost.exe is the Background Transfer API host. Apps and Store use it for uploads and downloads that can continue in the background. It is not the Delivery Optimization service.

## What does it do?

It runs BackgroundDownloader / BackgroundUploader jobs. BITS-style transfers for those APIs land here. Windows Update peering and LAN sharing are DoSvc, a different stack.

## Why is it running?

Microsoft Store, a UWP app, or another client started a background transfer. The host should exit when jobs complete. A forever copy with no Store activity is the case to inspect.

## Is it safe?

Usually safe

System32 backgroundTransferHost.exe is Microsoft. A host in a downloader zip is not. This is still the Background Transfer API, not Delivery Optimization.

A legitimate copy normally runs from:

`C:\Windows\System32\backgroundTransferHost.exe`

- Background Transfer API host
- Delivery Optimization is DoSvc, not this image
- Store downloads are a common starter

## Can I end it?

Those jobs fail

Ending backgroundTransferHost.exe cancels Background Transfer jobs in that host. DoSvc can keep peering. Pause the Store download if you meant to stop a purchase, not this End task alone.

## Can I remove it?

No

Do not delete backgroundTransferHost.exe. Store and app background downloads would break. Delivery Optimization settings do not remove this host.

## Should it start with Windows?

A transfer starts it. It is not a Startup Apps checkbox.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: Low to moderate while a job runs

  **Memory**: Small

  **Disk**: Writes the download payload

  **Network**: The transfer itself

## File information

| Executable name        | backgroundTransferHost.exe                     |
| ---------------------- | ---------------------------------------------- |
| Common legitimate path | C:\Windows\System32\backgroundTransferHost.exe |
| Publisher              | Microsoft Corporation                          |
| Signature expectation  | Signed by Microsoft Windows                    |

## Common problems

### People disable DoSvc to stop this host

Delivery Optimization is peering for Update and Store packages. This process is the Background Transfer API. Two knobs.

### Stuck at 0% in Store

Check this host and the Store app, then DoSvc if the package uses Delivery Optimization. Ending only DoSvc may leave API jobs running.

## Troubleshooting

Diagnose before you change anything destructive.

### Pause or cancel the Store / app download first

Settings > Apps or the Store downloads page. If the host exits, you found the job. That is not a DoSvc restart.

### Split DoSvc in Resource Monitor

Delivery Optimization has its own service and cache folder. backgroundTransferHost.exe will not be that svchost group.

## Technical details

Technical details

| Image name | backgroundTransferHost.exe   |
| ---------- | ---------------------------- |
| Role       | Background Transfer API host |

## Related

These entities connect to this article. Type is shown on every link.

[Delivery Optimization: Windows Service](https://feex.it/wiki/service/delivery-optimization)[MoUsoCoreWorker.exe: Windows Process](https://feex.it/wiki/process/mousocoreworker.exe)[Process vs service: Guide](https://feex.it/wiki/software/system/process-vs-service)

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we research](https://feex.it/wiki/research).

- [Microsoft Learn: background transfers ](https://learn.microsoft.com/windows/uwp/networking/background-transfers)· Background Transfer API host for apps and Store
- [Microsoft Learn: Delivery Optimization ](https://learn.microsoft.com/windows/deployment/do/waas-delivery-optimization)· DoSvc is a different download path
- [Foxhole process map ](https://foxhole.feex.it/)· First-party samples on Windows PCs. Not a lab benchmark.

## Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Type**: Windows Process

  **Publisher**: Microsoft Corporation

  **Executable**: backgroundTransferHost.exe

  **Typical path**: C:\Windows\System32\backgroundTransferHost.exe

  **Mapped by Feex**: Seen on Windows PCs in Foxhole

  **Related service**: [Delivery Optimization](https://feex.it/wiki/service/delivery-optimization)

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/process/backgroundtransferhost.exe/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)