Installing LabVIEW 2019 or DAQmax is not possible due to an issue with ni-msvcrt-2015 package

[TheHorse]

Hi.

As the title read, I've been having problems installing LabVIEW 2019 and DAQmax on my computer due to an issue with a package.

For LabVIEW I've managed to install the 2017 version by using the offline installer, but this is not working for LabVIEW 2019 and for DAQmax, both of them are giving me the same issue.

I'll put a screen shot and my errorlog, hoping somebody knows how to help a poor and unfortunate soul such as I am:

 

and error-log of the last time I've tried to install DAQmax:

Spoiler

===== 2019-Nov-24 16:37:15.967727 =====
Exception in ni::pkgclient::TransactionBase::StartInternal. Error code: -125083
Request type: 30
-125083: An error occurred while installing a package: ni-msvcrt-2015 (14.1.5.49152-0+f0)
File: source\nipkg_client\pkgclient\PluginInteraction.cpp
Line number: 239

Additional error information:
-125441: The executable returned error '1168' after running the custom execute command 'path='"C:\Users\user\AppData\Local\Temp\nipkg-e0c2-8ee0-9f6c-a57c\data\VCRunTimeInstaller.exe"', arguments='x86''.
File: C:\agent_work\17\s\nipkg\source\shared_agents\Base/ErrorHandler/ErrorInfo.h
Line number: 333



For now I've tried to disable my antivirus, I've tried updating Windows 7 (the version of Windows I'm currently using) to its last version, I've tried installing both of them offline but none of those things worked.
Thank you very much, I hope this is the right place to post this and I hope somebody can give me some advice.

[mpinzas]

Hello,

I have seen that some people had this error while trying to install new NI Software throught the package Manager. I found a Knowledge Article that explains this in the National Instuments webpage. I will attach the link 

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z0000019OIzSAM&l=es-MX

Also I found that several people had this same issue in some of the forums too. They provide a solution but this one might take more. This user had a problem with LabVIEW 2019 too. I will attach these solutions too. 

https://forums.ni.com/t5/LabVIEW/Error-While-Installing-Labview-2019/td-p/3973106?profile.language=e...

This one is not fully related to your issue but might help you as well. 

https://forums.ni.com/t5/LabVIEW/Possible-Installation-Issue-for-LabVIEW-2019/td-p/3930768?profile.l...

Hope you find this informations useful 

Regards 

Michael Pinzas 

[TheHorse]

Unluckily, nothing worked.

I've tried to install all of the updates, but I still get the same issue.

I think the issue may be in VCRunTimeInstaller.exe since it always crashes when reaching this point (with every installation or updates), but I don't know what it could be.

This is the error I get while updating:

 

[harsh1974]

DID u solve the issue I am facing the same problem ?

[dhung]

Running into the same issue but with Labview 2023 Q3. 

[rolfk]

Error -2147024110 is 0x80070312 in hex which corresponds to Windows API error 786 (x312): ERROR_ACCESS_DISABLED_NO_SAFER_UI_BY_POLICY

This basically would mean that the installer tried to access a location on the system that is not permitted by the current user policy as configured by your system Administrator.

Are you running the installation as local admin? Is your computer under special company IT administration or similar?

[dhung]

I believe I am running as Admin, but yes the computer is under special company IT administration. What is weird is that I just performed the same installation on another company laptop and it was fine. I'll have to get with our IT to help troubleshoot. 

Thank you!

[Scott_Richardson]

Hi David, newer security software being used by IT are now using advanced heuristics to evaluate actions taken by systems and their elevated processes like installers. We have heard reports of installations sometimes failing and sometimes not with a company.

Two software examples where we are starting to here customers hitting installation errors are Microsoft Smart App Control under Windows 11 22H2, and BeyondTrust, and there are likely more. If you learn more if and how your IT software might be interfering with installation, consider sharing back here or with me privately what you find.

To potentially workaround the issue that you are seeing, you might be able to manually install the latest Visual Studio 2015, 2017, 2019, and 2022 runtime from Microsoft Visual C++ Redistributable latest supported downloads, and then try reinstalling the NI software that required it.

[Elaine_R.]

Thanks for the tip, Scott!

Your recommendation for latest Microsoft Visual C++ 2015-2022 Redistributable seems to be a solid workaround, for my team.

The upgrade pushed me from (14.34.31931 --> 14.36.32532) for both (x86)& (x64) and appears (so far) to have unblocked all NI installers on my Win 10 Enterprise OS with CloudStrike.   I'm doing further tests to confirm Win 11 PCs are similarly fixable, so wish me luck.

I did some experiments yesterday with different permutations, and so far it feels like a combination of both variables in play?

(1) a machine with no/disabled antivirus, and older Redistributable... ran NI installers normally
(2) a machine with antivirus / Enterprise OS, and latest Redistributable... ran NI installers normally
(3) a machine with antivirus active, &  old redistributable  = bad times

Would love to know more about why this update to redistributable matters so much when clearly it isn't "needed" by the NI installers themselves.  I have a few more details I may share directly with you later, that you might find interesting.

Cheers,
Elaine R

[rolfk]

---

@Elaine_R. wrote:

Would love to know more about why this update to redistributable matters so much when clearly it isn't "needed" by the NI installers themselves.  I have a few more details I may share directly with you later, that you might find interesting.

Cheers,
Elaine R

---

It's not the installer itself that needs this dependency but one or more of the components getting installed. Generally any software developed with Microsoft C Visual Studio requires this Redistributable C Runtime library. This means basically any NI software for Windows, be it LabVIEW, NI-MAX, every single driver and what ever else.

Before Visual Studio 2015 it was even so that you had to have the specific version of the Redistributable Runtime installed that matched the version used to compile the application. This could result in the situation that NI installers actually had to install multiple versions of this software, since not every application, tool and help utility was always rebuild every single time when a new LabVIEW version was released for instance. Since Visual Studio 2015, the C runtime library has been unified so all newer Visual Studio version make use of the same baseline C runtime, of course with updates and bugfixes for newer versions but a program compiled with Visual Studio 2015 should still work with the C Runtime from Visual Studio 2023. The oppositie oviously is not true, so if you have multiple applications that were created with different versions of Visual Studio C, you need to make sure to have at least the version installed that comes with the latest Visual Studio C version that was used to create any of the applications. Installing the newest and greatest is of course also possible and SHOULD be not causing problems.

The Visual C Runtime Distributable installer is not a huge installer but does some particular things that Virus scanners or other Threat Prevention Tools might find suspicious. Being a standard Microsoft Product, these tools have of course fingerprint techniques to recognize this particular installer and white wash those suspicious activities. The Installer NI uses is a slightly customized installer and those fingerprint techniques seem to fail because of that, making the protection tools getting a hiccup because of those suspicious activities.