This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Firefox 57.0.2 hangs (Not Responding) when trying to print

  • 1 reply
  • 3 have this problem
  • 11 views
  • Last reply by WoofGrrrr

WoofGrrrr
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.

Chosen solution

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

Read this answer in context 👍 0

All Replies (1)

WoofGrrrr
WoofGrrrr Question owner
more options

Chosen Solution

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