Waiting for printer connection

Anonymous
2023-12-14T05:51:25+00:00

“Waiting for printer connection” pop up started coming up a couple of weeks ago and has been causing multiple issues.

Excel and Word randomly do not open, and then when I open the program again it tells me the file is already in use yet nothing is open. Task manager shows nothing open or running. I have to restart my computer each time to use the document or workbook and I sometimes I need to do this more than once before it will decide to randomly work.

I cannot print new documents or workbooks, it becomes unresponsive and then the program has to close. I can only print from saved documents, which o can’t always open!

MYOB cannot print now, I have to save as a pdf and then print. I know MYOB isn’t “Microsoft” but this only started when this pop up started. I have never experienced this issue before.

This is happening on all four computers and started at the exact same time.

I have tried turning off all network sharing connections and still no change.

This is really impacting my day to day operations ans these programs are all I use. It causing a significant loss of time.

Can someone please help?

Windows for home | Windows 11 | Performance and system failures

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.

0 comments

47 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2025-04-12T05:21:43+00:00

    I can print from my phone but somehow the printer will not work when I push the print button and "waiting for printer connection" message pops up.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-31T14:03:23+00:00

    I had this issue on a brand new laptop. Everything was quick except for printing. In my case, I have two HP printers as my primary printers and both had the same issue.

    1. I downloaded the HP Drivers rather than using the Windows Versions
    2. Changed the printers from IPP to TCP/IP ports

    Printing reverted to quick without the wait. After replicating it on both printers, it may have just required step 2 but I don't have another printer to test with.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2025-01-11T12:58:10+00:00

    Thank you that worked

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-01-09T19:21:51+00:00

    Yes, turning off allowing windows to manage default solved it. My problem was probably related to adding a new printer that Windows decided was the default even though it's not available when I'm at the office. The piece of code that just "gets stuck" when the printer isn't available needs to be updated...

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-11-30T04:11:31+00:00

    This is most likely happening because Windows is attempting to connect your document to a printer whose port settings are such that it requires the printer to be present and accessible. So, to fix this, go to control panel, select devices and printers. If you have no default printer set, then launch Windows Settings, go to Devices, then Printers and Scanners. From here, uncheck the box which says "Allow Windows to manage my default printer".

    If you DO have a default printer set, then either you need to switch on that printer and make it available OR select another default printer OR right click your default printer, select Printer Properties, go to the Ports tab. From there, you need to change the port settings. In my case I was connected to an Epson printer via an IPP port. Change it to another type of port. I suggest creating a new one by clicking the Add Port button or you could re-Configure the port via the Configure Port button. OR you could just choose another Printer from Devices & Printers window. In my case I had TWO connections to my Epson Printer. One via the network which used a different port configuration. Therefore, I suspect that ultimately, it is a it is a port configuration that is causing the issue. What or how exactly, I have not been able to investigate yet. but at least you have some direction to fix this issue. It is likely that this is also following a Windows Update that is changing how these ports work.

    Hope this helps!

    Was this answer helpful?

    0 comments