• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Recent posts

#41
I set "Notify Timout Configuration" under "Manage Conflicting Processes" to 5 minutes (see attachment mcp).
Then when the update appears on the client while PSPad is open the timeout is 5 hours  :o (attachment msg)!
Installed Publisher version is 2.3.2.0.
Could the latest update be the issue here?
#42
Updated the website, thank you!
BTW this website is the publisher's! https://amcrypto.jp/
And we are using the GitHub URL for the download: https://github.com/veracrypt/VeraCrypt/releases/download/VeraCrypt_1.26.29/VeraCrypt_Setup_x64_1.26.29.msi
#44
As far as I'm aware, the website for VeraCrypt is: https://veracrypt.io/

However in the Home Updater, when you click the three buttons, and go to "Open Web Page", it takes me to: https://amcrypto.jp/

Which seems like some kind of Crypto thing?

This puts doubt in my mind as to whether the download link/source is also accurate.
#45
Yes, I have the same issue on my Windows 11 installation.
#46
Hello team,

Tor Browser can not be downloaded. There is 404 response based on log.

[2026-06-20 08:49:19]  DEBUG  [Tor Browser]: Started downloading portable app: 'https://dist.torproject.org/torbrowser/15.0.15/tor-browser-windows-x86_64-portable-15.0.15.exe';.
[2026-06-20 08:49:19]  ERROR  System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found).
   at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
   at ModernHomeUpdater.Core.System.CustomHttpClient.StartDownloadAsync(String filePath)
   at ModernHomeUpdater.Core.Services.Implementations.ApplicationDownloader.DownloadAppAsHttpAsync(String pmpcName, String url, String filePath, IProgress`1 downloadProgress, CancellationToken cancellationToken)
   at ModernHomeUpdater.Core.Services.Implementations.ApplicationDownloader.DownloadPortableAppAsync(String pmpcName, String url, String filePath, IProgress`1 downloadProgress, CancellationToken cancellationToken)
   at ModernHomeUpdater.ClientApp.Services.Implementations.InstallationManager.InstallPortableApplicationAsync(InstallPortableCommandArgs args)

Thanks.
#47
Glad to hear the issue is fixed. We were made aware of this issue after working through this with a handful of customers and we have reached out to Adobe about it. We are still determining root cause, as the detection for these updates matches the rules that Adobe uses in their own catalog, and we've been using the same rule structure for over 6 years. We have yet to determine why these updates are suddenly not showing as applicable on select devices. The resolution I previously shared works because when logging is enabled, our publishing process includes a ScriptRunner as the primary installer instead of relying directly on the MSP file. Without ScriptRunner, the Windows Update Agent or Configuration Manager evaluates the MSP directly and hits Adobe's incorrect applicability logic, which causes the failure. With ScriptRunner, the applicability check is bypassed and the installation is executed, which allows the update to install successfully on applicable devices.

Please feel free to open a support case with us if you need anything further. Thanks!
#48
Hi DHammond,

Unfortunately, we are unable to support the lower version (7.4.3.4726) at this time due to the following factors:

Applicability detection will not work in this scenario as the "Newer" version uses a lesser version number.
  • Installing an older build over a newer one is ineffective. Even when the EXE installer runs and updates the version number in ARP, the actual program files are not downgraded.
  • The MSI installer fails entirely because both versions share the same ProductCode, preventing proper installation or rollback.
  • Uninstalling existing versions with a pre-script is also risky, as it can wipe configuration files that customers rely on.

Given these limitations, our best option is to wait (and hope) that the next release is higher than 7.4.3.8758, which is the latest version currently available our catalog.

We will keep monitoring this product release cycle and will offer the next version as long as the version numbers allow it. Apologies that we're unable to get this one out.
#49
I enabled the installation logging as you mentioned.
This fixed the issue.
Your solutions sounds like you already know this issue?
Do you have contacted Adobe about this problem already?

Because I am wondering, why this happens with this application / update?
We rolled out the Acrobat DC just a few month ago.
Before we used the Acrobat Classic 2020 Reader, without any issue.
#50
The version the publisher wants for 7.4.3 is wrong:

FortiClient VPN 7.4.3.8758 Rev1 (this is actually a hotfix 1.8758 release from prior to March)

When the actual current version (March Release) for the VPN only is:

FortiClient VPN 7.4.3.4726


You can also see this stated here
https://www.reddit.com/r/fortinet/comments/1t4hqe1/forticlient_vpn_743_build_numbers_not_making/