The Patch My PC catalog is a curated enterprise app catalog, with applications selected, tested, maintained, and supported by Patch My PC. This is our recommended source for application deployment. Because we own the packaging, testing, and maintenance, our catalog carries a level of reliability and quality assurance that customers should prioritize wherever an app is available there. See Curated vs. Crowdsourced: Why Enterprise Software Catalogs Require Professional Curation for more on why this distinction matters

External Apps in Patch My PC Cloud give you another option when an app isn’t in our catalog. This includes WinGet apps, which are classed as External Apps. Because these apps come from the WinGet repository rather than our own curated catalog, we don’t have visibility into how the installer or manifest was built, so we’re not in a position to guarantee or debug its behaviour. Doing so would mean making promises we can’t actually stand behind. As a result, External Apps are not equivalent to our catalog applications. They add deployment flexibility but don’t carry the same validation, maintenance, or support assurance

What We SupportCopy Link

Our support scope covers the Patch My PC Cloud experience and creating the app in Intune. Our support team will be able to help ensure:

  • Searching for and selecting External Apps (including WinGet apps) in Patch My PC Cloud works as expected
  • The Intune Win32 app is created successfully through Patch My PC Cloud
  • Supported customization options are applied correctly
  • Your configured deployment settings were applied as expected

Not SupportedCopy Link

Because External Apps come from repositories we don’t control, Patch My PC is unable to:

  • Validate, build, test, or maintain External App installers or manifests
  • Confirm whether a package source is vendor-approved or suitable for your environment
  • Guarantee install, upgrade, or uninstall behavior on client devices
  • Validate command-line switches, troubleshoot installer defects, or guarantee manifest accuracy

If Installation or Detection FailsCopy Link

We are not able to investigate or resolve installation or detection failures directly.

If a WinGet app fails to install or isn’t detected after deployment, support is limited to general guidance. For example, you may wish to:

  • Check that you’re targeting the correct architecture (x86, x64, or ARM64) and installer type (EXE, MSI)
  • Verify that an update deployment targets devices where the application is installed in the same context being used for deployment (SYSTEM vs USER)
  • Review the PatchMyPC-ScriptRunner.log on the client to ensure the expected configuration was included in the package delivered
  • Confirm that the configured deployment settings in Patch My PC Cloud are supported by the vendor
  • Test the application directly on the endpoint using the equivalent WinGet install command
  • If deploying in a SYSTEM context, use a tool such as PsExec to simulate the above installation under the SYSTEM account

Because we package strictly in accordance with the published WinGet manifest, installation issues should generally be reproducible when running the WinGet install command directly on the endpoint. If the application fails when installed directly from its source, the issue is likely outside the Patch My PC Cloud packaging and deployment workflow.

These are checks you’re welcome to perform yourself. Patch My PC cannot troubleshoot third-party installers, WinGet manifests, package content, or application detection logic maintained by the package owners.