PrintDialog.exe

Windows ProcessMicrosoft Corporation

Also called printdialog, print dialog, modern print dialog

WindowsSystem Component

Modern print dialog host. It is the print UI Windows apps open, not the Print Spooler and not the isolation host.

What you need to know

This is the print dialog UI.

PrintDialog.exe hosts the modern print dialog. Choosing a printer and options happens here. Jobs that were already submitted live in spoolsv.exe. PrintIsolationHost.exe is driver isolation. Closing the dialog does not uninstall a printer.

Safe?: Yes. It is the print dialog UI
Does it hold the queue?: No. spoolsv does
Can I end it?: The dialog closes

Feex says

If PrintDialog is stuck on screen, I end this UI host. I do not stop the Print Spooler unless the job is already in the queue and wedged.

What is PrintDialog.exe?

PrintDialog.exe is the print dialog UI. It is the modern printer picker, not the spooler. spoolsv.exe still owns the queue after you click Print.

What does it do?

It lists printers, options, and preview for apps that use the modern dialog. It does not isolate drivers (PrintIsolationHost) and it does not thunk 32-bit apps (splwow64).

Why is it running?

An app called Print. The dialog stays until you print, cancel, or the host hangs. A dialog with no app in front is a leftover UI, not a second spooler.

Is it safe?

Usually safe

The Microsoft print dialog is System32 or a Print Dialog system app. A PrintDialog.exe in Downloads is not the Windows picker. This is still UI, not spoolsv.

A legitimate copy normally runs from:

C:\Windows\System32\PrintDialog.exe

Print dialog UI only
Queue host: spoolsv.exe
Some builds also host a Print Dialog package

Can I end it?

Closes the dialog

Ending PrintDialog.exe is Cancel on that window. Jobs already handed to the spooler stay in spoolsv.exe. Isolation hosts are not this process.

Can I remove it?

Do not delete PrintDialog.exe. You would break the modern print UI. Removing a printer is Settings or Print Management, not an Explorer delete of this host.

Should it start with Windows?

An app starts it when you print. It should not sit in Startup Apps.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Low unless preview or printer discovery is stuck
Memory: Moderate for a UI host
Disk: Low
Network: Printer discovery can wake DAF and network printers

File information

PrintDialog.exe file information
Executable name	PrintDialog.exe
Common legitimate path	C:\Windows\System32\PrintDialog.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

Dialog empty, classic Print from Notepad works

This UI failed to enumerate. The spooler can still be healthy. Restart the dialog host, then look at printer connections.

People stop Spooler to close a hung dialog

End PrintDialog.exe first. Stopping spoolsv drops every queue on the PC.

Troubleshooting

Diagnose before you change anything destructive.

Close the dialog host, then print from Notepad as a control

If Notepad's older dialog works, the queue is fine and this UI is the broken piece.

Check printer discovery separately

A spinning modern dialog can keep dasHost busy. That is discovery, not proof the spooler died.

Technical details

PrintDialog.exe technical details
Image name	PrintDialog.exe
Role	Modern print dialog host

Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.

Microsoft Learn: print from your app · Apps open a print dialog, then the spooler takes the job
Microsoft Learn: Print Spooler · spoolsv is the spooler, not the dialog
Foxhole process map · 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.