What is causing the error code B305ED09 on my HP OfficeJet Pro 9018 printer and how do I fix it?

[Please_Choose]

The link in your response to the document to show me how to get the model results in a 404 page.

I have the Officejet Pro 9016 Model printer.

[CMSuff]

Me too, please help

HP 9014 Office Jet pro

[Fieldgreens]

Hello, I have an HP OfficeJet Pro 9018

[zekord]

How can I get the instructions to the same problem, please.

[ChiefF]

I Have a 9010 with the same problem could you send me reset instructions?

[CMSuff]

Please help, I posted a request for assistance two days ago with this issue.  A fix has been made available to other users, please can you share it

[Please_Choose]

"The reset instructions are specific for your printer and performing those steps on a different printer may brick the device" 
If pressing a simple sequence of the menu items is going to brick your device, I would consider that a disastrous design.

Having to go through this process of waiting for days for support staff to hopefully answer messages with a secret code sequence is just adding insult to injury.

I would strongly advise everyone to avoid ever purchasing this product.

[Fieldgreens]

Totally agree. I’m still waiting for HP to send me a direct message with a code to fix this issue. 
I’ve chosen not to try and resolve it on my own because I’ve read in another forum that resetting their printer rendered their printer cartridges useless, so they couldn’t print a test page to move onto the next step in fixing the problem. SMH

[CMSuff]

I have tried to arrange a callback, but despite promises nobody has messaged or called.  How can this be fixed?

[JoseD1]

I am having the same problem with an HP OfficeJet Pro 9015.  Don't you think it's strange that the reputed solution involves having to get a private message that is unique to our printer model alone with the threat that it can "brick" our computers if we don't follow these unique, individually sent, messages?  It doesn't make any sense.  Just print the solution, if there is one.

I am finding it very interesting that this specific error code seems to have come out in droves over the last 2-3 weeks.