Hi,
Thank you for your enquiry.
This is a known issue with the ReadRegistryKey() in version 4.21 (in fact, this function has never operated correctly, but the problem has only been reported recently).
Our developers have incorporated a fix for this issue in the forthcoming Service Release 3.
One workaround would be to export the details of the target registry key to a text file using batch commands. For example, if you run a batch file with the following command:
Code:
REGEDIT /E C:\info.reg "HKEY_LOCAL_MACHINE\SOFTWARE\Digital Workshop\Opus Pro"
A text file named info.reg is created in the root of the C: drive containing the following information:
Code:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Digital Workshop\Opus Pro]
"Version"="2002"
"Application Path"="C:\\PROGRA~1\\ILLUMI~1"
You could then use Read File and string functions to parse out the required information.
Kind regards,