[BUG] Claude Desktop – Black Screen After Canceling PDF Save Printer Dialog
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When creating a Markdown (.md) file in Claude Desktop and using "Save as PDF," the app triggers a printer connection dialog instead of a standard PDF save dialog. Canceling this dialog causes the app to crash into a persistent black screen that does not resolve even after reopening the app. The issue self-resolves after approximately one hour.
No file is downloaded
The app goes to a black screen
The black screen persists even after closing and reopening the app
The issue resolves on its own after approximately one hour
What Should Happen?
Either save a PDF file directly, or display an error message. The app should remain functional.
Error Messages/Logs
Steps to Reproduce
- Create a Markdown (.md) file using Claude Desktop
- Click "Save as PDF"
- A print preview opens
- The app attempts to connect to a printer
- When no printer is available / connection fails, the print preview closes and Claude returns a blank screen
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
-
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
The "Save as PDF" feature routes through the OS print system rather than a direct PDF export path. A print preview opens first, but when the printer connection fails, the preview does not close or recover gracefully — instead the entire app renderer freezes into a persistent black screen. The expected behavior would be either a working "Save as PDF" destination in the print dialog (no physical printer needed), or a direct PDF export that bypasses the print system entirely.
This does not appear to match any currently known reported bug (checked GitHub issues on anthropics/claude-code as of May 2026).
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