Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Failed to sign package error in Patch Manager

Failed to sign package error in Patch Manager

Updated Jan 25, 2019


When you publish third-party packages to the WSUS server(s), you may see the following error:


There are multiple reasons for the same error: 

1, In some cases after you delete, recreate, and resign the packages with valid WSUS cert, the error returns. 

2. The packages are copied successfully to the local publishing folder at %AppData%\Local\EminentWare\Packages and the Updates Services Packages folder on the WSUS server. However, the PM Worker process displays one or all of the following errors:

2018/06/13 16:44:04:073 PID: 3696 TID:  7684 [ERROR] Failed to publish update: Adobe Acrobat DC Update 18.011.20040 Message: Failed to sign package; error was: 2147942405 Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.SignPackageCab(Boolean dualSign, String httpTimeStamp)
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName, Boolean dualSign, String httpTimeStamp)
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)
   at EminentWare.UpdateServices.Administration.UpdateServer.PublishUpdates()

The permissions are not an issue. When you review the Application Event logs in the WSUS server, you may notice an error message similar to the error below with Event Source = MOVE AV Client and eventid = 24, which points to the root cause in this case.

Deferred scan is in progress for file 'D:\WSUS\Upd
ateServicesPackages\cde8e668-2572-4777-8fbf-427af3497cd3\b75e6446-1c23-4115-8d60-2edb35ebeb1b\AcrobatDCUpd1801120040.msp'. (A thread in  process took 30 seconds for scanning. Hence, access denied.)


  • All Patch Manager versions
  • WSUS


  • The WSUS content store was improperly moved or is misconfigured.
  • Packages larger than 200 MB may be blocked or locked by the antivirus software.
  • One of the WSUS(or SUP) servers Certificate expired


  1. Verify that WSUS cert store has a valid cert on the WSUS server you are trying to publish
  2. Verify the WSUS permissions as explained in this SolarWinds article.
  3. Verify the WSUS shares are in place and accessible by the Primary Application Server.
  4. Check windows event logs if antivirus software is not locking/blocking the update files due to their large size i.e few 100 MB.

If the shares were previously moved and the error displays when you publish, use the WSUSUtil tool to move the content stores. (© 2018 Microsoft Corporation, available at, obtained on August 8, 2018.)

You can move the shares back to your current path. The utility should resolve issues with the shares and registry settings that help define the storage location.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.




Last modified