Skip to main content


Feels like Groundhog Day.

I have a few OS X 10.10.x Macs that are constantly getting prompted to update either the HP Printer Software Update 3.0 or the HP Printer Software Update 3.1, over and over, regardless if it has already been installed or not. Sometimes the 3.0 update wants to be installed on top of the 3.1 update, which is really weird (I think they are comprehensive and have no dependencies on prior updates).

The updates show up in the GUI and via the CLI too. The software update command line tool /usr/sbin/softwareupdate shows them as "031-1003-3.0 HP Printer Software Update (3.0)" and as "031-1003-3.1 HP Printer Software Update (3.1)"

Printing is not affected. All Macs can add new HP printers and print to existing HP printers with no issues.

The updates are coming from my USUS server, not the Mac App Store. I have my Macs pointed to an internal SUS server running OS X 10.10.5 and Server 5.0.3. I have removed/deleted and then re-enabed both HP updates from the Server GUI. Nothing seems to change. It looks like the 3.0 update is no longer available now, but some clients still see it. Weird behavior.

I can't tell if its a Apple SUS server issue or a OS X client issue.

I can't find a package receipt for the H updates on my Macs. So I think the install/update may be failing. Heres the packages I find. After running /usr/sbin/pkgutil --pkg-info XXXX none seem applicable.

com.apple.pkg.HewlettPackardPrinterDrivers
com.apple.pkg.HP_CHorse
com.apple.pkg.HP_CHorsePDM
com.apple.pkg.HP_CHorsePIL1
com.apple.pkg.HP_CHorsePL
com.apple.pkg.HP_CHorsePSF
com.apple.pkg.HP_Chuckwalla
com.apple.pkg.HP_Cmd2HP
com.apple.pkg.HP_DMF4
com.apple.pkg.HP_DriverCore
com.apple.pkg.HP_FaxK2
com.apple.pkg.HP_ImageEnhancement1
com.apple.pkg.HP_KextNew
com.apple.pkg.HP_Pdf2Pdf2
com.apple.pkg.HP_PSK3
com.apple.pkg.HP_PSS
com.apple.pkg.HP_Scan3
com.apple.pkg.HP_ScanButton

Feels like Groundhog Day.

Feels like Groundhog Day.

Welcome to crazy town. Need HP software?

Your SUS catalog has an issue. I've seen this before... can't remember off the top of my head which file in /Library/Server/Software Update you need to remove to fix this. Doesn't require redownloading everything, just the catalogs, potentially.

Do you have a lot of updates selectively disabled?

@RobertHammen Why yes, I do actually. Matter of fact, in the last few weeks, I have been trimming the available updates on my SUS server - for storage reasons.

I used to download everything and enable them after vetting. But now, I don't download or enable anything until Im ready to get them manually.

Here is my current config:

swupdatekc01:~ admin$ sudo serveradmin fullstatus swupdate
swupdate:state = "RUNNING"
swupdate:lastChecktime = 2015-09-30 08:00:05 +0000
swupdate:autoMirrorOnlyNew = no
swupdate:syncServiceState = "RUNNING"
swupdate:startTime = 2015-09-18 19:32:20 +0000
swupdate:lastProductsUpdate = 2015-09-30 11:37:12 +0000
swupdate:logPaths:swupdateServiceLog = "/Library/Server/Software Update/Log/swupd_syncd.log"
swupdate:logPaths:swupdateErrorLog = "/Library/Server/Software Update/Log/swupd_error.log"
swupdate:logPaths:swupdateAccessLog = "/Library/Server/Software Update/Log/swupd_access.log"
swupdate:pluginVers = "10.11.111 (111)"
swupdate:checkError = no
swupdate:autoEnable = no
swupdate:updatesDocRoot = "/Library/Server/Software Update/Data/"
swupdate:hostServiceState = "RUNNING"
swupdate:autoMirror = no
swupdate:numOfEnabledPkg = 401
swupdate:servicePortsAreRestricted = "NO"
swupdate:numOfMirroredPkg = 1449
swupdate:setStateVersion = 1
swupdate:syncStatus = "DONE"
swupdate:readWriteSettingsVersion = 1

My swupdate logs are blank. Nothing showing up in Console app for swupd. Need to address this, too.

How do I force re-download of Apple's catalogs?

Will /Applications/Server.app/Contents/ServerRoot/usr/sbin/swupd_syncd -sync re-sync all catalogs and thus clean-up certain issues?

Hey,

Having the exact same issue, did you managed to solve it?

@chaniel I ran /Applications/Server.app/Contents/ServerRoot/usr/sbin/swupd_syncd -sync and it appears to have clean-up my issues. I can no longer reproduce the issue on an of my SUS clients.

Terms & ConditionsCookie settingsAccessibility statement