Jul 16th, 2026, 8:25am
Welcome, Guest. Please Login or Register.
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print
   Author  Topic: Query Regarding CHECK_FOR_NEW_VERSION Behavior in  (Read 285 times)
Query Regarding CHECK_FOR_NEW_VERSION Behavior in
on: Jun 16th, 2026, 11:05am
Quote Quote  Modify Modify

Hello Team,
 
We have observed a change in the behavior of the CHECK_FOR_NEW_VERSION=0 parameter between versions 6.3.10.0 and 6.4.2.0 and would like to confirm whether this is an intended change.
 
In version 6.3.10.0, when the application is installed with CHECK_FOR_NEW_VERSION=0, update checks are successfully suppressed. This is reflected in both the shortcut configuration and the corresponding registry entry.
 
However, in the latest version (6.4.2.0), even when CHECK_FOR_NEW_VERSION=0 is passed during installation, update checks are not being suppressed. The registry key is present, but updates remain enabled in the shortcut.
 
During our investigation, we found that the behavior works as expected when the registry path is changed from:
HKLM\SOFTWARE\FabulaTech\USB for Remote Desktop Workstation
to:
HKLM\SOFTWARE\FabulaTech\USB for Remote Desktop (Workstation)
 
The addition of the brackets in the registry key name appears to resolve the issue.
 
Could you please confirm the following:
Is this registry path change an expected modification in version 6.4.2.0?
Is this a known issue that will be addressed in a future release?
Should we handle the creation/modification of the registry key with the bracketed name as part of our post-installation process going forward?
 
Thanks & Regards,
Meena Prabhakaran
IP Logged
Re: Query Regarding CHECK_FOR_NEW_VERSION Behavior
Reply #1 on: Jun 16th, 2026, 1:50pm
Quote Quote  Modify Modify

Dear Meena Prabhakaran,
 
Thank you for bringing this issue to our attention.  
 
We will test this in our lab in a moment and let our developer know if the issue is confirmed.
IP Logged
Re: Query Regarding CHECK_FOR_NEW_VERSION Behavior
Reply #2 on: Jun 16th, 2026, 2:42pm
Quote Quote  Modify Modify

Dear Meena Prabhakaran,
 
We have confirmed that this problem exists within the latest build, and the behavior is the same in our lab.  
 
I created the task #24339 for our developers to investigate and fix this issue in our next update.  
 
It is unclear if the change was intentional or not at the moment, but for now you can change this option in the registry by modifying the path or unselecting this option in the program preferences.
IP Logged
Pages: 1  Reply Reply  Notify of replies Notify of replies  Print Print

No topic | Next topic