What does Windows error code 1651 (ERROR_PATCH_MANAGED_ADVERTISED_PRODUCT) mean?

 
Previous Next
ERROR_INVALID_PATCH_XML ERROR_INSTALL_SERVICE_SAFEBOOT

ERROR_PATCH_MANAGED_ADVERTISED_PRODUCT

The managed product is advertised but has no installed feature to update.

ERROR_PATCH_MANAGED_ADVERTISED_PRODUCT is Win32 error 1651 (0x673). Advertisement registers a product and its features without necessarily installing the feature payload. For a per-user managed or per-machine product that remains entirely advertised, Windows Installer has no installed feature state against which to apply the requested MSP. The code therefore describes product state and deployment context, not corruption of the patch file.

Typical ways this state is reached

  • software distribution advertised the MSI but the user never activated or installed any feature
  • an administrator attempts to pre-stage a patch before the base product is installed locally
  • the patch command runs in a different user or machine context from the advertised registration
  • inventory reports the product as present even though every feature remains advertised or absent
  • a deployment sequence omitted the feature-install step that was expected before patching

Installation facts to collect

Capture ProductCode, PatchCode, user SID, installation context, assignment source, feature states, package and patch versions, elevation, and the complete MSI command line. A verbose log should show whether the product was found as per-user managed, per-user unmanaged, or per-machine. Distinguish “registered” from “installed”; generic software inventory often hides that difference.

Diagnostic sequence

Query Windows Installer for the target product and enumerate feature states in the same security context used by the patch operation. Verify that the ProductCode is the exact target and that at least one required feature has local or source state rather than advertised state. Check whether a management platform is launching the patch as SYSTEM for a product advertised only to a user.

Review the deployment order. If the intent is a new installation at an already patched level, use an approved installation source or administrative image that includes the required update strategy rather than trying to patch an unmaterialized advertisement. Confirm vendor support for slipstreaming or chained installation.

Supported resolution

Install or activate at least one appropriate product feature, then apply the patch in the matching context. Alternatively remove the obsolete advertisement and deploy the base MSI followed by the MSP according to publisher guidance. Do not manufacture feature-state registry values; Windows Installer component registration must remain consistent.

Deployment tooling should model advertised, installed, and patched states separately. Before offering a patch action, it should verify product context and feature state and provide a clear prerequisite instead of repeatedly returning 1651.

Difference from a nonapplicable patch

A patch can be perfectly valid and applicable to the product family yet still return 1651 because no feature is installed. Conversely, an installed product may reject a patch for version or sequencing reasons. The first correction is to establish the actual feature state, not to replace the MSP blindly.

Example

A managed desktop receives an advertised accounting application through Group Policy. Before the user launches it, a maintenance job applies an MSP as SYSTEM and gets 1651. Installing the assigned core feature first, then applying the MSP in the per-machine context, completes successfully.

References

Looking for a different code? Search another status or error code.