Microsoft Print to PDF outputs blank — GDI sandbox reset (Windows 10/11)
Updated: · Answered by Joe B. in 4 mins
Joe B.
Reviewed for technical accuracy
Specialities: Windows 10/11 printing, Microsoft Print to PDF, Print Spooler, GDI/EMF to XPS pipeline, Driver Isolation
Microsoft Print to PDF blank/empty file — reset GDI printer sandbox, driver isolation, spooler & feature reinstall
Technician
Hey! We’ll fix **Microsoft Print to PDF** generating **blank pages/0-KB PDFs**. Quick triage:
• Windows version (Windows 10 or Windows 11 22H2/23H2/24H2)? Any recent **KB update** installed before this started?
• Does printing to **Microsoft XPS Document Writer** or a real printer work?
• Symptoms: PDF opens but shows white pages, file size 0–5 KB, or Edge/Chrome print preview looks fine but output is empty?
• Environment: local PC or **RDS/Remote Desktop**? Third-party PDF printers installed (Adobe PDF, CutePDF)?
We’ll reset the **GDI → EMF/XPS** pipeline, check **GDI printer sandbox/driver isolation**, and reinstall the **Windows Feature** if needed.
Customer
Windows 11 23H2. “Microsoft Print to PDF” creates **empty PDFs** from any app — Word, Chrome, even Notepad. XPS Document Writer works. This started after a cumulative update last week.
Technician
Thanks — classic **Print to PDF blank output** pattern. In Windows, apps render via **GDI**; the spooler converts (**EMF→XPS→PDF**). After some updates or policy changes, **driver isolation/GDI sandbox** and the PDF feature can desync. Result: jobs “complete” but the **spool file** never writes valid pages → you get **blank/0-KB** PDFs.
Fix plan: 1) Reset spooler queue. 2) Toggle **Microsoft Print to PDF** feature off/on. 3) Switch **Driver Isolation** mode (aka GDI sandbox reset). 4) Force jobs to **spool then print**. 5) Test from multiple apps and repair the pipeline if needed (DISM/SFC).
Customer
Let’s do it. I have admin access. What’s first?
Technician
Step 1 — Clear the Print Spooler (safe reset)
1) Press Win+R → type services.msc → Enter → right-click Print Spooler → **Stop**.
2) Open %windir%\System32\spool\PRINTERS and delete files inside (these are stuck jobs).
3) Back in Services → **Start** the Print Spooler.
4) Try printing to **Microsoft Print to PDF** again from Notepad. If still blank, proceed.
Customer
Still blank PDFs.
Technician
Step 2 — Reinstall the Windows Feature (repairs the PDF virtual driver)
1) Press Win → search **Turn Windows features on or off**.
2) Uncheck Microsoft Print to PDF → OK → restart.
3) Open Windows Features again → check Microsoft Print to PDF → OK → restart.
4) In Settings → Bluetooth & devices → Printers & scanners → Microsoft Print to PDF → Printer properties → Advanced:
• Tick **Start printing after last page is spooled** and **Keep printed documents** (helps the pipeline).
• Untick **Enable advanced printing features** if present (bypasses problematic EMF features).
Test again from Notepad and Chrome.
Customer
After reinstall, the print dialog works but the PDF is still empty from Chrome and Word. XPS still fine.
Technician
Step 3 — Reset the GDI printer sandbox (Driver Isolation)
Windows can run print drivers in isolated processes (aka **Driver Isolation / GDI sandbox**) to protect the spooler. Sometimes isolation state breaks PDF rendering.
• Open Print Management (printmanagement.msc) → **Printers** → right-click Microsoft Print to PDF → **Properties** → **Advanced** → set **Driver Isolation** to **Shared** (or **Isolated** if already Shared), Apply → test again.
• If you manage via policy: **Local Group Policy Editor** → Computer Configuration → Administrative Templates → Printers → set **Override print driver execution compatibility** to **Enabled** to force isolation mode consistently. Reboot and retest.
This toggling effectively “resets” the sandbox boundary for the PDF driver.
Customer
Switching Driver Isolation from Shared → Isolated, rebooted — now Notepad and Word export fine, but Chrome still creates a 0-KB file.
Technician
Step 4 — Test multiple render paths & clear app cache
• In Chrome/Edge, try **Ctrl+P → More settings → Use system dialog (Ctrl+Shift+P)** → pick **Microsoft Print to PDF**. This uses the Windows print pipeline, not the browser’s internal renderer.
• Try **Save as PDF** vs **Microsoft Print to PDF** — if Save as PDF works, GDI path was at fault.
• Clear browser cache and update to the latest build; relaunch with --disable-extensions if needed.
• If PDFs from browsers only are blank, print the same page from **WordPad/Notepad** to confirm system GDI works. We can leave a browser-specific workaround and keep system PDFs working.
Customer
System dialog works. PDFs generate with content now. Any steps to make this stick after updates?
Technician
Step 5 — Make it durable
• Keep **Driver Isolation** at the stable setting that worked (Shared or Isolated). If you’re on a domain, apply the **Printers** policy above so updates won’t flip it.
• In Printer properties → **Advanced**: leave **Start printing after last page is spooled** and **Keep printed documents** on for a few days (you can turn them off later).
• Run integrity repair: open elevated CMD → DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
• If the issue returned right after a specific **KB**, check **Settings → Windows Update → Update history** and install the latest optional quality update that mentions **Print to PDF** reliability.
Customer
What about RDS/Remote Desktop? Our users on a session host also reported empty PDFs.
Technician
On **RDS/Server**, Print to PDF can fail if isolation or spooling mode is inconsistent across user sessions.
• On the host, set **Driver Isolation** consistently and ensure **Start printing after last page is spooled** is enabled for the PDF queue.
• Clear each user’s temp spool remnants (%temp%) and purge C:\Windows\System32\spool\PRINTERS (as admin).
• If recent updates broke it, install the latest cumulative or temporarily roll back the problematic KB, then reapply once Microsoft publishes a fix. Test from **Notepad** in a clean session.
Customer
Great — PDFs have content again from all apps via system dialog. Thanks!
Technician
Summary: When Microsoft Print to PDF outputs blank, reset the spooler, reinstall the **Microsoft Print to PDF** feature, and **toggle Driver Isolation (GDI sandbox)** for the PDF queue. Set **Start printing after last page is spooled**, optionally disable **Advanced printing features**, and test via the **system print dialog**. Need help applying the **Printers** group policy or RDS settings? Open the chat.
Quick answer: the accepted fix
Accepted fix for Microsoft Print to PDF blank pages: clear the Print Spooler queue, turn off/on the Windows feature Microsoft Print to PDF, then reset the GDI printer sandbox/Driver Isolation (Shared ↔ Isolated), and set **Start printing after last page is spooled**. If browsers still output empty PDFs, print via the **system dialog** (Ctrl+Shift+P) or update the affected app.
Why Print to PDF goes blank (GDI/EMF, isolation & updates)
GDI rendering generates EMF/XPS data which the spooler converts to PDF. If the **driver isolation (GDI sandbox)** process or feature binaries desynchronize after a **Windows Update (22H2/23H2/24H2)**, the pipeline can write an empty job. Toggling isolation, reinstalling the feature, and forcing spool-then-print usually restores the EMF→PDF conversion. On **RDS/Remote Desktop**, apply the same isolation mode for all sessions.
How to verify the fix (Notepad, system dialog, file size)
Print a one-page Notepad file. In **Printer properties → Advanced**, verify **Start printing after last page is spooled**. Use the **system print dialog** from Chrome/Edge. A healthy output is a PDF larger than 20 KB with selectable text. If you still get a **0-KB** file or white pages, run DISM /Online /Cleanup-Image /RestoreHealth followed by sfc /scannow, then reinstall the feature again.
Blank PDF — quick troubleshooting checklist
Covers Windows 10/11, Workstation & RDS (session hosts).
• Clear Print Spooler and stuck EMF files → reinstall **Microsoft Print to PDF** feature.
• Toggle **Driver Isolation (GDI sandbox)**: Shared ↔ Isolated; enforce via **Printers** policy if needed.
• In Advanced tab, enable **Start printing after last page is spooled** and **Keep printed documents**; disable **Advanced printing features** temporarily.
• Test **XPS Document Writer** and **system print dialog**; update browser/Office; apply latest optional quality update if a recent KB caused it.
Disclaimer: This information is AI-generated and intended for general guidance only. For advice specific to your environment, please consult a verified expert on Whizz-Tech before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including tech support, mechanics, vets, and more.
Expert will respond in minutes
We match you with an Expert who specializes in your situation. Talk, text, or chat — whichever you prefer.
Save time & money
No scheduling hassles or expensive consults. Membership can save you significant time and money each month.
FAQ
Why does Microsoft Print to PDF create blank or 0-KB files?
Corrupted spool files, a broken PDF feature install, or a mismatch in Driver Isolation (GDI sandbox) can stop EMF/XPS data from reaching the PDF writer. Reinstall the feature and toggle isolation to reset the pipeline.
How do I reset the GDI printer sandbox (Driver Isolation)?
Open Print Management → properties of Microsoft Print to PDF → Advanced → change Driver Isolation (Shared ↔ Isolated). In Group Policy: Computer Configuration → Administrative Templates → Printers, enable Override print driver execution compatibility to enforce isolation mode.
“Save as PDF” works, but “Microsoft Print to PDF” is blank — why?
“Save as PDF” uses the app’s renderer; “Microsoft Print to PDF” uses the Windows GDI/Spooler path. If the GDI path is affected, print via the **system dialog** (Ctrl+Shift+P) or repair the feature and isolation settings.