LabVIEW Executable Using NI FieldPoint Fails After Upgrading Windows OS

Updated Mar 25, 2025

Reported In

Hardware

  • Controller for Compact FieldPoint

Software

  • LabVIEW Run-Time Engine

Driver

  • NI-FieldPoint

Issue Details

I have a LabVIEW 8.5.1 or older application that uses NI Compact FieldPoint (cFP) hardware. The program was compiled and ran on my Windows computer without any issues. However, when I upgraded my computer OS to Windows 10, my application no longer functions. 

Solution

There is software incompatibility between NI FieldPoint and the Windows OS. To resolve the compatibility issue, see the section appropriate for your cFP controller. 

cFP 22xx and cFP 21xx Controllers

  1. Upgrade to LabVIEW 2015 SP1, LabVIEW Real-Time 2015 SP1 , and NI FieldPoint 15.5 on the development computer. 
  2. Upgrade to LabVIEW Run-Time Engine 2015 SP1, LabVIEW Real-Time 2015 SP1, and NI FieldPoint 15.5 on the Windows 10 deployment computer, or include them in an installer.  
  3. Open the source code in the upgraded LabVIEW version and mass compile the code . 
  4. Build the executable in the upgraded LabVIEW version.
  5. Deploy the executable to the Windows 10 computer. 

cFP 20xx Controllers 

cFP 20xx Controllers do not support LabVIEW Real-Time Module 8.6 or later, and LabVIEW Real-Time Module 15.1 is the earliest supported version on Windows 10. National Instruments highly recommends upgrading to CompactRIO . 

Additional Information

The executable may exhibit unexpected behavior if the deployment computer OS version is different from that of the development computer . 

NI FieldPoint 15.5 is the last release for FieldPoint software. If you are setting up a new system or plan for future software upgrades, National Instruments highly recommends to migrate to CompactRIO, which offers higher performance and more flexibility than Compact FieldPoint. 

Related Links

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.