Jump to content

Recommended Posts


When I try to install LabVIEW 8.5.1 runtime or visa 4.1 on an Intel NUC with CPU i5 7260U I get:

Microsoft Visual C++ Runtime Library

Runtime Error!

Program ........\LV RunTime 8.5.1\setup.exe

This application has requested the Runtime to terminate it in 

an unusual way.

Please contact the application's support team for more 



Just in case I installed Visual C++ 2005 redistribution and checked under add remove programs that the Windows feature of allowing version under .net 3.5 to run was enabled.

This is not an ARM based processor so why does LabVIEW has a problem installing on the NUC?

Link to post
Share on other sites

I have 8.5.1 runtime running on win10.

The fact you can run it on a U processor tailored for mobile says I guess that the issue is not the processor but rather some other NUC issue or C++ issue.

Did someone here install LV on a NUC?

Link to post
Share on other sites

LV Runtime 8.6.1 and above works fine. Running the exe gets me to the installer panel.

LV Runtime 8.5.1 and below won't work on my NUC. Running the installer gives an error before the installer's panel is up.

There is a change in the windows environment (c++ .net ...) between the versions.

Going to work some http://www.dependencywalker.com/ magic

Link to post
Share on other sites

My NUC is running Win10 64 bit  and I installed all the updates.

The KB offers patches for win8.1, 8, vista, RT, server8 and server 2012 assuming that the issue is solved for win10 through the updates.

Should I try installing the win 8.1 64 bit patch on my win10 64bit?

Link to post
Share on other sites

I have a NUC running Windows 10 x64.  I've successfully got LabVIEW 2017 development environment installed and things seem to work well.

Link to post
Share on other sites

Same here.

It works from LV 8.6 to 2018.

But from 8.5.1 and prior to that version (8.2 tested) it is not working.

Tell me if you are able to install 8.5.1 on your NUC, just getting into the first panel of the installer

Link to post
Share on other sites

8.5 came out in 2007 and 8.2 in 2006, so they and their installer may or may not be built in Visual Studio 2005. There is a good change that they were in fact created using Visual Studio .Net 2003 or even Visual Studio .Net 2002 though that last one doesn't make to much sense as it was pretty flaky. So you may need to specifically add support for the Visual Studio 2003  C runtime library to your system. Starting with Visual Studio 2002 Microsoft deviated from the previous principle that all Microsoft C compiled programs were referencing the standard MSVCRT.dll that was also part of the Windows installed components. Instead each created application was using its own version of the C runtime library depending on the Visual C version used. Those C runtime versions often are installed in a standard Windows installation as many components that are distributed with Windows were created with various versions of Microsoft C (some pretty old). But it is very feasible to assume that Microsoft managed to extinguish in Windows 10 any application that still requires a C runtime library version prior to 2008.

It may still be present on a fresh install of Windows 10 sometimes, depending on additional installs like video or network card drivers for instance with their own specific utilities, but it is very likely that it does not come with any Visual C 2005 support or earlier. Unfortunately it is pretty much impossible to convince Visual C to not use the version specific C runtime library. Writing a new C compiler is almost easier :D. The installer will of course install the C runtime library support that LabVIEW 8.2 or 8.5 will need, but in order to install the C runtime library support for the installer itself you would need an installer for the installer. A sure catch 22 situation.

Only applications created in Visual Studio 6 can run on any Windows version without needing specific C runtime versions to be installed. But I'm sure Microsoft is considering ways to break that at some point :lol:

Edited by rolfk
Link to post
Share on other sites

Thanks rolfk!

So to sum it up, since LV 8.5.1 is using GNU C Library version 2.2.4 I should install Visual Studio 2003 (or Visual c++ distribution 64bit) and it should work?

I'll update in a few hours. Wish me luck. 

Link to post
Share on other sites

No no. Gnu C on Windows has no significant use. You might need it if you use one of the Open Source C compilers such as DevC or or MinGW or Cygwin, which are based on gcc but Visual Studio is based on Microsoft Visual C and will never use the GNU C library! :lol:


