Error: 'Failed to sign package; error was: 2148081670' when Publishing Updates

Error: 'Failed to sign package; error was: 2148081670' when Publishing Updates

Symptom

  1. When using the Configuration Checker to validate the settings, an error is returned:
    OR
  2. When publishing updates, the AutoPublish.log will show:

'Failed to sign package; error was: 2148081670'

Solution

The error code resolves to 'No provider was specified for the store or object.' There are 2 ways to resolve this error.

First make sure there is only one Code Signing certificate imported into the WSUS > Certificates store on the WSUS server:

  1. In the Configuration Manager console, navigate to the Software Library workspace.
  2. Navigate to Software Updates > Lenovo Patch > Updates.
  3. Click the Settings button on the ribbon bar.
  4. In the Lenovo Patch Settings dialog, click the WSUS Server tab.
  5. In the Current certificate subsection of the WSUS signing certificate section, click the View Certificate button.
  6. In the Certificate window, click on the Details tab.
  7. Scroll to the bottom of the list and obtain the Thumbprint value.
  8. On the WSUS server, open CERTLM.msc.
  9. Navigate to WSUS > Certificates.
  10. Review all certificates with the Intended Purposes of Code Signing.
  11. Remove any other Code Signing certificates from the WSUS > Certificates store where the Thumbprint value does not match the thumbprint value from step 7. Leave only the one Code Signing certificate with a matching Thumbprint value from step 7.

Next, make sure that the certificate file imported into the WSUS > Certificates contains the private key. The private key can be provided through a .PFX file, not a .CER file.

  1. On the WSUS server, open CERTLM.msc.
  2. Navigate to WSUS > Certificates.
  3. On the Code Signing certificate in the WSUS > Certificates store, review the icon in the "Issued To" field. Verify that the Icon has a key on the left side, ex:

    Certificate Icon

  4. For further review, open the Code Signing certificate to the General tab and, below the “Valid from MM/DD/YYYY to MM/DD/YYYY” line, verify there is a key icon similar to the one on the icon above and a message stating “You have a private key that corresponds to this certificate.”
    If the key is not present on the icon and the key and message are not present in the certificate on the General tab, the .cer file was manually placed in the WSUS > Certificates store.
  5. Obtain a copy of the code signing certificate in a .PFX file that includes the private key. The .PFX file should be password protected. Import into Lenovo Patch through the Settings > WSUS Server tab, using the Import button. Enter the password when prompted.