HP Officejet Pro 8610 - Cartridge Damage

[SpoonDono]

Hello all!

I've been able to use my Officejet Pro 8610 for about 7 years now with no issues until last week. The magenta cartridge was running low during printing, so I replaced it with a brand new genuine cartridge. I was thrown an error that meant I could no longer print.

I've tried everything from unplugging and waiting, removing and replacing cartridges, carefully cleaning the print head and cartridges, seeing if the old ones still work (they don't), checking for firmware updates (none); pretty much anything suggested on the internet and in the Virtual Assistant.

I know the printhead is fine as its health is good. All of my new color cartridges are "damaged" somehow. The XL black cartridge is fine.

My current assumptions are I need to figure out how to wipe the error from the printer's memory to see if it goes away (power cycling by removing cables isn't working), it's a software/security upgrade on the cartridge chip making it incompatible with the printer until a software upgrade releases, there's a new physical piece (that I can't see) of the HP 950/951 cartridges that isn't mating well with the printer, or [big box store] sold me bad cartridges.

[sandytechy20]

@SpoonDono

Welcome to the HP support community.

I understand that you are getting cartridge error, I am glad to assist you.

Follow the steps mentioned in this HP document to fix the issue:- Click here

Keep me posted.

If this helps, please mark the public post as an accepted solution so that it benefits several others.

Cheers.

[SpoonDono]

Hi Sandy,

I followed the steps for my specific error and it didn't work. When I went through this process the first time, the error changed from stating that one cartridge was damaged to three of them being damaged.

[sandytechy20]

@SpoonDono 

This might require one on one interaction to fix the issue, I am sending you a private message with the steps to talk to HP support.

Please check the mailbox icon at the top-right corner of this screen.

I hope this helps resolve this issue completely.

If this helps, please mark the public post as an accepted solution so that it benefits several others.

Cheers