It might work with the Visual Studio 2003 runtime installer but there is no 64 bit version for that. Visual Studio 2005 was the first version to properly support creating 64 bit applications. If it works depends on what Visual Studio version was used to create the installer executable. You shouldn't need to install the entire Visual Studio software, just the redistributable Visual C runtime library for the correct Visual Studio version.


Edited by rolfk
Link to post
Share on other sites


I installed:

1. .net 1.1 (via slipstreaming)

2. visual studio .net 2003 full application (took me forever to find it)

However. LV 8.5.1 runtime keeps giving a C++ runtime error.

I went into the unpacked installer of LV 8.5.1 and found the MSI installer of the LV8.5.1 and it did run!

Not all the MSIs of the packages run. Some report a missing Microsoft component.

My app opens and hangs now which is a different behavior than before.

Visual Studio SP1 patch still can't run saying that Visual Studio itself is not installed. How do I install the runtime now that I have the IDE? I can't find the runtime.



After nstalling VS2003 IDE the VS2003 SP1 was able to run, thus, I have VS2003 runtime and .net 1.1 yet LV 8.5.1 still fails on C++ error.

The runtime MSI was able to run successfully yet I don't see National Instruments in add remove apps or the LV 8.5.1 runtime itself which is strange. 

My app still doesn't run on the NUC with Win10 64bit

Edited by 0_o
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By Yaw Mensah
      I have installed Labview 2020 on Dedian Buster using the rpm to deb conversion method via alien. Due to Architecture mismatch i deleted the *i386.rpm files before conversion.
      My Problem is that after creating a project at "Build Specification"-> "rigth click" i am only able to select "Source Distribution". Application does not show up as an option. 
      I will be grateful for any suggestions.
      Thank you in advance.
    • By javier_r
      VIPM.io now allows you to post LabVIEW Resources, Ideas, and Tools. For example, you could post a link to a video tutorial or blog article about a package. You can also post ideas, like feature requests or new tools. Best of all, package developers are notified when you post your ideas and resources, and you can comment and discuss posts with the community. Take a look at this video to learn more: https://www.vipm.io/posts/664960df-f111-4e13-989a-24be8207182d/

    • By Shuvankar Das
      I want to connect My ccd camera with labview. The details of my system is given bellow. I cannot connect it please help   OS:  WINDOWS 7, 64bit   LabView Run-Time 2013(64-bit) NI-IMAQ 4.8 NI-IMAQdx 4.3   Camera: QICAM Monochrome Cooled (QIC-F-M-12-C) Model QICAM Resolution 1392 x 1040 Sensor 1/2" Sony ICX205 progressive-scan interline CCD Pixel Size 4.65 x 4.65µm Cooling Type Peltier thermoelectric cooling to 25˚C below ambient Digital Output 12 bit Video Output FireWire (IEEE 1394b) Max. Frame Rate 10 fps full resolution @ 12 bits Pixel Scan 20, 10, 5, 2.5MHz Mount Type C-mount optical format  
    • By javier_r
      Hello everybody!
      Wondering how many people have tried the new vipm.io site. We have added a ton of features to make it easy to Discover LabVIEW Tools and there are some cool ones coming soon.
      Check it out and let me know what you think 😀

    • By DigDoug
      CLA_ATM_QMH_PRACTICE.zipHi Folks,
      I'm taking the CLA exam in a few weeks and would like some feedback on the solution I put together (attached). A few specific questions:
      Can I dump tags in the VI Documentation of the VI like I did in Error Handler - Console Error.vi and get credit since there are instructions for developers to complete this work? This would be my strategy if I run out of time. 
      Does this seem like a passing solution? Why/why not?
      Where do you think I would lose the most points in this solution?
      Any other feedback on this exam or general strategy tips are greatly appreciated!
      Best Regards,
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.