07-05-2016 01:42 PM
Dear Henk
Can we have a report on the progress you have made in the past 2 years, please? In my experience this is NOT a solved issue.
I can confirm that this is STILL a problem with the installers in the Feb. 2016 issue of the Developer Suite media and Windows 8.1
The problem is that to install the software you need to have Administrator Rights wherever My Documents points to, and not just on the local machine.
Why can the directory not be selected at install time?
07-14-2016 09:05 AM
I was hoping to apply the mccracken fix (regedit) by exporting a portion of my registry and giving the user a .reg file, however, my branch has most items already set at %USERPROFILE% and I could not find a My Documents key (see attached). Or am i looking for the wrong thing? I see the "personal" key has a value of "%USERPROFILE%\documents", is that what is needed?
Anyone wish to
1. export their HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders to a .reg file
2. modify the "my documents" key value to include %USERPROFILE% (.reg is just a text file)
3. post it to this forum?
As a bonus for reading this post I'd like to point out any of the paths shown in the attachment can be entered into file explorer address bar when preceded by shell: for example
shell:personal
will take you my documents. (had to put in a code snippet because colon p kept getting converted to an emoticon)
07-19-2016 01:31 AM
Hello,
I set the value of "personal" key to "%USERPROFILE%\My Documents", which works for me.
Uli
12-15-2016 11:25 PM
I just ran into this very issue yesterday on a client site, where the installer (the LV2016 RTE "web browser plugin") fails because the My Documents folder is mapped to a network location.
Imagine my annoyance to find that not only is this issue known to NI, it has been known for SIX YEARS. Even then a CAR for the issue was only raised three years after the fact, and only because it was mentioned in the NI Idea Exchange. Another three years later and there's still no fix in sight.
For others running into this issue, I have another workaround that doesn't involve the registry, but will not suit all applications (and is a bit of extra work). In this case all I needed was the minimal LabVIEW RTE, so I repackaged it in my own installer. This involved:
Anyways it's not a perfect solution, and probably won't help the majority of people running into this problem.
04-10-2017 04:30 AM
Still no proper solutions? After all this time
@ _nick_
May be you can uncheck that it is solved? you never know that this trigger NI
Because when people see this post, they expect to see good solution.
If I summarize it corretly:
They can ask IT has to come over
Or they have to play in the registry.
Or we have to ditch the NI Installer
In my opinion one of these solutions are suitable for an application at a customer
10-18-2017 02:21 AM
..have kept an eye on this conversation too. What kind of solutions there are with the installers to solve this instead of temporary reg edit?
12-17-2018 03:37 AM
And it still appears to be an issue in the LabVIEW 2018 runtime engine installer!
12-17-2018 06:45 PM
Here's hoping it'll at least be fixed within a decade of it first being reported... I wonder if NXG suffers the same problem?
12-17-2018 07:03 PM
Can we save the goofy GIFs for facebook and keep them out of a professional forum?
07-10-2020 06:04 PM
Si funciona en 2020