Problem with new HP Printer Software

Upton666's workaround did the trick for me.

Upton666's solution worked for me too!! Thanks

Really, incredibly unbelievable that Apple would let this go on for so long.. roll back the update!!

In Finder navigate to Macintosh HD / Library / Printers / hp / PDEs. Right (control) click on 'hpPostScriptPDE.plugin' and 'Show Package Contents'.

Then open the Contents folder and you will find a plugins folder. DELETE IT and your printer will work.

The old 2.09 version did NOT have this folder and plugin.

This did the job for me - thanks @upton666

worked a treat - took a couple of minutes to do once I had found this answer - spent the last few hours trying to figure it out. Thanks!

Now, if only I could get MS Word to work after the Mountain Lion upgrade... :/

I also was unable to print to PDF or print to paper using a HP printer (HP Laserjet 1300). Each time I tried, regardless of which program I used to print, the software would crash. I am running Lion 10.7.4.

The following solution worked. I downloaded from the HP website the driver for 10.6 and installed it. For the HP Laserjet 1300, the 10.6 driver is called "HP Laserjet and Edgeline print-only"

Smooth sailing afterward.

Just to test, I tried reinstalling Apple's HP Printer Software Update 2.10 through System Preferences. The crash problem resurfaced immediately. Installing the 10.6 HP driver got rid of the problem again.

Great, many thanks, worked perfectly!

Regards RAPHAEL

The fix worked, but now the App Store keeps asking me to update the software back to 2.10. It clearly picks up thag part of the update has been manually removed. Does anyone know how to stop this from happening, because having to re-delete the folder again and again is nearly as annoying as the original problem!

Don't update is the simplest way. Skip that update until it has been fixed, I'm doing this on 2 iMacs.

Wyndham Top Shop wrote:

Don't update is the simplest way. Skip that update until it has been fixed, I'm doing this on 2 iMacs.

Looks like your skipping effort has payed off. You can now update to version 2.11, which was released along with Mac OS X 10.8.1. I'm currently installing version 2.11, and shall report back with my findings ASAP. I'd say the problem will be fixed, though, as it's quite a high-priority bug.

Just installed 2.11 and all is good. HP still suck though!

At least their software QA went haywire... 2.11 was released with the sole purpose of resolving the issue which arose in 2.10. So 2.10 should never have been released in the first place.

A word of advice to anyone who downgraded to 2.09 in order to resolve the issue: If Software Update (10.6 and 10.7) or the Mac App Store (10.8) advertises both versions of the HP Printer Software (i.e. version 2.10 AND version 2.11), please apply the update to version 2.10 FIRST; then update to 2.11. That way, you won't run the risk of your system's updater wanting you to downgrade to 2.10 after having applied 2.11.

That is what happened to me. My system (10.8, so it's the App Store) advertised availability of version 2.10 AFTER I applied 2.11. In the end it didn't matter, because no downgrade actually took place, but it certainly was a bit of a strange issue... Apparently, Printer Driver Updates aren't cumulative, or at least not in the 'eyes' of Software Update/the App Store...

Anyhow, I'm really glad this blatent bug has finally been resolved.

And just to stick with the promise I made in the previous post: I have no problems whatsoever when printing using software version 2.11. So there's no need to wait any longer.

The other way to deal with this is..when the 2.10 update pops up, right-click just below the "Update" box and tell it to "Hide Update". On two systems I manage, doing that avoided having the App Store ask again to install the 2.10 update before installing the 2.11.

I had wondered (and committed G****le searches on) how to hide updates in Mountain Lion, so I'm really glad I've found that out now, through your post. But as I've explained, even if you would have started its installation again, you would have noticed nothing, as a newer version of any device driver won't budge unless you force it to (i.e. deleting, then reinstalling). Fortunately, this also applies for this update: once a newer version has been installed, an older update (thus a downgrade) can and will not replace it. To perform a downgrade, you'll have to physically overwrite the device driver files by the ones for the older version.

Agree that the system shouldn't perform a downgrade (the old Software Update never seemed to have that problem), but I read your post to say that's what it tried to do, even if it wouldn't complete it. I simply supplied a method of avoiding the scenario in the first place. In my case, when I realized what the problem was, I completely removed 2.10 and manually replaced it with 2.09. A bit later, once I had determined that it was the postscript plug-in in 2.10, I simply deleted the plug in until 2.11 was released. In the interim, to avoid having the App Store's software update try to install the bad guy on my other systems (and dealing with my wife inadvertently installing it), I simply told the App Store to hide the update on our other machines.