LabView 2014 has to search for many files on startup

[jeepers52004]

I have recently installed LabView 2014 on a laptop that's not had any version of NI software installed.  When starting LabView, I get more than a few popups for file searches.  A few screen captures are attached.  I also get these file searches the first time I try to save or access the file menu from an open VI.  I completed a software repair from MAX but this did not solve the issue. 

I have installed LabView on a couple other laptops and they don't seem to exhibit this same condition.

Thoughts?

[jeepers52004]

I'm attaching a screenshot showing the file LabView searches for the first time I select the file menu of an open project.  So far, LabView always finds the files but I'd like to get things moved so it doesn't take so long to open and work with LabView.

Thanks

Michael

[natasftw]

How are you opening LabVIEW?

[jeepers52004]

---

@natasftw wrote:

How are you opening LabVIEW?

---

I'm opening LabView via the shortcut that was created on the desktop when the software was installed.

[altenbach]

---

@jeepers52004 wrote:
I'm opening LabView via the shortcut that was created on the desktop when the software was installed

---

The LabVIEW installer does not create a shortcut on the desktop. Could it be that you are clicking on some manually created old shortcut that points to a a partially unistalled old LabVIEW version?

Right-click the shortcut and see where it points to.

What happens in you click on the new LabVIEW shortcut in the start menu instead?

[jeepers52004]

---

@altenbach wrote:

---

@jeepers52004 wrote:
I'm opening LabView via the shortcut that was created on the desktop when the software was installed

---

The LabVIEW installer does not create a shortcut on the desktop. Could it be that you are clicking on some manually created old shortcut that points to a a partially unistalled old LabVIEW version?

Right-click the shortcut and see where it points to.

What happens in you click on the new LabVIEW shortcut in the start menu instead?

---

My mistake then.  I must have created the shortcut and it's pinned to the task bar.  Attached is a screenshot of the shortcut path.  Opening from the start menu produces the same results.

[jeepers52004]

---

@altenbach wrote:

---

@jeepers52004 wrote:
I'm opening LabView via the shortcut that was created on the desktop when the software was installed

---

The LabVIEW installer does not create a shortcut on the desktop. Could it be that you are clicking on some manually created old shortcut that points to a a partially unistalled old LabVIEW version?

Right-click the shortcut and see where it points to.

What happens in you click on the new LabVIEW shortcut in the start menu instead?

---

Also, this is the only version of LabView ever installed on this machine so it really can't be an old shortcut.

[billko]

---

@jeepers52004 wrote:

---

@altenbach wrote:

---

@jeepers52004 wrote:
I'm opening LabView via the shortcut that was created on the desktop when the software was installed

---

The LabVIEW installer does not create a shortcut on the desktop. Could it be that you are clicking on some manually created old shortcut that points to a a partially unistalled old LabVIEW version?

Right-click the shortcut and see where it points to.

What happens in you click on the new LabVIEW shortcut in the start menu instead?

---

Also, this is the only version of LabView ever installed on this machine so it really can't be an old shortcut.

---

I have to say that the only reason it would have to search for stuff is because it can't find it in the directory it was looking in.  The only reason why it would search for stuff in vi.lib is because the base files for LabVIEW was somewhere it wasn't expecting.  The only reason that would be is because there was a previous installation of LabVIEW on there.  Or maybe remnants of a failed install that no one told anyone about.

Big question:

WHERE IS LABVIEW FINDING THESE FILES???

[altenbach]

@jeepers52004 wrote:

---

Also, this is the only version of LabView ever installed on this machine so it really can't be an old shortcut.

---

Did you try to repair the LabVIEW installation? (you said something about MAX. I am talking about the windows software control panel. I am not sure what you did in MAX to "repair")

Is this a site license or an individual license?

Are you running any unusual antivirus or other security software?

If you look in the NI license manager, what flavor of LabVIEW (base, full, pro, etc.) does it say you have activated?

[jeepers52004]

I'll have to video the screen to capture exactly where it find each file because those locations disappear when the file is found and the next one is being searched for.

This laptop was used by an intern over the summer and LabView wasn't installed.  The laptop had the drive erased and a new image installed before deploying to our department.  We are the only users of LabView and owners of the purchased software (physical media and license keys.)   So no other version of LabView has ever been installed, 99% certainty.

How can I diagnose if something failed when I installed Labview and/or how can I repair what's existing hopefully without uninstalling and reinstalling everything?

I will pick one specific file that requires significant search time and locate it myself on the drive.  With that info, is it possible to relocate those files to the correct location? 

---

@billko wrote:

---

@jeepers52004 wrote:

---

@altenbach wrote:

---

@jeepers52004 wrote:
I'm opening LabView via the shortcut that was created on the desktop when the software was installed

---

The LabVIEW installer does not create a shortcut on the desktop. Could it be that you are clicking on some manually created old shortcut that points to a a partially unistalled old LabVIEW version?

Right-click the shortcut and see where it points to.

What happens in you click on the new LabVIEW shortcut in the start menu instead?

---

Also, this is the only version of LabView ever installed on this machine so it really can't be an old shortcut.

---

I have to say that the only reason it would have to search for stuff is because it can't find it in the directory it was looking in.  The only reason why it would search for stuff in vi.lib is because the base files for LabVIEW was somewhere it wasn't expecting.  The only reason that would be is because there was a previous installation of LabVIEW on there.  Or maybe remnants of a failed install that no one told anyone about.

Big question:

WHERE IS LABVIEW FINDING THESE FILES???

---