LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error when installing Real-Time Module (windowsdesktop-runtime-6.0.22-win-x64.exe)

Hello!

 

The NI Paket Manager wants to install the Microsoft Windows Desktop Runtime - 6.0.22(x64) when installing the Real-Time Module, which unfortunately fails. I noticed in the log file that my Windows version seems to be recognized incorrectly:

[05AC:47BC][2024-01-29T16:17:53]i001: Burn v3.14.0.5722, Windows v6.1 (Build 7600: Service Pack 0), path: C:\WINDOWS\Temp\{F4EF8CD0-E36B-49C9-A4F9-901C78495270}\.cr\windowsdesktop-runtime-6.0.22-win-x64.exe

 

Which causes the error:

[05AC:47BC][2024-01-29T16:17:54]e000: Error 0x81f40001: Bundle condition evaluated to false: ((VersionNT > v6.1) OR (VersionNT = v6.1 AND ServicePackLevel >= 1))

 

According to `winver` I have Windows 10 22H2 (Build 19045.3930) so it should actually say Windows v10.0. I have already installed the Windows Desktop Runtime - 6.0.22(x64) manually (without any problems) but the Paket Manager doesn't care and still tries.

 

Any idea what I can do?

 

The rest of the log is in the attached file. The Paket Manager error log is rather short:

===== 2024-Jan-29 16:19:26.917547 =====
Exception in ni::pkgclient::TransactionBase::StartInternal. Error code: -125083
Request type: ComplexSolverTransaction (30)
-125083: An error occurred while installing a package: ni-msdotnet-desktop-runtime-60 (23.8.0.49180-0+f28)
File: source\nipkg_client\pkgclient\PluginInteraction.cpp
Line number: 266

 

Additional error information:
-125441: The executable returned error '1' after running the command 'path='"D:\my_user\AppData\Local\Temp\nipkg-bb2d-a722-1a5f-717b\data\DotnetInstallerRunner.exe"', arguments='windowsdesktop-runtime-6.0.22-win-x64.exe'' for the custom operation.
File: C:\dev\_r\17\src\package_manager\nipkg\source\shared_agents\Base/ErrorHandler/ErrorInfo.h
Line number: 335

 

 

0 Kudos
Message 1 of 7
(991 Views)

What were you trying to do?  Are you installing some version of LabVIEW on a PC running some version of Windows?  If so, what version of LabVIEW, and what version of Windows?  Is some version of LabVIEW already on the PC?  Are you even using a PC?

 

You seem to be using some version of NI Package Manager -- what were you doing at that time?  [Answers could be something like "I was attempting to install ???? on a ????].

 

Bob Schor

0 Kudos
Message 2 of 7
(935 Views)

Hey!

 

I have LV 2013, 2016, and 2021 (all 32-bit) installed on my machine. For an upcoming project I need to work with a cRio controller and I am trying to install the Real-Time Module for LabVIEW 2021 using the NI Paket Manager. As mentiond in my previous post im running Windows 10 22H2 (Build 19045.3930) on my system.

0 Kudos
Message 3 of 7
(913 Views)

I have LabVIEW 2019 (32-bit) and 2021 (32-bit) installed on my Windows 10 (64-bit) PC, along with the CompactRIO Driver and support modules for LabVIEW 2019 and 2021 (according to NI Package Manager).  I also have LabVIEW Real-Time Module English for 2019 and 2021.

 

I don't know why a very old version of LabVIEW (such as LabVIEW 2013) would necessarily interfere with the configuration you describe, but LabVIEW can be tricky and "difficult".  If you are not planning to use LabVIEW 2013 (or if you have it installed on another machine if you need it), you might consider using NIPM to remove all NI Software (along with itself, in a second step), and carefully reinstall LabVIEW.  I, and others, have posted (the only?) safe ways of uninstalling LabVIEW, and recommendations for re-installing.

 

Bob Schor

0 Kudos
Message 4 of 7
(881 Views)

First of all, thanks for the advice.

 

I was already afraid of something like this. As I have probably exhausted all other options, I will have to bite the bullet.

0 Kudos
Message 5 of 7
(860 Views)

If you do decide to do a National Instruments software "Remove all/Reinstall" sequence, do not attempt to "clean the Registry".  It is an excellent way to make LabVIEW "uninstallable" until you wipe your C: drive and reinstall Windows, all your programs, and restore all your data.  [Sadly, I can say "Been there, done that."].

 

Bob Schor

0 Kudos
Message 6 of 7
(832 Views)

Thanks for the advice. In the past, I have also had rather bad experiences with this type of software and I prefer to keep my hands off it. I will first uninstall everything I can with the NI package manager, then add/remove programs from Windows and finally the package manager itself. Then manually remove the usual file and folder remnants.

0 Kudos
Message 7 of 7
(823 Views)