01-15-2014 02:32 PM
Is anyone else having the following problems? Any solutions?
LabVIEW 2013: Click Exit by any method (right click taskbar then click close, push the "x" button, file-->exit) and LabVIEW 2013 "starting" window remains open and does nothing
LabVIEW 2012: Close Exit by any method and the result is a brand new subVI
I have been resolved to close LabVIEW by ending the process. Surely I am not the only one to deal with this. I looked through forums, but only found close reference and close subVIs and what not.
01-15-2014 02:50 PM
Ctrl+Q
There is a known issue with the Getting Started Window that has another work around that should be resolved with available updates.
01-15-2014 03:30 PM
What about the LabVIEW 2012 opening a new SubVI issue. Is this known?
01-15-2014 03:42 PM
check your Private Messages
12-19-2014 01:15 PM
I realize this thread is a year old, but Labview 2012 is still doing this for me.
I'm on Windows 7 64 bit.
If I CTRL-Q the start page, it opens a new sub-vi. When I exit the sub-vi, it opens the start page. The X button in the upper right does nothing at all to the start page.
I was finally able to get it to fully quit by pressing CTRL-Q multiple times until the windows went away. Is there a fix planned for this, or is there a better way to exit that doesn't involve quitting multiple times or killing the task from the task manager.
12-19-2014 02:23 PM - edited 12-19-2014 02:23 PM
I recommend messaging Jeff P Bohrer (above) about this issue. He'll fix you right up. Muahahaha
12-19-2014 03:08 PM
@DailyDose wrote:
I recommend messaging Jeff P Bohrer (above) about this issue. He'll fix you right up. Muahahaha
He was already copied Shhhhhh....
05-18-2016 11:50 AM
I'm having this issue with LabVIEW 2011 .. why are you hiding the solution?! 😉
06-20-2016 07:59 AM
We have the same problem with Labview 2012 64bit.
If the opening screen is closed Labview starts a new VI if this VI is closed the opening screen is displayed and you keep running around in circles.
Could someone please post a usable solution for this as i get the impression this problem occurs with several Labview users.