LabVIEW: remote registry access denied.

[SC-Aust]

Hi,

I’m setting up a replacement PC.

The present PC is Windows 10 Ent. Installed on it is  LabView 2017 SP1 f4 (RTE) and the program that controls the instrument the PC is attached to.  This PC was supplied to us by the company that supplied the instrument.

Due to our updated Cyber Security Policy, I need to replace the PC. One that is Cyber Secure.

I have set the new PC up with my company’s PC image using Windows 10  Ent LTSC  21H2.  I installed LabView 2017 SP1 f4 (RTE) and then the required instrument program. The company that supplied the original PC and instrument sent me installation instructions to help with the install process.

After all the required programs are installed. I can open the Program.

When I go to save settings for the program, I receive an error:

Error -604 occurred at the create Registry Key.vi

Possible reason: -  LabVIEW: Remote registry access denied.

I have signed on to the new PC with my administrator credentials.  I have the same error. ☹

I raised to   Full Control    the folders:

           c:\Program Files (x86)\HDI

           c:\Program Files (x86)\National Instruments

           c:\Program Files\National Instruments

In services, I have  RemoteRegistry   set to always start

I have the same error ☹

I need help!

[GerdW]

Hi Aust,

---

@SC-Aust wrote:

When I go to save settings for the program, I receive an error:

Error -604 occurred at the create Registry Key.vi

Possible reason: -  LabVIEW: Remote registry access denied.

I need help!

---

There are two parties that could help you:

1. The provider of that software by changing its product to NOT write to the registry - or only use "accessable" registry folders. (Further testing required.)
2. Your IT department by allowing more access to certain registry folders. This will reduce your "cyber security"…

The general recommendation is: don't use the registry to save settings of your (or your supplier's) software. Microsoft does/will apply more strict access rules than was applied at Win95 times!

(When your supplier needs ways to apply theft protection (aka license management) to their software then they should use some available 3rd party tools, like those from WibuSystems.)

[SDJsowhat]

Hi GerdW,

I don't know if you work for National Instruments or not but I have the same problem.  Do yu know of NI have updated their software to not involve a PC's registry.  This is 2026, surely they should have done something by now?  By the way, I am using a Windows 11 laptop , which is my own, I am the administrator.  The temperature and humidity data logger is work equipment, but I have loaded the software on my personal laptop.

 

 

[GerdW]

Hi SDJ,

---

@SDJsowhat wrote:

I don't know if you work for National Instruments or not

---

I don't work for/at NI/Emerson.

---

@SDJsowhat wrote:

The temperature and humidity data logger is work equipment, but I have loaded the software on my personal laptop.

 

---

Who created this software?

It doesn't look like coming from NI…

[rolfk]

---

@SDJsowhat wrote:

Hi GerdW,

I don't know if you work for National Instruments or not but I have the same problem.  Do yu know of NI have updated their software to not involve a PC's registry.  This is 2026, surely they should have done something by now?  By the way, I am using a Windows 11 laptop , which is my own, I am the administrator.  The temperature and humidity data logger is work equipment, but I have loaded the software on my personal laptop.

---

This is not about LabVIEW itself! The application build in LabVIEW tries to access a protected part of the registry that only can be accessed with elevated rights or special user accounts. So you have to contact whoever wrote that software and used the Registry VIs to do something with it.

Windows security is tightened up again and again and various parts that could be read or written too in the past will now generate errors when not accessed with elevated rights. And no, elevated rights is not the same as running under an Administrator account. Even under an Administrator account you explicitly have to start an application with "Run as Administrator" in order for Windows to consider it elevated. Several hives in the registry are not accessible anymore for writing or even at all, if the process in question is not explicitly elevated or running as System Service.