Opening and reading PDF files in Microsoft Edge on Windows 11
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have a problem with printing from the latest version of Microsoft Edge. When I select some text on the browser and choose Print → 'Save As Pdf', the download starts but never finishes. How can I fix this? Is this a common issue for all the users of the latest version of Edge?
I have tried restating the PC, Resetting the browser, stopping all the extension etc. to fix it. but it doesn't work? Should I switch to Chrome?
Opening and reading PDF files in Microsoft Edge on Windows 11
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Same problem! Please solve this problem ASAP!
I am having the same issue for the past 3 days. I saw among the comments here that another option is to choose Microsoft Print to PDF. And it works. But what really happened with Save to PDF option? It works in other browsers but not in Edge.
Yes, Microsoft Print to PDF works (for now) but the PDF you get is not editable. It is what looks like an assembly of images. If you do not care to make minor edits to the PDF or just to simply highlight text and copy it to paste elsewhere, then it's OK.
As best as I can tell Save to PDF stopped working when Edge was updated from v119.x to v120.x.
I found if I use Firefox, I can generate .pdf files. I will stop using Edge until they get around to fixing this issue. I wonder what we all have in common regarding our computer system that we are susceptible to this issue. My computer happens to be 11 years old and will not be compatible with Windows 11.
If you have the option of using Microsoft Print to PDF in your printer list you can get around this bug till they fix it. If you need OCR type functionality however, this won't do it for you. Use Chrome of Firefox if this is the case.
This is happening to me as well and it appears to have started with the latest update.
I am also running Version 120.0.2210.61 (Official build) (64-bit), on Windows 10 Pro.