Firmware Update has ruined my ability to print on cardstock

[ldscdr74]

My Office Pro 8710, which I purchased in 2023, could print on all kinds of paper. One of its strengths was printing greeting cards on card stock. However, after I upgraded my firmware version, NOTHING WORKS. It continues to print on regular paper but printing on cardstock paper is a complete disaster. How do I either (1) Fix the problem or (2) roll back to my old firmware version? 

[Sneha_01 · Accepted solution]

Hi @ldscdr74

Welcome to HP Support Community.

Thank you for posting your query, I will be glad to help you.

I'm sorry to hear you're having issues with your OfficeJet Pro 8710 after the firmware update. Here are some steps to help you troubleshoot and potentially resolve the cardstock printing issue:

1. Check Printer Settings

• Make sure you have the correct paper type selected in the printer settings. If you’re printing on cardstock, ensure that you choose "Cardstock" or "Heavyweight" in the print settings on your computer.

2. Update Printer Drivers

• Check if there are any updates available for your printer drivers. Sometimes, driver updates can resolve compatibility issues. You can find the latest drivers on the HP Support website.

3. Adjust Print Quality Settings

• In the print dialog, try adjusting the print quality settings. Selecting a higher quality might help when printing on thicker paper.

4. Use the Right Paper Path

• Ensure that you are using the correct paper tray and path for cardstock. Some printers have specific trays designed for thicker media.

5. Perform a Printer Reset

• Try performing a hard reset:
  • Turn off the printer and unplug it from the power source.
  • Wait for about 60 seconds, then plug it back in and turn it on.

I hope this helps.

Take care and have a good day.

Please mark this post as “Accepted Solution” if the issue is resolved and if you feel this reply was helpful click “Yes”.

Rachel571

HP Support

[ldscdr74]

Rachel571, I'm not exactly sure what I did to correct the problem, but it appears to be resolved now. I appreciate your support and thank you for your assistance with this vexing problem!