Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

I am no longer able to print to a PDF file using Microsoft Print to PDF

  • 5 回覆
  • 1 有這個問題
  • 16 次檢視
  • 最近回覆由 annevw.aw

more options

I save many items and documents as PDF files using the Microsoft Print to PDF option, rather than physically printing on my printer. This worked fine for quite some time. This option no longer works when I am using Firefox, but it still works if I use Chrome.

I would rather not have to switch to Chrome whenever I want to print something to a PDF file.

How can I resolve this?

I save many items and documents as PDF files using the Microsoft Print to PDF option, rather than physically printing on my printer. This worked fine for quite some time. This option no longer works when I am using Firefox, but it still works if I use Chrome. I would rather not have to switch to Chrome whenever I want to print something to a PDF file. How can I resolve this?

所有回覆 (5)

more options

Post a screenshot of this issue. When you say "no longer works", what does that mean? Are you getting an error message?

more options

Basically, the option is disabled. That is evident as soon as I select Microsoft Print to PDF, and the options to print or apply are no longer enabled. Here's the screenshot. No error message.

more options

That's very strange. Can you report this to the developers at https://bugzilla.mozilla.org/ so that we can track this issue?

more options

Can you verify this? See screenshot

more options

I have verified that Microsoft Print to PDF is enabled (see screenshot), which makes sense, as it works from Chrome, just not Firefox.

I could try uninstalling and reinstalling Microsoft Print to PDF if that might help, but as it works in Chrome, I'm not sure that is the problem.