Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Publishing packages error: Verification of Signature failed for file

Publishing packages error: Verification of Signature failed for file

Updated January 16, 2018

Overview

When you publish third-party updates to your WSUS server, the following error displays: 

Verification of Signature failed for file:

Environment

  • All Patch Manager versions
  • All WSUS versions

Resolution

Solution 1: Run the Provision WSUS Server for Publishing Wizard

This procedure will create or distribute the certificate needed for publishing.

  1. Log in to the Patch Manager Administrator Console as an administrator.
  2. Expand Administration and Reporting and select Software Publishing.
  3. In the Actions pane, click Server Publishing Setup Wizard.
  4. In the wizard, click the WSUS Server drop-down menu and select your WSUS server.
    wizard.png
  5. Complete the remaining fields, and click Next.
  6. Compete the wizard. 

Verification

Run Microsoft MMC and add the snap-in for certificates for the computer account on the WSUS and the Patch Manager servers.
The certificates should be in the following:

  • Trusted Publishers store
  • Trusted Root store

On the WSUS server, the certificates should be in the WSUS certificate store.

Solution 2

If the steps in Solution 1 does not help:

  1. Backup the existing WSUS cert from the MMC snapin.
  2. Delete the WSUS cert from Trusted Root and Trusted Publishers store(s).
  3. Follow steps in Solution 1 and then verify.
  4. Make sure there are no duplicate or old certificates in the Trusted Publishers and Trusted Root and WSUS store.

 

Last modified

Tags

Classifications

Public