PDF-XChange Editor winget

[Hense]

Hi

I believe there might be some mismatch in your winget repo versions?

When trying to install "TrackerSoftware.PDF-XChangeEditor" using winget, I'm getting the following error "Installer hash does not match; this cannot be overridden when running as admin".

Looking up the latest version, then it's showing 10.2.0.384 - but it seems that it's actually your latest 10.2.1.385 getting downloaded, which maybe could explain the hash mismatch.

Name Id Version Source
-----------------------------------------------------------------------
PDF-XChange Editor TrackerSoftware.PDF-XChangeEditor 10.2.0.384 winget

Best regards

[Daniel - PDF-XChange]

Hello, Hense

I know our certificate did change just before the 385 release, but that all should have passed through fairly smoothly. I will ask our Dev team leader to check this.

Kind regards,

[Daniel - PDF-XChange]

Hello again!

After speaking with the Dev team, and some tests on our end, we can confirm that winget seems to serve the correct latest release in most cases. There may be a region error, I would need to ask you to email us, via [email protected], with a link to this topic.
If you can include a screenshot of your CMD after running this, as well as your publiuc IP address, we can check the logs and see what might have lead to this situation for you (and should be able to quickly resolve it).

Kind regards,

[Hense]

Hi Daniel

Thank you for the response.
I've sent an email to support as suggested

Best regards

[Stefan - PDF-XChange]

[urw_leoj]

Hello

I wanted to make you aware that this issue seems to happen every time a new version of a PDF-XChange product is released. For example, when Editor v10.7.1.399 was released on 26 August, installs were down for three days until Microsoft's failsafe bot submitted a pull request and a human being working for Microsoft approved the update. When v10.7.2.400 was released just today, installs once again started to fail; they are currently down until the latest bot-generated pull request is approved by an admin. I filed an issue in the WinGet PKG GitHub repository to try and expedite the pull request. Here's the link:
https://github.com/microsoft/winget-pkgs/issues/289628

We use WinGet to install several apps at this point, and none of them have had this issue once. Meanwhile, just for PDF-XChange Editor, it's happened 8 times in 2025 – once for each release, resulting in a total of 13 days of installer downtime. You can see this for yourself by reviewing your change history for PDF-XChange PRO vs the change history for the PDF-XChange PRO WinGet package (https://github.com/microsoft/winget-pkgs/commits/master/manifests/t/TrackerSoftware/PDF-XChangePRO). Reliance on WinGet is only going to increase, so this is a gap it would be in your best interest to address.

To resolve this, there are a couple of strategies that other companies use that might be worth investigating:

• Create a new, version-specific URL for each release, just for use with WinGet and other package managers. This gives you the greatest control, and will allow you to release new versions without invalidating the old hashes.
• Create your own pull requests in the WinGet PKG GitHub repository (https://github.com/microsoft/winget-pkgs/tree/master/manifests/t/TrackerSoftware), timed for when you release new versions of software, with new folders for the new versions and new manifests referencing the new hashes. This allows you to either significantly decrease the amount of time WinGet cannot install PDF-XChange products, if not eliminate the problem altogether.

In case it's not clear: we really love the product, and I want you folks to succeed. This is a sore spot for us because we are just now about to start rolling out PDF-XChange PRO to replace Acrobat Pro across the company, and it's happened twice during our pilot. Our users are very sensitive to any perceived negative experience connected to PDF-XChange products because they're all still used to Acrobat and don't like that they have to give it up. WinGet is a godsend for us, it's the only realistic mechanism my lean IT team can use to roll out software without building installers for each release...but getting errors on install across the company all at once for a major product replacement would leave a bad taste in a lot of people's mouths.

Please let me know how I can help.

[Daniel - PDF-XChange]

Hello, urw_leoj

I have done what I can today by bringing it directly to the attention of our Dev Team Lead and upper management. I cannot make any promises for what will happen going forward, until I have heard back from them.

Kind regards,

[urw_leoj]

Thank you Dan, I appreciate the quick response. I hope this can be resolved soon.

[Daniel - PDF-XChange]