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.
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. Patch My PC does not own, curate, validate, test, or maintain External Apps, their installers, manifests, or metadata. 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 Support
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 Supported
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 Fails
If a WinGet app fails to install or isn’t detected after deployment, our support is limited to general pointers rather than active troubleshooting.
Because we package strictly in line with the WinGet manifest, any installation issue should be directly reproducible by running the WinGet install command on the endpoint. The best first step is trying that, along with checking whether the version or architecture already installed matches what you’re targeting.
These are checks you’re welcome to try yourself, though unfortunately we’re not able to investigate or resolve installation or detection failures directly.