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

Recent posts

#81
That extra info is helpful, and we are hoping to utilize it to better support this app in the near future! Thanks!
#82
It's probably a registry issue, but can you please share a screenshot?
#83
Unfortunately it's not fixed, today PMPc is detecting VC++ 2013 v12.0.40664 as an "outdated" version of VC++ 2015-2022 (which currently is 14.50.35710, but PMPC thinks it's 14.44.35211.0).
#84
Patch My PC Home Updater is showing 4 apps out of date. But I have checked each one and they are up to date. They are the same versions that Home Updater wants me to update to.

I don't know if this is a bug in PC Home Updater, a registry issue, or whatever. Any ideas how to fix this?
#85
This is now fixed in the home updater v5.3.2.0 :)
#86
Hi Niclas,

We'd love to support "update-only" behavior on macOS, but the limitation comes from Microsoft Intune, not from Patch My PC.

On Windows, we rely on Intune's Win32 app model, which allows custom requirements and detection scripts to check whether an app is already installed before updating. macOS app deployments in Intune don't have those same capabilities, there are no requirement scripts available for macOS apps, so we can't distinguish between "install" and "update" in the same way.

That said, macOS app deployment through Patch My PC Cloud is already available, and customers can absolutely use it today. As a workaround, you could assign macOS apps as "Required" to your target groups, which will make sure the apps are always up-to-date. To be clear, though, this is not "Update-only" because it will also install the app if it is missing.

Once Microsoft expands Intune's macOS app model to include requirement scripts or similar functionality, we'll add full update-only support.

Hope this clarifies the topci for you :)
#87
My Patch My PC Home Updater still shows the same message!
#88
We're also having issues with this, where it perceives 6.3.3-676 to be the same as 6.3.3-633, and therefore doesn't push out any updates until it hits 6.3.4

One "workaround" we've found is to change the app itself to use a custom detection method:

Path: HKEY_LOCAL_MACHINE\SOFTWARE\Palo Alto Networks\GlobalProtect\PanSetup
Name: CurrentVersion
Method: String Comparison
Operator: Equals
Value: 6.3.3-676 (or your version number)

The downside with this that it will treat this as a first-time deployment and ignores the update rings we have in place - something that for a business critical app just doesn't work for us.
#89
Hi
Do you have any roadmap for Mac support to update already installed applications?
Where is the problem laying getting the support?

Cheers
Niclas
#90
Quote from: JamieMc on August 22, 2025, 01:47:03 AMJust to make you aware, all JetBrains software (PyCharm, CLIon, InteliJ etc) that is on version 2025.2 doesn't deploy start menu shortcuts.

This appears to be a bug caused by JetBrains them self due to the install location changing from %programfiles(x86)%\JetBrains to %Programfiles%\JetBrains.
Melon Playground
This is my fix below, not the prettiest & you might need to change it depending on the apps you have installed.
$StartMenu = 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs'
$AppPath = 'C:\Program Files\JetBrains'
$FirewallRules = Get-NetFirewallRule


if(Test-Path -Path $AppPath)
{

    $apps = Get-ChildItem -Path $AppPath |Select-Object -ExpandProperty Name

    foreach($App in $Apps)
    {

        $AppName = $App.Split(" ") | Select-Object -First 1         
        $AppExe = $AppName + '64.exe'

        if($AppName -eq 'IntelliJ'){ $AppExe = 'idea64.exe'}

        if(Test-Path "$StartMenu\$AppName.lnk"){Remove-Item -Path"$StartMenu\$AppName.lnk"}

        $shell = New-Object -ComObject WScript.Shell
        $shortcut = $shell.CreateShortcut("$StartMenu\$AppName.lnk")
        $shortcut.TargetPath = "$AppPath\$app\bin\$AppExe"
        $shortcut.Save()   

        if(!($FirewallRules | Where-Object {$_.DisplayName -eq $App}))
        {
       
            New-NetFirewallRule -DisplayName $App -Direction Inbound -Program $shortcut.TargetPath -RemoteAddress Any -Action Allow -Profile Domain

        }
       

    } # End Foreach Region


} # End If Region
I have same question!