Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Caută ajutor

Atenție la excrocheriile de asistență. Noi nu îți vom cere niciodată să suni sau să trimiți vreun SMS la vreun număr de telefon sau să dai informații personale. Te rugăm să raportezi activitățile suspecte folosind opțiunea „Raportează un abuz”.

Află mai multe

Firul de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Duplex printing not available on default Firefox profile

user297409699465247449685822672927256813163
user297409699465247449685822672927256813163
mai multe opțiuni

When printing from Firefox I do not have duplex printing available. I found the following answer, https://support.mozilla.org/bm/questions/1132257, which suggests creating a new profile. This does work, but I do not want to lose my profile settings as I am syncing across four computers. Is there anything another without resetting Firefox?

Firefox version: 93.0 (64-bit) Windows version: Windows 10 Pro 21H1 Printer: Brother HL-L8260CDW

When printing from Firefox I do not have duplex printing available. I found the following answer, https://support.mozilla.org/bm/questions/1132257, which suggests creating a new profile. This does work, but I do not want to lose my profile settings as I am syncing across four computers. Is there anything another without resetting Firefox? Firefox version: 93.0 (64-bit) Windows version: Windows 10 Pro 21H1 Printer: Brother HL-L8260CDW

Toate răspunsurile (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 25 Contributor
mai multe opțiuni

Hi, the problem is that the "Two-sided printing" section under "More settings" is missing?

Does it make any difference if you switch between your regular printer and the built-in Save to PDF printer and then back again? (The goal is to get Firefox to re-read the printer settings and update the More settings panel.)

By the way, due to changes in printing during the past 12 months, I wouldn't rely on a 2016 thread to be accurate for current versions of Firefox. Let's ignore that old advice.