NI Software Crashes During Start Up

Updated May 24, 2019

Reported In

Software

  • Measurement & Automation Explorer (MAX)
  • LabVIEW 2016

Operating System

  • Windows

Issue Details

  • When I launch my LabVIEW 2016 program, the environment crashes before loading, and gives me an Exception: Unknown (0xC06D007E) error or a message that says that the api-ms-win-crt-runtime-l1-1-0.dll file is missing. I have tried multiple times to launch LabVIEW 2016 with no success, and have verified that my software is properly activated. Why is this happening, and how do I resolve it?
  • NI MAX is crashing when it is first opened. I've tried reinstalling the program, but this hasn't worked. I still always get this error code: Exception: Unknown (0xC06D007).

Solution

This error could occur for the possible reasons below:
  • Beginning in 2016, some NI-released products are built with Visual Studio 2015, which relies on sections of the Universal C Runtime in Windows. Some versions of Windows do not contain the necessary sections of the Universal C Runtime, or contain the wrong version for Visual Studio 2015. Try manually installing update for Universal C Runtime in Windows from Microsoft's website.  Note: To install this update, you will need Windows Update on your system. 
  • This error could be given because a previous version of the Microsoft Vision C++ is in collision with the one used correctly in your Labview. Ensure that no other version of Microsoft Vision C++ is aleady installed as this program could be using the previous version of Microsoft Vision C++.
  • This error could occur if drivers are not properly installed. Generate a MAX tech report in order to look over what software is installed on your computer. Use the report to verify that all drivers are properly installed. If you do not have all needed drivers. Install the ones that are missing.

Additional Information

This error is known to happen with multiple versions of LabVIEW and NI MAX; most commonly on Windows 7 SP1, Windows 8.1, Windows Server 2012 R2, and Windows Server 2008 R2 systems, but has been seen on Windows Embedded 7 systems as well.

WAS THIS ARTICLE HELPFUL?

Not Helpful