Windows 8 LabVIEW Installation Problems

[Dave_Thomson]

   I have a new HP Split running Windows 8.1.  When I install LV 2013 (software lease, with RT, FPGA, DSC, and a few other things), the computer can't boot anymore.  I managed to recover once with everything but the NI software still in place.  The next time, I installed just LabVIEW and the toolkits, but no drivers.  It rebooted fine.  Then I installed the drivers.  Back to the same problem.  I went into safe mode, but couldn't uninstall any NI software as the uninstall program kept giving error 1016.  So W8 did a "recovery" process and wiped every program I had put on since buying the computer.  I'm now trying to install LabVIEW again.

   Has anyone else run into this problem?  Is there one (or more) specific drivers known to cause it?  Any work arounds?

DaveT

[mikeporter]

Have you ever used these disks before? Do you have any sort of strange hardware in the PC? Video cards, liquid-nitrogen-cooled coprocessors, etc?

Mike...

[Dave_Thomson]

   Yes, I've used the disks repeatedly.  I suppose they could have gone bad.  I haven't used them successfully yet since these latest issues.  I could try the previous set of disks...

   The hardware is pretty current, but nothing special.  An HP "tablet"-style laptop.  Touchscreen.   A bit of a light-weight machine for LabVIEW, but it isn't my primary development computer.  Just wanted to be able to look at things once in a while...

DaveT

[Dave_Thomson]

Just as a follow up:  On my third try, I got LV to install with minimal drivers and still was able to boot the computer.  The last time, I deselected as many drivers as I could, though it was surprising how many components I was not allowed to deselect due to dependencies.  I left out motion and vision, as well as a few others.  I haven't used LV much yet on this computer, and haven't plugged any daq devices in yet, so I can't say for sure how well it worked.  It would be great if we could ever figure out what driver is incompatible...

DaveT

[Joseph-S]

Hi DaveT,

This is a known issue that has come up very recently. We are actively investigating this and a Corrective Action Request has been filed. I'll post more details as they become available. The problem is computer hardware-specific, and I have only been able to reproduce it on one out of eight unique test machines. In the interest of narrowing down the cause, I've sent you a PM requesting further information about your system. 

Regards,

Joseph

[Dave_Thomson]

Thanks for the update.  Good to know that this is being investigated.

DaveT