Apps crash on Print — isolate bad package via PrintIsolationHost

Joe B.

Reviewed for technical accuracy

Specialities: Windows 11/10, Print Spooler, Print Driver Isolation, Office & Adobe apps, Enterprise print servers

App crashes on Print in Windows 10/Windows 11 — Word, Excel, Outlook, Adobe Acrobat/Reader, Edge/Chrome

Technician

Hey! We’ll stop your apps crashing on Print. Tell me which app fails — Word/Excel/Outlook, Adobe Acrobat/Reader, or Edge/Chrome — and the printer brand (HP, Canon, Kyocera, Brother, Ricoh, Lexmark, etc.). We’ll use Print Driver Isolation (PrintIsolationHost.exe) to sandbox the bad driver package, then repair or replace it.

Customer

Windows 11, Office 365 Word and Outlook. When I click Print the app freezes then closes. Event Viewer shows Event ID 1000, Faulting module: KERNELBASE.dll. We use Kyocera KX and an HP Universal PCL6 queue.

Technician

Got it. Application crashes when opening Print dialog usually mean a user‑mode Type 3 print driver is injecting a bad module into the app process. Symptoms: Word/Outlook/Acrobat crash, WER points at ntdll.dll / ucrtbase.dll / KERNELBASE.dll, and Print Spooler (spoolsv.exe) keeps running. Fix plan: isolate print drivers via PrintIsolationHost, find the faulting driver DLL from PrintService\Admin logs, then update or swap to a stable package (e.g., HP UPD PCL6/PS, Kyocera KX current, Canon UFR II, Ricoh PCL6, Brother PCL, Lexmark Universal). We can also force winprint processor and RAW data type to avoid EMF/XPS hooks.

Customer

How do I turn on Print Driver Isolation on Windows 11?

Technician

Enable Print Driver Isolation (PrintIsolationHost.exe):

1. Open Print Management (printmanagement.msc) → Drivers → right‑click each suspect driver → Set Driver Isolation → choose Isolated.
2. Or enforce via Group Policy: Computer Configuration → Administrative Templates → Printers → enable Execute print drivers in isolated processes = Enabled.
3. Restart the Print Spooler (services.msc) or run net stop spooler && net start spooler.

After this, the app calls the print UI but the driver code runs in PrintIsolationHost.exe, preventing Word/Acrobat from crashing even if the driver misbehaves.

Customer

Isolation helped. How do I identify which driver package is bad?

Technician

Locate the faulting driver DLL:

• Open Event Viewer → Applications and Services Logs → Microsoft → Windows → PrintService → Admin. Look for errors around the crash. Note the driver name, provider, and processor (PCL6/PS/XPS).
• In Windows Logs → Application, find Event ID 1000 (Application Error). The Faulting module often references a vendor DLL (e.g., KXUI.DLL, Hpcpp116.dll, CNLB0*.dll). That’s your culprit.
• Optional deep dive: capture a short ProcMon trace or WER dump to confirm.

Once identified, we either update to the latest stable package, roll back, or switch the queue to a Universal/Class driver that’s known‑good.

Customer

Which replacements are stable? Our fleet is mixed (HP, Kyocera, Canon, Ricoh, Brother, Lexmark).

Technician

Stable driver choices to stop print‑dialog crashes:

• HP: HP Universal Print Driver (PCL6 or PS). Prefer PS for PDFs/graphics; PCL6 for Office text. Avoid very old Type 3 packs.
• Kyocera: latest KX Driver. If KX UI causes issues, test Mini Driver (PCL) or PS.
• Canon: UFR II or Generic Plus UFR II. For legacy apps, PS3 often isolates best.
• Ricoh: current PCL6 or PS universal. Turn off Bidirectional if the UI hangs.
• Brother: Brother PCL or BR-Script (PS) package; disable add‑on Status Monitor.
• Lexmark: Universal v2/v3 PS/PCL; remove legacy print monitors if present.

Also set each queue to: Print Processor = winprint and Default Data Type = RAW (Printer Properties → Advanced). This bypasses flaky EMF/XPS filters.

Customer

Acrobat still crashes on one old Canon PS queue.

Technician

For Acrobat/Reader crashes on Print:

1. Update Acrobat, then enable Use system dialog and try the Adobe PDF/PostScript path.
2. Switch that Canon queue to UFR II or a clean PS3 package; remove any legacy print monitor.
3. In Printer Properties → Advanced, uncheck Enable advanced printing features (disables EMF spooling).
4. Test a fresh queue with Class (Type 4) driver if supported; Type 4 isolates better in Windows 10/11.

Customer

Do I need to reinstall the whole print subsystem?

Technician

Usually not. Do a targeted driver cleanup:

• Remove the crashing queue. In Print Management → All Drivers, delete the suspect package (check Driver is in use warnings).
• Clear temp spool files: %SystemRoot%\System32\spool\PRINTERS (stop Spooler first).
• Install the replacement driver; set Isolation = Isolated; default processor = winprint.
• Disable third‑party add‑ons (status monitors, port monitors) and test with a Standard TCP/IP Port.

Customer

Any tips for RDS/Terminal Server where multiple users crash?

Technician

On RDS/VDI, enforce isolation globally via GPO, disable Render print jobs on client computers, and restrict to a known‑good Universal PS/PCL. Avoid old Point and Print packages; use Type 4 where possible. Capture one user’s WER crash and fix the underlying driver; crashes will disappear for everyone.

Customer

Great — Word and Acrobat no longer crash. What’s the final checklist?

Technician

Summary checklist to fix “apps crash on Print”: Isolate drivers (PrintIsolationHost) → Check PrintService\Admin & Event ID 1000 for faulting module → Replace/update the bad print driver (HP UPD, Kyocera KX, Canon UFR II, Ricoh PCL6, Brother/Lexmark Universal) → Force winprint + RAW → Disable advanced features/monitors → Clean the spool folder → Test again. Need help? Open the chat.

Quick answer: the accepted fix

Accepted fix when apps crash on Print (Windows 10/Windows 11): Enable Print Driver Isolation so drivers run in PrintIsolationHost.exe, identify the faulting driver DLL from Event Viewer, then update/replace the driver (HP/Kyocera/Canon/Ricoh/Brother/Lexmark). Set Print Processor = winprint, Data type = RAW, and disable third‑party print monitors.

FAQ

Step‑by‑step (Windows 10/11)

1. Open Print Management → Drivers → set each vendor driver to Isolated.
2. Restart the Print Spooler and clear the PRINTERS spool folder (service stopped).
3. Replace crashing packages with Universal PS/PCL (HP UPD, Kyocera KX, Canon UFR II, Ricoh PCL6, Brother/Lexmark Universal).
4. Printer Properties → Advanced: Processor = winprint; Data type = RAW; uncheck Enable advanced printing features.

Step‑by‑step (macOS)

1. macOS crashes are rarer; rebuild the queue with the latest vendor driver or AirPrint.
2. Disable third‑party status plugins; test with a generic PostScript queue.
3. If only PDFs fail, print via system dialog and export as image to validate the printer path.

Sources

• Microsoft — Introduction to Print Driver Isolation
• Microsoft — Printer management on Windows
• Adobe — Troubleshoot PDF printing

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.