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 > Unable to deploy revised publishing package with SolarWinds customization

Unable to deploy revised publishing package with SolarWinds customization

Updated: July 4, 2017


This article describes an issue where edited updates are not applied to clients when a package is edited or republished.


  • All Patch Manager versions
  • All Windows Server Update Services (WSUS) versions


The Windows Update Agent caches updated binaries and metadata. When the new revision of an update was available, only the metadata was updated and this caused the update installation to fail because the checksum was incorrect.


When editing the package metadata (title, description, detection rules, and so on), edit the previously published package and republish it.

Note: The package revision number will change to a later version.

If there is a change in the binaries (installer and package content), publish the package as new a package. When making a change to a binary in a package:

  1. Create a duplicate of the previously published package.
    Note: The duplicate package name will not be visible to end users.
  2. Edit the binary content of the duplicated package.
  3. Set the previously published package in WSUS to Expire.
  4. Publish the new update.


Last modified