Question
Why am I Unable to set or access registry values from Kaseya scripts on 64-bit systems?
Answer
64-bit Windows isolates registry usage by 32-bit applications by providing a separate logical view of the registry. Since the Kaseya agent is a 32-bit application, it is not able to directly access the registry.
New script commands have been added to access the registry on 64-bit Windows using the re-director.
Here is a possible workaround for v5.1 and below: -
1) from a 64-bit system, run 64-bit regedit.exe (%windir%\sysnative\regedit.exe) and create a .reg file with the required values
2) from the script, write the .reg file to the machine and execute a shell command to import it (something like "%windir%\sysnative\regedit.exe /s <filename>")
More Information
Applies To
Kaseya Server / Agent v5.1 and below
Why am I Unable to set or access registry values from Kaseya scripts on 64-bit systems?
Have more questions?
Was this article helpful?
Provide feedback for the Documentation team!
Browse this section
- #vPatchConfiguration.LanCacheUNCPath# variable not storing value
- Agent Procedure Error "The File Exists"
- Agent procedure to Collect Windows Event Logs - Application and System Logs
- Agent Procedures - deleteDirectory with "recursively delete" option fails on agents with Italian Windows installation
- Agent Procedures - Execute User Command.
- Agent Procedures - WriteFile() fails to write files to C:\Windows\system32
- Agent Procedures appear to be scheduled by a user that is no longer with the company
- Agent Procedures are not approved even though they were created by a "Master" user.
- Agent Procedures show as Pending Approval
- Agent Procedures taking longer to execute
- See more