Microsoft recently released Edge Version 154.0.4258.37, and this update introduced a browser bug that prevents many virtual PDF printers—including Win2PDF, Microsoft Print to PDF, and Adobe PDF—from working correctly.
What’s Happening
When printing from Edge 154 using the Windows system print dialog, the job never reaches the PDF printer. Physical printers still work, and Edge’s built‑in Save as PDF option continues to function, but any virtual printer fails before the print job is sent. To the user, the browser closes and no file save window is presented.
Microsoft has confirmed the problem and listed it as a known issue. Their internal logs show a JavaScript error inside Edge’s print pipeline, meaning the failure occurs within Edge itself, not in Win2PDF or other PDF printer drivers.
Who Is Affected
This issue impacts anyone using Edge 154 to create PDFs through a virtual printer. Win2PDF continues to work normally in:
- Edge 153 and earlier
- Chrome and Firefox
- All Windows desktop applications
Only Edge 154’s updated printing code is affected.
Workarounds
Microsoft recommends the following temporary solutions:
- Roll back to Edge Version 153
- Use Internet Explorer Mode for pages that support it
- Use Win2PDF’s Auto-name feature which bypasses the Win2PDF file save window
- Use Chrome, Firefox, or other non-Edge web browser
Status
Microsoft has acknowledged the regression and is working on a fix. We will update our customers as soon as a corrected Edge build is released.
