Target Configuration does not allow installation

[FKhueson]

Hi all, this is a critical issue with a time sensitive element. Suddenly (without any modifications or updates to labview on any computer) I am unable to install labview to a Raspberry Pi through the Target Configuration Wizard. This is something I've been able to easily do in the very recent past without issue. I've tried this using multiple computers and SD cards in the Pi, no luck.

1. I turn on my Pi with kb/m and monitor, connected to network by ethernet.
2. SSH is enabled.
3. I turn on my PC (win11), open labview 2024q3 (24.3.6f6), open target configuration wizard from the hobbyist menu in tools.
4. Enter IP, username, password.
5. The status at the bottom indicates a successful connection, but the installation, network settings, and target info buttons do not become available. Thus, I cannot install labview.
6. Clicking on the "..." I see:
   

   Connecting to target...
   Successfully connected to target.
   Successfully connected. Gathering target info...
   Target configuration updated.
   OS Version: 12.12
   CPU: Raspberry Pi 4 Model B Rev 1.2
   Systemd Version:
   Has Internet Access: False
   Device Type: Raspberry Pi 2 B

   Ignoring Error: 56 NI_Subprocess.lvlib:Raw Subprocess.lvclass:_Select.vi:4540001<APPEND>

   <b>Complete call chain:</b>
   NI_Subprocess.lvlib:Raw Subprocess.lvclass:_Select.vi:4540001
   NI_Subprocess.lvlib:Raw Subprocess.lvclass:Interact.vi:2440001
   NI_Subprocess.lvlib:Buffered Subprocess.lvclass:Pump.vi:6140001
   NI_SSH.lvlib:Execute SSH Command.vi
   LMH-LINX.lvlib:SSH Execute Command.vi
   LMH-LINX.lvlib:Check Target Internet Connection.vi
   LMH-LINX.lvlib:Interrogate Target.vi
   LMH-LINX.lvlib:Target Configuration.vi

7. The Pi has internet access, I have updated it where it's at.

Any idea why this changed? We have a research partner who is at a stop because of this. Thank you for any help!

[FKhueson]

Update:

1. Created new SD card with Raspberry Pi Imager. (Raspberry Pi OS (Legacy, 32-bit) 2026-06-18)
2. Installed updates (weird, thought it said it had no internet), restarted.
3. Enabled all interfaces (SSH, I2C, etc) except VNC.
4. Rebooted, same connection issues.
5. After some reading, perhaps something changed on the RPi side? Added lines to SSH config files (and generated DSA key) as per: https://forums.ni.com/t5/Hobbyist-Toolkit/Device-interrogation-failed-unable-to-connect-to-the-targe...
6. Connect with Target Configuration successful, but now the log shows:
   Connecting to target...
   Successfully connected to target.
   Successfully connected. Gathering target info...
   Target configuration updated.
   OS Version:
   CPU:
   Systemd Version:
   Has Internet Access: False
   Device Type: Unknown
7. The installation, network settings, and target info become available, but in installation is shows no available versions.
8. Clicking upgrade yields:
   

   Connecting to target...
   Successfully connected to target.
   Successfully connected. Gathering target info...
   Target configuration updated.
   OS Version:
   CPU:
   Systemd Version:
   Has Internet Access: False
   Device Type: Unknown

   Ignoring Error: 1 Scan From String (arg 1) in LMH-LINX.lvlib:Check OS Version.vi->LMH-LINX.lvlib:Generate Target Compatibility Report.vi->LMH-LINX.lvlib:Target Configuration.vi
   Adding MakerHub feed...

   Updating package index. This may take over 30 seconds depending on your internet speed...

   Installing LabVIEW...

   Checking target status...

   Installation completed successfully. Click Launch Example to get started.
   Target configuration updated.
   OS Version:
   CPU:
   Systemd Version:
   Has Internet Access: False
   Device Type: Unknown

   
   Not sure what the deal is with this now, it clearly has internet as I was able to update the OS.

[AndyLB · Accepted solution]

Hi FKhueson,

There is a fault on the server that NI use to host the files for the LINX LabVIEW runtime. I have reported the fault to NI and they are working on a solution.

It is still possible to install the LINX LabVIEW runtime manually.

1) Boot the Rpi with a 32 bit version of PI OS. I used the version dated 18 Jun 2026

2) SSH into the Rpi

3) Enter the following commands

sudo echo "deb [trusted=yes] http://feeds.labviewmakerhub.com/debian/ binary/" | sudo tee /etc/apt/sources.list.d/makerhub.list
sudo apt-get update
sudo apt-get install -y lvrt24-schroot
sudo raspi-config nonint do_i2c 0
sudo raspi-config nonint do_spi 0

Enter the following command to check that the LabVIEW run time is running

ps -Af | grep lvrt

 Check there is an entry for ./lvrt

root 2855 1 0 00:14 ? 00:00:00 ./lvrt

You should now be able to connect to the Rpi from LabVIEW 

Hope this helps,
Andy.

[FKhueson]

Andy, many thanks! This seems to have gotten things going again on our end, I greatly appreciate it.

Do you think the SSH hostkey lines I entered are necessary, or is the manual install the only required solution until the server is fixed? I can do more tinkering on it, but if you have a notion let me know.

[AndyLB]

Hi FKhueson,

Excellent news!

It's just the manual install that's required. I didn't enter the SSH key commands.

[juavil]

I think that  the issue with installing LabVIEW on the latest version of the operating system is due a security update in the newest version of Raspberry OS.

Now, when running a command as root, the OS requires the password to be entered via standard input. This limitation applies to commands executed via SSH as well.

I suspect the LabVIEW installer uses this method during installation, which is why it fails.

To work around this limitation, you can either disable this additional security feature in your Raspberry Pi's configuration or—as a temporary measure—log in to the Raspberry Pi and run a root command (such as "sudo ls"). This will prompt you for the user password, after which you should be able to proceed with the LabVIEW installation.

[AndyLB]

Hi Juavil,

Thank you for your post and all the information about the changes from the 2026-04-13 release of the PI OS. It may affect users running commands on the Rpi using the ssh vi's. 

The target configuration tool does support a password for sudo. I think it may have been required for the Beaglebone  Black. The issue was due to a fault on the server used to host the files required for the installation. This has now been fixed by NI. Thank you Ken_S for all your help.