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

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Firefox 57.0.2 hangs (Not Responding) when trying to print

  • 1 èsì
  • 3 ní àwọn ìṣòro yìí
  • 12 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ WoofGrrrr

more options

When I try to print a page from Firefox 57.0.2 (64-bit on Windows 10,) after selecting the printer and clicking "Print", I get a dialog that says "preparing..." and then nothing happens. Firefox hangs. Windows 10 says that the app is Not Responding". I have to manually exit. If I look at the print queue, the status is "spooling".

This just started happening today. I have had 57.0.2 since it was first offered. The print driver has had no recent update. It is an Epson Workforce WF-3620.

I have tried using FF Safe Mode. Same problem.

I will re-install the printer driver to see if that fixes it.

When I try to print a page from Firefox 57.0.2 (64-bit on Windows 10,) after selecting the printer and clicking "Print", I get a dialog that says "preparing..." and then nothing happens. Firefox hangs. Windows 10 says that the app is Not Responding". I have to manually exit. If I look at the print queue, the status is "spooling". This just started happening today. I have had 57.0.2 since it was first offered. The print driver has had no recent update. It is an Epson Workforce WF-3620. I have tried using FF Safe Mode. Same problem. I will re-install the printer driver to see if that fixes it.

Ọ̀nà àbáyọ tí a yàn

I did re-install the driver and related software and that seems to have fixed the problem. Sorry for bothering you all.

Ka ìdáhùn ni ìṣètò kíkà 👍 0

All Replies (1)

more options

Ọ̀nà àbáyọ Tí a Yàn

I did re-install the driver and related software and that seems to have fixed the problem. Sorry for bothering you all.