LabVIEW 2010 SP1 may not cleanly shut down

[Unplugnow]

Occasionally LabVIEW 2010 SP1 (32-bit, running on Windows 7) will appear to "hang" when the "Getting Started" window is closed.  The window disappears but the shortcut icon still appears in the Windows toolbar in the bottom of the screen.  Right-clicking and selecting "Close Program" does not work and Windows seems to think any VIs that have been recently closed are still open.  The program is still in the list in Task Manager and it can successfully be shut down all the way from there.

This is more of an annoyance than an operational issue (I think) - is there something I am doing (or failing to do) that causes this problem? 

Thanks in advance.

[smercurio_fc]

There's a few basic things you can try:

• Delete the LabVIEW.ini file and then start LabVIEW.
• Check to see if you have the palettes set up to load during launch. If you do, do you have any links to network folders?
• Do you have custom probes?
• Have you specifically disabled any services? If so, which ones? Try turning them back on one at a time to see if that makes a difference.
• Check to see if your anti-virus program is interfering.

[Unplugnow]

This is the third clean, out-of-the-box install of LabVIEW that I have seen this happen with, two of my own and one of a team member here.  There are no virus programs installed, and all that is being requested of LabVIEW is to 1) open 2) open a basic, hardward-free vi, make changes, then close LabVIEW.

FWIW, when this problem occurs, LabVIEW.exe does not go away even after waiting 16 or so hours.

Before I do something "basic" like deleting the LabVIEW .ini file and starting LabVIEW, I need to know why I am doing it.

Thanks.

[Blayne_K]

Hello Unplugnow,

Deleting the .ini file will not cause any issues in terms of being able to reload Labview it will simply restore the default settings for Labview which will insure that there were be no data corruption issues. I have tried this procedure on my side with no issue although I would recommend copying the .ini file to another directory in case you need to recover this information at a later time. 

To another note, does this issue arise when you are opening a particular VI, or does it occur when you are simply opening and closing Labview?

Best,

Blayne Kettlewell

[Unplugnow]

My colleague and I are working on different projects - we are not using the same in-house VIs. I have not noticed if the problem is tied to any specific LabVIEW VI.