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

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Andrew Jimenez (Patch My PC)

A fix just rolled out in today's catalog update, we had to fall back to a file version detection if the registry version detection does not work. This seems to have been a problem since they switched over to the MSI based installer. We modified the existing updateid, so you will want to republish https://patchmypc.com/when-and-how-to-republish-third-party-updates the Nextcloud update to make this change active, otherwise all future releases should be fixed as well.
We were able to replicate this and will work to resolve this week.
Thanks for the report, we will see if we can replicate and fix this issue.
This should be updated in today's catalog release. Please reach out if you still run into issues!
Interesting, I think we'll need to collect logs for this can you please open a support case here: https://patchmypc.com/technical-support
Please include the following logs from a device where the software is not showing as applicable:
%WinDir%\CCM\Logs\PatchMyPC-ScriptRunner.log (If exist)
You need to run Get-WindowsUpdateLog on Windows 8.1 and newer in PowerShell.

What version of Notepad++ are you currently running? I just checked on my test box and it is 8.1.1 x64 is showing as applicable for me.

Here is the applicability rules for Notepad ++ 8.1.1 x64. If you can check that these registry values exist:
  <bar:RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Notepad++" Value="DisplayVersion" />
  <bar:RegSzToVersion Comparison="LessThan" Data="" Value="DisplayVersion" Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Notepad++" />
  <bar:WindowsVersion Comparison="GreaterThan" MajorVersion="5" MinorVersion="1" ServicePackMajor="3" />

Can you confirm the deployment method? WSUS/ConfigMgr App/Intune App?
You will likely need to recreate the code-signing cert on the new box. Our "Modify Published Updates" wizard has a nice option for re-signing your existing updates with the new cert once you get that in place: https://patchmypc.com/modify-published-third-party-updates-wizard#topic3
If you are using the ConfigMgr Apps, or have Patch My PC trigger the SUP sync, you will need the ConfigMgr client installed on the SUP (We use the dlls to connect to ConfigMgr). The current release is solid  :).

If you run into any issues, feel free to open a support case with us: https://patchmypc.com/permissions-required-in-sccm-for-base-installation-packages-from-patch-my-pc
or schedule a review session with an engineer: https://patchmypc.com/environment-review-call
You will need to install Patch My PC on the new SUP server. You can transfer the settings using the backup and restore options: https://patchmypc.com/backup-and-restore-publisher-settings.
If you have ConfigMgr Apps enabled, you may also need to give permissions to the new SUP server to create ConfigMgr applications: https://patchmypc.com/permissions-required-in-sccm-for-base-installation-packages-from-patch-my-pc

Other than that, everything should continue to work as usual.
You are correct. Our new native code signing method is much less picky in terms of certificate usage.
Other users have had success by doing the following:


How are you publishing these updates? via our publisher or ConfigMgr in-console publishing?
Please recreate the detection method for this app, this issue was solved about a month ago, and the detection method just needs to be recreated. Thanks!