{"version":"2.1.277","anchor":"pdf-page-render-pdftoppm-hardened-for-windows-unc-paths-an","canonical_anchor":"pdf-page-render-pdftoppm-hardened-for-windows-unc-paths-an","heading":"PDF page render (pdftoppm) hardened for Windows UNC paths and clearer errors","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/pdf-page-render-pdftoppm-hardened-for-windows-unc-paths-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### PDF page render (pdftoppm) hardened for Windows UNC paths and clearer errors\n\nPDF-to-image rendering now cleans up error messages, including Windows network path prefixes, and handles a new move-failure case\n\n**What**\n\nWhen Claude Code converts a PDF page to an image (using the `pdftoppm` tool, part of reading PDF files), it now cleans up the error text before showing it to you:\n\n- Temp-file paths embedded in the underlying tool's error output are replaced with the original filename, so errors reference the file you actually gave it\n\n- Windows extended-length and UNC path prefixes (`\\\\?\\UNC\\`, `\\\\?\\`) are stripped out of error text\n\n- A distinct error is now reported if moving the rendered page images into the output folder fails\n\n**Why**\n\nThis makes PDF rendering failures easier to understand, especially on Windows, where raw error text could otherwise show confusing internal path syntax instead of your file's name.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}