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

Recent posts

#31
That's interesting it's requiring a manual uninstall. Curious if you currently have the 32-bit version installed? Maybe that's why it wants a manual uninstall since we would default to the 64-bit
#32
I just remembered to check Task Scheduler to see when Patch My PC - Self Updater kicks off. I saw that it's scheduled to start at 7 pm daily, with no repeat.

My PC is scheduled to wake-up from hibernation also at 7 pm, so I'm thinking that explains why Patch My PC doesn't self update on that PC - it's not quite awake when the self updater kicks off. So I've changed my PC's wake-up time to 6:45 pm daily and will wait to see if that resolves it.
#33
I just noticed that there was a new update (ver. 5.4.0.0), which I installed via the About page. The latest version was updated automatically on my laptop, but did not update automatically on my desktop.

I've checked the settings window, but didn't see where I could enable or disable automatic updating.

Why would Patch My PC update itself automatically on one PC but not on another PC, even though both are configured with identical settings?

See attached diagnostic file.
#35
I personally appreciate Patch My PC for working around their lack of standards. I have be trying to work around this for now with the detection mod and I noticed if I try to replace the MSI with a newer version or create a second custom app for GP, I am told that there is already 3.2.8 installer. Even that would be useful, as now I need to completely delete the app from the Portal, Publisher, and app catalog and remake it (and somehow retain my additiona command switches). Tips on that are welcome as well. Either way, thanks for coming up with good workarounds.
#36
You are correct, Palo should be versioning their software correctly, and we recommend customers reach out to Palo about this. Until the installers change, we are planning to implement some improvements to detection for these apps anyway.
#38
Just to keep the responsibility on the right side, shoudn't Palo Alto be making these properly versioned? It seems like Palo Alto should be releasing their products with standard dot releases, and Patch My PC should need to work around their lack of proper version control. Am I wrong, here?
#39
Hi all,

using Home Updater v5.3.3.0 the update from Inkscape 1.4.0 to 1.4.2 fails.

Here's the relevant part of the log:
[2025-11-07 16:02:43]  DEBUG  [Inkscape]: Started downloading: 'https://media.inkscape.org/dl/resources/file/inkscape-1.4.2_2025-05-08_ebf0e94-x64.msi'.
[2025-11-07 16:02:45]  DEBUG  [Gpg4win]: 'C:\ProgramData\PatchMyPC\Gpg4win-4.4.1.exe' has been removed.
[2025-11-07 16:03:18]  DEBUG  [Inkscape]: File 'C:\ProgramData\PatchMyPC\Inkscape-1.4.2.msi' downloaded successfully.
[2025-11-07 16:03:18]  DEBUG  [Inkscape]: Started installing 'C:\ProgramData\PatchMyPC\Inkscape-1.4.2.msi' with arguments '/qn ALLUSERS=1 REBOOT=ReallySuppress'.
[2025-11-07 16:03:22]  ERROR  System.InvalidOperationException: [Inkscape]: Failed to install application: 1603 .
   at ModernHomeUpdater.ClientApp.Services.Implementations.InstallationManager.InstallApplicationAsync(InstallCommandArgs installArgs, IProgress`1 progress, CancellationToken cancellationToken)
[2025-11-07 16:03:22]  ERROR  System.InvalidOperationException: [Inkscape]: Failed to install application: 1603 .
   at ModernHomeUpdater.ClientApp.Services.Implementations.InstallationManager.InstallApplicationAsync(InstallCommandArgs installArgs, IProgress`1 progress, CancellationToken cancellationToken)
   at ModernHomeUpdater.ClientApp.ViewModels.ApplicationViewModel.<>c__DisplayClass86_0.<<InternalApplicationUpdateAsync>g__InstallAppAsync|0>d.MoveNext()
[2025-11-07 16:03:22]  ERROR  Failed to update application due to error [Inkscape]: Failed to install application: 1603 ..
[2025-11-07 16:03:22]  INFO  Start update for IrfanView application...

When updating manually, the following message presents, which may be causing the silent install to fail.

1)

Clicking "OK" does not trigger the uninstall, instead it leads to:

2)

After uninstalling 1.4.0 manually (over appwiz.cpl), Home Updater still detects Inkscape 1.4.0 and the update to 1.4.2 succeeds.

#40
After KeePass got updated to the latest version this month our users reported that they could not access the application anymore. Seems like the Start menu shortcut got removed.

New installation of the last MSI does create the shortcut so it seems it only gets removed when updating from a older version.

For now we re-created the shortcut manually for all our users as they were all not able to use the application.