HP OfficeJet Pro 9018 printer update won't download.

[hay3911]

To all using HP 9010 and 9020 series OfficeJet Pro all0in0one printer. I wrote the above request for info and 19 have replied. Please note: I am using a Mac computer running the latest OSX upgrade: Ventura 13.5.

The "fix" I thought I found did NOT work. I replied to my own Post noting that.  I have since not been able to correct the HP download issue.  It may be an issue with a HP/newest Mac OSX interface (But have never had one in the past).  It may be that the "fix" being reported is applicable to only Windows based computers as they interface with our HP printers.  I suspect this latter note may have some validity in that on one HP posted set of resolution steps I had come across listed where one could shut off all downloads - but on my computer access of that page, all the options were greyed out - meaning they were not accessible by me on my Mac computer.  I've notified Apple of this issue and am awaiting a reply with some info.  Re: HP, well I am angry enough that I've written directly to HP's Pres/CEO to complain and ask his assistance in getting HP to address our needs.  We are their customers and if they want us in the future they need to resolve this for us.  Otherwise, this HP OfficeJet Pro all-in-one is my last.  If I get a reply I will post further.  In the meantime, thank you all for sharing your experience and suggestions.

[subrosa2]

Hello hay3911,

Have you tried uncording your printer from the Mac and try to stop the updates/downloads from the  little screen on the printer? I would think you can then reconnect to your Wi-Fi and then reconnect your cord. You might want to give it a try.

[hay3911]

Thank you for offering it as a solution.  Yes, have tried that, but, this same issue repeats each time. 

[bgellisshapiro]

I too am having the same issue.  I am Windows 11.  I reset, restored, reloaded, etc etc, unplugged, tried to locate the firmware to download to the computer directly (not listed).  Chat help is garbage. 

HP is definitely at fault here and there is no way to find out if they are even dealing with it.  This is the third time my relatively new (but out of warranty) HP printer has crapped out on me.  I am seriously considering going with another brand.

I replaced the Instant Ink cartridges with store bought cartridges and it does print.  So, my workaround is to cancel Instant Ink, until and unless the firmware update gets fixed.

[Bbtaz]

Same here. Using Windows, Mac, and Iphone iOS and all the same.

[bgellisshapiro]

Just spent some time on phone with technical support.  The only option they had was to let technical support takeover my laptop and try to fix it.  BUT I would have  to buy the extra support package to pay for it.  They would do the same things I tried and not get anywhere.  I said no.

[bgellisshapiro]

Is there any way to remove the Solved tag that is currently attached to this discussion?

[hay3911]

I. wish there was.  I made a mistake when I posted by also clicking "Accepted".  Dumb step by me.  Sorry.  If anyone kn ows how to remove the "Accepted" Post, please do.

Thanks,

HAY3911

[Bbtaz]

I just completed these steps posted by SiriusNo earlier and so far this has worked and stopped the endless loop of the update won't download for now:

Until HP fixes the problem they caused you can disable firmware updates without having to restore factory defaults.

In a web browser, HTTP: to the printers IP address (Example https://192.168.1.100) Your address will be different.

This takes you to the printers Embedded Web Server. Go to settings at the top, then on the left side expand Security, Administrator Settings. Then at the bottom of Printer Features on the right, uncheck the "All Firmware Updates" and click Apply.

[Seadog_J]

If you have Instaink, you will not be able to disable updates.  The only current solution is to call and cancel Instaink.  I canceled, and the rep asked why; when I explained, she just said ok and canceled it.  Frustrating to say the least.  I am on a Windows 11 PC and from everyone else posting it looks like a recent update caused this.