Error Code 11 - M234DWE - Genuine Toner suddenly stopped working. Unable to clear error

[Skypilot62]

My M234dwe LaserJet has suddenly stopped working and displays “Er 11”. This relates to non-compatibility of the toner cartridge. It’s a genuine cartridge (subscription type with HP) and was installed about three months ago with low usage but was working fine yesterday when last used. 

I have cleaned the little tiny chip as well as the “socket” for it (no liquids)

I have done a factory reset

i have tried hard restart

 nothing seems to clear the issue. Is it likely to be the toner cartridge or printer at fault? Printer is just over two years old and just out of warranty (October 2024). Are toner cartridges covered by a warranty period?

[Gill80]

Identical problem here, was printing yesterday and it just stopped and threw up code 11. Even got a new HP cartridge delivered today from Amazon, no difference. Have tried all of the suggestions, various resets, cleaning, uninstalling, reinstalling, nothing gets rid of this code. I have managed to get two status pages printed out, so it still functions as a printer, just can't get it to work otherwise.

[EvanCao]

"I have managed to get two status pages printed out"  

How do you get this status page print out,   Mine was working fine days ago,  I tried all the things you mentioned.

Still see this error 11 after turning on the printer.

[Gill80]

Not certain to be honest, I'd done some diagnostics etc and it was after one of many off and on reboots that they ran off. I think it was one where it included some sort of reset. I got excited that it was working and then the er 11 popped back up.

My suspicion is that there has been some sort of update that's caused this. Like the OP our printer and the cartridge have been working fine for months. I printed out one invoice fine, sent second to printer and up popped this code. That a brand new HP cartridge doesn't fix it concerns me, plus it was £60 I maybe didn't need to spend.

I just find it curious that my search on here found an identical issue at an almost identical time for someone else.

[Gill80]

Just to add, the status pages that printed were a day apart, one was yesterday from the existing cartridge and then one today from the new, identical, cartridge delivered by Amazon. 

This tells me that the printer can access the cartridge and use it to print, when it wants to. I don't see how anything other than a software/firmware change could create this identical issue across multiple users. If there's three of us on here already I would guess there's plenty more out there. 

Sadly I'm not knowledgeable/expert enough to figure if and when a change happened and whether it could be reversed or rolled back. If it does turn out to be HP trying to 'protect' its users then I'm less than impressed. I've had to go and buy another printer in the meantime as I was printing invoices for my customers, so I don't have a choice.

[K-Med]

Same thing here! Same printer, same error and same timing.

HP pushed something that broke our printers and it needs to be addressed ASAP.

[K-Med]

This firmware update hit all of our printers on March 4th or around that time.

Here's the link to the readme of the firmware update. It needs to be reverted or updated again.

HP LaserJet MFP M234dw Printer Software and Driver Details

[Valiant91]

Can confirm mine updated last night and I have the exact same issue. My dad has the same printer and his is doing the same also today 

[H411]

Same thing. This is 100% un-called for. They should issue an update ASAP. Or provide us with new replacement printers FOR FREE. I paid for a printer - and they have knowingly BROKEN it. With no recourse or even acknowledgement of the problem. That is 100% theft in my book. I did not "rent" a printer. I paid for a printer (IN FULL) to use when I needed to. With "official" HP toner as well. 

Now the stupid printer thinks I am using a "non-HP" toner cartridge?

Unacceptable.

And I have no way to contact them! And if I did - they wouldn't understand me anyway! 

[shippinguy]

Exact same issue here, the culprit is the latest firmware update.  Anyone know where to find the previous version?