# PrintIsolationHost.exe

Windows Process: Microsoft Corporation

Also called printisolationhost, print driver isolation, print sandbox

Windows, System Component

Print driver isolation host. Isolated print drivers run here so a crash does not take down spoolsv.exe. It is not the Print Spooler itself.

## What you need to know

Isolation host for print drivers, not spoolsv itself.

PrintIsolationHost.exe is the sandbox Windows starts when a print driver runs isolated from the spooler. spoolsv.exe keeps the service and the queue. A host crash should leave the spooler up. splwow64.exe is the 32-bit thunk, a different isolation story.

- **Safe?**: Yes. It isolates print drivers

  **Is it the spooler?**: No. spoolsv is the spooler

  **Crash here?**: Isolation did its job

Feex says

If PrintIsolationHost dies while I print, I remove that vendor driver. I do not disable the Print Spooler first, because the point of this host is that spoolsv can survive.

## What is PrintIsolationHost.exe?

PrintIsolationHost.exe is the isolation host for print drivers. Shared or isolated mode loads driver code here so a fault does not halt spoolsv.exe. It is not the spooler itself.

## What does it do?

It hosts print processors and driver modules the spooler proxies to. The queue folder and the Spooler service remain in spoolsv.exe. The modern print dialog is PrintDialog.exe.

## Why is it running?

You printed, or a driver in isolated or shared mode initialized. Full isolation can start another host per driver. No print activity should let the host exit.

## Why are there multiple copies?

Shared isolation can keep one host. Full isolation can start another host per driver. None of those hosts is spoolsv.exe.

## Is it safe?

Usually safe

System32 PrintIsolationHost.exe is Microsoft isolation. A host in a driver "cleaner" folder is not. A crash here is often the vendor driver, not proof the spooler is malware.

A legitimate copy normally runs from:

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

- Started for isolated or shared driver mode
- Spooler remains spoolsv.exe
- 32-bit thunk is splwow64.exe

## Can I end it?

That isolated driver unloads

Ending PrintIsolationHost.exe drops the sandboxed driver. The spooler service can stay up. That is the opposite of ending spoolsv.exe, which kills the whole queue.

## Can I remove it?

No

Do not delete PrintIsolationHost.exe. Remove the bad print driver from Print Management or Settings. Deleting spoolsv.exe is also wrong.

## Should it start with Windows?

The spooler starts isolation hosts when a job needs an isolated driver. Not Startup Apps.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: Follows the isolated driver while it renders

  **Memory**: Per sandbox. Full isolation costs more hosts

  **Disk**: Spool files still go through the spooler directory

  **Network**: Follows the printer port

## File information

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

## Common problems

### Host crashes, Notepad can still see the printer

Isolation worked. spoolsv survived. Replace the driver. Do not "repair" by replacing this exe.

### People set isolation to None to hide the host

That loads the driver back into spoolsv. A later crash then takes the whole spooler. Use isolation to find the bad driver, then remove it.

## Troubleshooting

Diagnose before you change anything destructive.

### Print Management: isolate, then remove the suspect driver

The driver that dies with this host is the one to replace with a Type 4 or IPP driver. spoolsv staying up is the success signal.

### Do not clear PRINTERS as the first step for a host crash

Empty queues with a crashing host mean the driver sandbox failed, not a leftover SPL file. Fix the driver, then clear jobs if they are actually stuck.

## Technical details

Technical details

| Image name | PrintIsolationHost.exe      |
| ---------- | --------------------------- |
| Role       | Print driver isolation host |

## Related

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

[spoolsv.exe: Windows Process](https://feex.it/wiki/process/spoolsv.exe)[splwow64.exe: Windows Process](https://feex.it/wiki/process/splwow64.exe)[Print Spooler: Windows Service](https://feex.it/wiki/service/print-spooler)

## Sources and verification

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

- [Microsoft Learn: printer driver isolation ](https://learn.microsoft.com/windows-hardware/drivers/print/printer-driver-isolation)· Isolated drivers run outside the spooler process
- [Microsoft Support: printer problems ](https://support.microsoft.com/windows/fix-printer-problems-in-windows)· Queue and service still belong to the spooler
- [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**: PrintIsolationHost.exe

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

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

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

Feex Reviewed: Last verified August 2026

---

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

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