---
title: "Print Scout MSI deployment via SCCM fails, or upgrades fail after previous versions are only partially removed"
slug: "print-scout-msi-deployment"
tags: ["deployment", "installation failure", "msi", "pharos cloud", "print scout", "registry cleanup", "sccm", "upgrade", "windows"]
status: "new"
updated: 2026-08-19T13:56:30Z
published: 2026-08-19T13:56:30Z
canonical: "kb.pharos.com/print-scout-msi-deployment"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Print Scout MSI deployment via SCCM fails, or upgrades fail after previous versions are only partially removed

### Overview

When deploying the Pharos Cloud Print Scout MSI through SCCM, you may see one of two related problems: the initial deployment fails when the installer is run from an unsuitable source context, or later upgrade attempts fail because an earlier Print Scout version was only partially removed from the workstation.

This article explains how to separate those two conditions and restore a working deployment path for affected Windows clients.

### Applies to

- Pharos Cloud Print Scout for Windows.
- SCCM based MSI deployments.
- Upgrade scenarios involving prior Print Scout versions, including 8.2.1.100 and 8.3.10.100.

### Symptoms

- SCCM deployment of Print Scout fails with MSI exit code 1603.
- The installer works when run locally on a clean machine, but the SCCM deployment still fails.
- A workstation that previously had Print Scout installed may continue to fail during upgrade even after a new installer package is provided.
- The upgrade path may appear to enter removal or upgrade logic for an older version that is no longer fully present on the machine.

### Cause

There are two distinct causes that can produce similar deployment failures.

First, the initial MSI deployment can fail when the package is executed from a source path or package structure that the installer cannot use correctly during deployment operations.

Second, upgrade attempts can fail if an earlier Print Scout installation was only partially removed, leaving behind MSI or registry state that causes the newer installer to treat the machine as an incomplete upgrade target.

### Resolution

1. Validate the installer from a local folder first: Download or copy the Print Scout installer package to a local folder on a test workstation that has not already been affected by the failed upgrade path, then run the install locally.
2. If the local install succeeds, review the SCCM package design: A successful local test means the installer itself is viable in that environment, and the next step is to review how the SCCM package stages and executes the content.
3. If upgrades still fail on machines with previous Print Scout versions, treat the issue as incomplete prior-version cleanup: Check for lingering Print Scout remnants from the earlier install and remove the stale upgrade state before retrying the new MSI.
4. Use the affected product codes to confirm which version remnants are still present:
  - Print Scout 8.2.1.100: `{35447D8C-DE7C-4F8E-854A-97CBBA3C5CE9}`
  - Print Scout 8.3.10.100: `{1D95A751-B997-4A0B-A775-A9F06170168D}`
5. Capture full MSI logging from SCCM during retest: If the failure persists, collect verbose MSI logs from the SCCM deployment so you can confirm whether the problem is still package execution, or whether the machine is still carrying old installer state.
6. Retest the upgrade after cleanup, first manually, then through SCCM: Once the previous-version remnants are removed, verify the new MSI manually on the affected machine before reintroducing the same logic into SCCM for broader deployment.

### Notes

- A local success does not by itself prove the SCCM deployment is healthy for upgrade scenarios.
- If only upgrade paths fail, the most likely differentiator is leftover state from a prior Print Scout version.
- If this issue appears across multiple endpoints, consider adding pre-install detection and cleanup logic to the SCCM package before launching the MSI.