I just tested publishing and am also seeing the same issue. From the UltraVNC website it doesn't appear they have a newer update than this so I'll check with our content team to see if anything needs to be fixed. I'm thinking maybe the URL the vendor is using changed or something similar. I'll update when I find out some details.
Our content team looked into this and did confirm the vendor made a change - it looks like they updated the digital signatures on the downloads for Ultra VNC 18.104.22.168. Our content team will be updating the logic in the next release for Shavlik Patch.
So, you can either;
Wait until the new Shavlik Patch update comes out, overwrite these updates on import, and then publish.
Or, you could manually download the latest file and make the change within SCUP before publishing.
Thanks for the heads up on this.
Thanks Adam, I can wait till the next update...
I got the update (dated 8/5) and it still does not work...
That's odd. I just tested with the new cabs and it successfully published for me now.
This might be an issue concerning how you originally mentioned you had it configured. Did ensure to import the newest .cab in SCUP and re-download the update and place in your local source? In case you need to re-download the update(s) here's the links:
If you still have issues, could you send in the SCUP log after attempting to publish it? If you prefer, you can send it in by opening a case at https://support.shavlik.com/.