01-02-2013 07:41 PM
Hello,
I'm running Windows 8 64-bit, and have LabVIEW 2012 32-bit (12.0f3). I started using it a few days ago, and was never able to shut down LabVIEW properly. I could close my projects, but when I then tried to exit LabVIEW from the home screen, the GUI simply stop responding, and I'd have to forcibly kill it. Then, I installed the latest VIPM, and noticed that I can't shut that down properly either (I believe VIPM is implemented in LabVIEW?). None of my non-LabVIEW-based programs have this issue.
Then, I tried to install OpenG from within VIPM, which launched LabVIEW itself. However, that hung at "Initializing menus".
I'm not sure if VIPM had anything to do with it, but now, I'm unable to start LabVIEW altogether. Even after restarting my machine (using the Restart option, not Windows 8's Hybrid Boot), LabVIEW would hang at "Initializing menus". Task Manager shows 0% CPU activity, and LabVIEW had only taken ~20MB of memory.
What could be the cause, and how can I fix it?
Thanks
Solved! Go to Solution.
01-03-2013 06:00 AM
01-03-2013 09:59 AM
Ok, I:
LabVIEW launches now, but I'm still unable to shut it down properly... 😞 One day it will probably refuse to launch too.
Some help please?
01-03-2013 11:40 AM
My guess would be the FPGA Xilinx tools are the root of your troubles. See here for NI product compatability with Windows 8. Did you turn off fast start?
01-04-2013 04:16 AM
Thanks for replying, Jeff.
When installing, I deselected EVERYTHING, and selected only "Ni Development Suite Core" -> "LabVIEW 2012 (English)". So, I have no other modules, no FPGA support, no drivers, no patches, no Xilinx tools.
Anyway, I tried disabling fast startup, but LabVIEW still hangs at exit.
Does LabVIEW come with a diagnostics tool/troubleshooter?
01-04-2013 09:18 AM
I would suggest working closely with your local NI support team. Most of LabVIEW has been tested out on Win 8 and is "Under Normal Support" (That means they will fix bugs found - not quite the same as "no known issues exist")
I'm sorry but, you are on the (B)leading edge here... New OS's are usually that way. figuring out what Microsoft really did is a lot more trouble than reading about what they thought they did.
I even coded a bug once
01-07-2013 04:43 AM
01-13-2013 02:17 AM
01-29-2013 02:52 PM - edited 01-29-2013 02:57 PM
I have exactly the same config and the same problem with Windows 8 and Avast 7.
Disabling Avast, I managed to close the labview's window.
Can you open examples ?
More information here
01-29-2013 06:33 PM