# CompPkgSrv.exe

Windows Process: Microsoft Corporation

Also called comppkgsrv, component package support server

Windows, System Component

Component Package Support Server. It stages optional and on-demand Windows component packages. TrustedInstaller / TiWorker apply the component store (CBS).

## What you need to know

CompPkgSrv stages optional component packages, not TrustedInstaller applying CBS.

CompPkgSrv.exe is Component Package Support Server. Optional features, Features on Demand, and some app-triggered packages go through this worker. TrustedInstaller.exe and TiWorker.exe still apply the component store. Ending CompPkgSrv does not roll back a CBS apply that already started.

- **Safe?**: Yes, in System32

  **Is it TrustedInstaller?**: No. This stages optional packages

  **Should I end it?**: An optional feature can fail

Feex says

If CompPkgSrv is busy after I added an optional feature, I let it stage. I do not kill TrustedInstaller to stop a FOD.

## What is CompPkgSrv.exe?

CompPkgSrv.exe stages optional component packages. It is Component Package Support Server, not TrustedInstaller.exe applying CBS. TiWorker.exe still does the heavy component-store file work.

## What does it do?

It prepares on-demand packages apps and Optional features request. It does not own the TrustedInstaller service. A quality update apply spike is more often TiWorker.

## Why is it running?

You added an optional feature, an app asked for a capability (.NET, a media pack, a language FOD), or Windows pre-staged a package. Idle CompPkgSrv after that work should exit.

## Is it safe?

Usually safe

System32 CompPkgSrv.exe is Microsoft. A CompPkgSrv.exe in a "debloat" zip is not. This file still does not replace TrustedInstaller as the CBS applier.

A legitimate copy normally runs from:

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

- Optional / on-demand package worker
- CBS apply: TrustedInstaller.exe and TiWorker.exe
- Expected publisher: Microsoft Corporation

## Can I end it?

That package can fail

Ending CompPkgSrv.exe can fail the optional package it was staging. It does not stop TrustedInstaller mid-CBS the way ending TiWorker can. Wait if Optional features shows progress.

## Can I remove it?

No

Do not delete CompPkgSrv.exe. Remove an optional feature from Settings if you do not want that package. Do not delete TrustedInstaller to "debloat" this host.

## Should it start with Windows?

An optional feature or an app capability starts it. It is not a Startup Apps row.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: Rises while a capability stages

  **Memory**: Moderate

  **Disk**: Package payload. CBS apply disk is often TiWorker

  **Network**: Windows Update if the FOD is not local

## File information

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

## Common problems

### People blame TrustedInstaller for every package name

Optional features and FODs often wake CompPkgSrv first. CBS apply is the later TrustedInstaller / TiWorker phase.

### Debloat scripts delete this exe

Later Optional features and some Store apps then fail in a confusing way. Restore the system file. Do not copy a random replacement.

## Troubleshooting

Diagnose before you change anything destructive.

### Settings > System > Optional features

If a feature is installing, this worker is expected. Cancel or finish that item. Do not end TrustedInstaller as the first click.

### Split staging from CBS apply

TiWorker plus TrustedInstaller in WinSxS is apply. CompPkgSrv in System32 is the package support server. Match the path before you run DISM.

## Technical details

Technical details

| Image name | CompPkgSrv.exe                   |
| ---------- | -------------------------------- |
| Role       | Component Package Support Server |

## Related

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

[TrustedInstaller.exe: Windows Process](https://feex.it/wiki/process/trustedinstaller.exe)[TiWorker.exe: Windows Process](https://feex.it/wiki/process/tiworker.exe)[MoUsoCoreWorker.exe: Windows Process](https://feex.it/wiki/process/mousocoreworker.exe)

## Sources and verification

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

- [Microsoft Learn: Features on Demand ](https://learn.microsoft.com/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities)· Optional Windows component packages
- [Microsoft Learn: Windows ](https://learn.microsoft.com/windows)· Primary Windows documentation
- [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**: CompPkgSrv.exe

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

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

  **Related process**: [TrustedInstaller.exe](https://feex.it/wiki/process/trustedinstaller.exe)

Feex Reviewed: Last verified August 2026

---

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

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