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

Recent posts

#1
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.
#2
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.
#3
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/
#4
Hi sw-deploy,

Thanks for reaching out about the Adobe update failures with error 0x80240017. What we are seeing here is related to an issue on Adobe's side with how their MSP updates report applicability. Even when the update is actually applicable, the Windows Update Agent or Configuration Manager can incorrectly determine that it is not, which results in the failure you are seeing.

Recommended Resolution

To work around this:
Enable Manage Client-Side Logging for the Adobe update
- https://patchmypc.com/kb/right-click-options-available-updates/#h-manage-installation-logging

Republish the update after enabling this option
- https://patchmypc.com/kb/when-how-republish-patch-my/

Deploy the newly republished update
 
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.

If you are still experiencing issues after attempting that resolution, please open a support case with us here: https://patchmypc.com/technical-support and include the logs listed here: https://patchmypc.com/kb/collect-sccm-intune-logs/#h-third-party-software-updates-failing-to-install-on-client-devices

Thanks!
#5
Hello guys!
Since the previous Acrobat Reader update (26.001.21529) we have the issue, that many devices cannot install the update through MEMCM.
The same issue with update 26.001.21662 now.

The weird thing is, when I start the update manually, it works without any error.
Currently we have around 1000 devices with this issue.
Any idea what this could cause the problem?
Thanks
#6
Quote from: matt84 on April 10, 2026, 10:07:34 PMPatch my PC Home Updater updated CPU-Z and HWMonitor recently. Did Patch My PC download the compromised installers?

fnf https://gist.github.com/N3mes1s/b5b0b96782b9f832819d2db7c6684f84
Check the exact CPU-Z and HWMonitor versions that Patch My PC installed. If they were downloaded during the compromise window, compare their hashes with the malicious hashes from the advisory. The update date is the key factor.
#7
Unfortunately, the Revit 2025 updates are larger than 2GB. 3rd party WSUS updates have a maximum size of 2GB, as they are stored in a CAB file and the maximum size of a CAB file is 2GB. Due to this size limitation, we are unable to add Revit 2025 to our catalog and will likely be unable to ever add them (to WSUS) due to that file size restriction within WSUS.
#8
We are planning to upgrade from Revit 2024 to 2025, and I noticed that there is no Revit 2025 update in Publisher. Autodesk support (https://help.autodesk.com/view/RVT/2025/ENU/?guid=RevitReleaseNotes_2025updates_html) shows 9 updates since the release. I see most of the Autodesk products have the normal progression of years, so not sure why this is missing 2025. Is this just as simple that I need to submit a product request?
#9
I can confirm seeing this behavior with some applications as well. It might be worth mentioning which apps leave shortcuts behind, as the result could depend on how the installer creates the desktop icon.
#10
Thanks, but as I said in my original post, the hourly checks are disabled. Despite that, it adds a task to do exactly this every 2 hours.