"Printer not Ready" Error

[sfintel]

Purchased new and arrived today – 3/16/15. HP Officejet Pro 8630 – [Personal Information Removed]

Installed all items as specified in documentation.

Will not print Outlook 2007 items – I get a “printer not ready” error. However, everything checks out okay with product.

Does not work with wireless or USB. However, I can print .pdf documents. And I can print from my iPhone.

[Sunshyn2005]

Hi @sfintel 

Based on your description, it sounds to me like the issue might have something to do with the driver on the computer. Please try using driver for the 8600 and let me know if doing so works.

The following instructions will help you to download and install the driver for 8600;

First, download the driver from here.

Next, select the 8600 driver instead of your 8630:

1. Click on the Start menu.
2. Click on Devices and Printers.
3. Right-click on your printer.
4. Select Printer Properties.
5. Click on the Advanced tab.
6. Click on New Driver.
7. Click Next.
8. Select HP from the first list.
9. Select the 8600.
10. Click Next.
11. Click Finish.
12. Click Apply.
13. Click OK to close the window.

Please try printing from your chosen programs and let me know if it works. Thanks.

[BillyRValentine]

8600 is not in the list.  There is a K8600 though?

[Sunshyn2005]

Hi @BillyRValentine,

Did you download the driver from here first? Once you download the driver it will be available. The k8600 is specifically older and will not have the same functionalities as the driver I am suggesting.

[BillyRValentine]

Thanks for pointing out the link again - overlooked that earlier.  The original poster never replied but the 8600 driver WORKED for me.  Thanks for that tip!  Aside from the driver nightmare, the printer is otherwise very nice - even moreso now that I can use it :smileytongue:.  For anyone else lurking, I did a manual install of the bare 8600 driver - skipping over the default selections.  Clicking the button below and unchecking ALL 4 items.  It's not obvious, but that will still install the bare printer driver.

Since they updated the Fax driver for the 8620 last week, I can only hope that they can update the 8620 printer driver too soon.  It offers a few different settings than the 8620 as shown below.

The printing shortcut settings are apparently new to the 8620.

[FerrellT]

All...After weeks of fighting this issue I finally had success today!  I turns out that Outlook creates a temporary file in %TEMP% location when printing.  Skipping ahead, I was able to determine that Windows 10 was blocking Outlook form creating that temp file in %TEMP%.  I checked the permissions on the %TEMP% folder and noticed that domain\Users was set to Read only.  When I gave domain\Users write permission on the %TEMP% directory, it was able to print.  I hope this works for you. 

[BillyRValentine]

I'm not using Windows 10.  Just replaced my 8620 with an 8720 and now the problem is back!  

I've not tried the 8600 drivers yet.

[BillyRValentine]

Ok, just selected the 8600 driver since it was still around.  Works.  Guess I'll need to burn this driver to a CD and put it in my safety deposit box if I want to print from Outlook in the future.

Got only knows what I've messed up by using the 8600 driver to print on the 8720!

[BillyRValentine]

Kudo's to HP chat.  They got me working using the magic printer driver.  "Deskjet 6980"  It's built in to Win10.

Deskjet?  Really?  I guess Outlook is picky and the newer drivers just don't mesh well with it.  Have no idea how they picked this one from the long list of drivers in Windows.  Their were plenty of OfficeJet drivers in the list but they were apparently looking specifically for this one.

I'm still using the driver on Win7 (8600) that I talked about above last year.  I ain't about to touch that since it's working.  It was already installed so I just switched to that driver after installing the 8720 software.

Really liking the design of this new printer.  Though I'd been happy with lightening NOT striking the house and killing the other to begin with!  After the initial driver debacle, it worked perfectly for over a year.