• 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


Anyone running into issues with latest "FileZilla Client 3.58.0" getting a 403 error on download when try to import via "WSUS Package Publisher"
I dug up what I think are URLs download from which work fine in a browser.


Thanks in advance
With Citrix Workspace release on 7/29 seems some changes how Workspace is targeted changed.

With Workspace version prior to (non LTSR)  4 conditions for patch to be installable.

1. RegValueExists Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\CitrixOnlinePluginPackWeb" Value="DisplayVersion" RegType32="true"

2. RegSz Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\CitrixOnlinePluginPackWeb" Value="DisplayName" Comparison="Contains" Data="Workspace" RegType32="true

3. RegSzToVersion Key="HKEY_LOCAL_MACHINE" Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\CitrixOnlinePluginPackWeb" Value="DisplayVersion" Comparison="LessThan" Data="" RegType32="true"

4.  WindowsVersion Comparison="GreaterThan" MajorVersion="6" MinorVersion="1" ProductType="1"

With 21.7.044 there seems to be some additional conditions that also target off "HKLM\SOFTWARE\Citrix\ICA Client\AutoUpdate\Commandline Policy"  & "HKLM\SOFTWARE\Policies\Citrix\ICA Client\AutoUpdate" LTSROnly=true conditions.

Overall some thoughts on regular Workspace vs LTSR Workspace.

If LTSROnly=true that indicates either a GPO is set or command line was used to limit auto upgrades to LTSR versions.  If PatchMyPC upgrades LTSR Workspaces to regular Workspace installs that is ignoring the configured setting installer or admins are configuring. 

Our environment for example majority of our Workspace installs are LTSR as we need the cerification and stability of LTSR over cutting edge feature of Workspace.  In the past I've modified the Workspace installable rules to avoid patching our LTSR installs. 

Wanted to start a discussion and suggest that targeting of Workspace & Workspace LTSR with different approach.  What may make sense is if any LTSROnly=false or values do not exist then Workspace patch permitted.  If LTSROnly=true then only LTSR installs are permitted.  Customers like us would need to have both Workspace & Workspace LTSR patches approved, but it keeps the Workspace on Workspace and LTSR on LTSR. 

PatchMyPC with WSUS

DCU 4.2.0 has installable rule where DCU has to be 3.0 or higher to install.  Do we know why the 3.0 or greater limitation exists?  I could adjust the rule to upgrade legacy versions, but rather not if known issues with legacy upgrades.

Somewhat related there are 2 version of DCU.  Classic & UWP DCU 4.2.0 only installs on Classic.  Any plans for UWP DCU update?

From release notes:

PDFCreator 3.0 requires the .Net Framework 4.5.1 and therefore Windows Vista or above. Windows XP is no longer supported. If you need Windows XP support, please use PDFCreator 2.x instead.


PDFCreator will install if requirements are not met, but will error when running application.  Can PatchMyPC detection account for .NET Framework 4.5.1 requirement?   Application failures can be high if upgrading from older PDFCreator prior to 3.0 with .NET 4.5.1 or newer.
Healthcare Messaging App TigerConnect's healthcare messaging app allows you to take advantage of unprecedented cost savings, improved clinician morale and better health outcomes.


The MSI that were version and older had issue where when installed from local system account application wouldn't run from non-admins.   Not tested if issue still exists in latest version.  EXE version does not have this issue. 

InstallShield MSI extracting installer.

TigerText_Installer_x86.exe /S /V" /QN " should work.   Exitcodes 0 & 3010.