Hello Chris,
First of all, thank you very much for providing the files.
I have tested this and can confirm the behavior you encountered.
I will also post about this here so that this will be public for future users facing a similar scenario.
First of all, please note that this is not an issue with your installation package, but rather winget's upgrade-compatibility guard tripping.
I have tried to create a verbose log of the winget upgrade process and in the log, I found the following:
2026-08-27 16:18:25.065 <V> [CLI ] Installer [X86,exe,Machine,] not applicable: Installed package type 'msi' is not compatible with installer type exe
Note: to create the log file, run the upgrade process with the --verbose-logs option, e.g.:
Code: Select all
winget upgrade --id JumpingBytes.ClipboardMaster --verbose-logs
then you can find the log here:
Code: Select all
%LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
As we can see, winget is tripping and sees your installed package type as an MSI.
My guess would be that winget gets the info from here:

- Screenshot_180.png (177.2 KiB) Viewed 16733 times
As you might be aware, Advanced Installer is a Windows Installer authoring tool, which means we utilize this technology for the packages that we create. Even if you create an EXE package, behind the scenes that's still an MSI that we create a wrapper over.
As per my understanding so far, to work around this issue, we need to set the
AppsAndFeaturesEntries entry in our winget manifest. In that entry, we need to declare the following:
ProductCode/UpgradeCode/DisplayVersion.
This should theoretically make winget able to correlate the EXE manifest to the MSI-based ARP entry without relying on the generic installer-type match.
Could you please try this and let me know if it helps?
Best regards,
Catalin
FOLLOW US
Get the latest news in Application Packaging