I have an issue where I need to manipulate the latency setting of a number of COM ports in windows to a value other than the default. I can successfully read the value; however when I try to write the value I get Error -601. To check that the error is related to permissions, I first changed the registry to KEY_READ. This successfully returned the current setting of the device. Secondly, I closed LabVIEW and restarted with the "Run as Administrator" option. This allowed me to read and write the registry with my existing code. While a non-administrator user can manipulate this value from a deeply buried menu, I would really like to be able to have LabVIEW change this value automatically. My first choice is to have LabVIEW make these changes silently at run time as a 'normal' user. Is there an option I am missing or different permission setup where this could happen? My second choice would be to have LabVIEW trigger the user to allow the registry change. I did a quick search and did not find any posts that related to getting Window's User Access Control dialog to allow elevated permissions temporarily. My last choice would be to have the built executable always prompt the user to "Run as Administrator". Any ideas I'm missing? Thanks for your thoughts.

You place a file <your appname>.manifest alongside the executable file with contents as pointed out in the LabVIEW help. https://www.ni.com/docs/en-US/bundle/labview/page/deploying-labview-applications-on-windows-vista-and-later-operating-systems.html Respectively LabVIEW seems to already embed a manifest file in the built executable. So you have to retrieve it, change it and put it back into the executable.

LabVIEW

Registry Edit Permissions in Windows 7 and after

Solved!

Author

Well hot diggity! I've not actually heard of the .manifest file. The help file certainly sounds like this is what I want. I'll do some digging and report back.

Thank you!

Message 11 of 11

(737 Views)

LabVIEW

Registry Edit Permissions in Windows 7 and after

Re: Registry Edit Permissions in Windows 7 and after