LabVIEW opens new blank vi when attempting to exit

[Dpete]

I've had this problem on a few machines intermittantly since we migrated to 2012.  We can close out all of the VIs and get back out to the "welcome" screen.  but upon attempting to exit that screen either by file\exit or the red X it instead opens a new blank vi.  when it starts doing this it continues until labview is aborted by end process tree through task manager. (windows 7) Just end task on the application causes the same behavior as trying file exit.  I have not seen any other reference to this in postings, yet we have it on multiple machines.

[JÞB]

Are you sending in the reports????  Does LabVIEW open a warning screen on next launch?

[Bublina]

This happened to me too, just like it started it stopped after some time 🙂 I noticed LabView closed itself properly when you used standard file-exit in some opened VI or project browser.

[Dpete]

Labview does not throw a warning on next launch.  LabVIEW apparently does not believe it has a problem worth reporting.

[Jeff-P · Accepted solution]

Hi everyone,

We are aware of this issue and are working to resolve it (it is being tracked via CAR 386855). The problem is related to the Getting Started Window, which can get into a state where it incorrectly handles errors and fails to launch. When it fails to launch, it launches a blank VI, which is why you are seeing this behavior. The issue is constrained to the Getting Started Window and will not affect other parts of LabVIEW.

Bublina and Dpete, I am PMing (Personal Messaging) you a version of the Getting Started Window which contains a fix for this problem. Please follow the instructions in that message and see if the problem is fixed for you. Please let me know the results, and if the fix does not work, I will work with you to further troubleshoot the behavior.

Regards,

Jeff Peacock 

Product Support Engineer

LabVIEW R&D

Certified LabVIEW Developer

[Dpete]

At this point I do not know what triggered the behavior.  It is an intermittent fault in my book.  I spent some time this morning trying to get it to recreate.  I have now installed your fix.  I will run with it for a while and see if it reoccurs.  Without being able to retrigger it at will, I am not sure if we have a fix though.

[Rax]

I am having this problem as well, can you give me the fix?

[Dpete]

It has been over a month now with no occurrences.  I am willing to call it a solution now.

Thank you.

[crelf]

I'm using LabVIEW 2012.0.1F1 (32-bit) and I'm seeing this behavior. Did the new version of the GSW not make it into SP1? Is there a workaround?

[Jeff-P]

Hi crelf,

Unfortunately that fix did not make it into 2012 SP1. I have PMed you the fixed version and the instructions for installing it.

Let me know if you are still having the issue!

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments