Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Patch Manager > Unable to deploy revised publishing package with SolarWinds customization

Unable to deploy revised publishing package with SolarWinds customization

Created by Interspire Import, last modified by Rodim Suarez on Jul 03, 2017

Views: 108 Votes: 1 Revisions: 17

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
17:26, 3 Jul 2017