List of known issues
The following table was created from parsing the Release Notes from NI Website (https://www.ni.com/en/support/documentation/release-notes/product.labview.html).
There is no guarantee the parser succeeded completely in importing all the data. In doubt, check back at the NI Website.
| DISCLAIMER: Information here is purely processed data. There is no way to keep the data synchronized with NI Website. The idea was to gather all official related data to bugs and known issues in one place. If you find a mistake you are allowed to fix it. If you have new data, you are allowed to include it. |
| Bug Number | Description | Reported Version | Resolved Version | Added |
|---|---|---|---|---|
| 1000558 | LabVIEW can crash when the Class Hierarchy window is open and missing dependency
If there is a class or interface which has a missing dependency class or interface and the LabVIEW Class Hierarchy window is open and the missing dependency is selected when you close the project or quit LabVIEW, a crash may be encountered. Workaround: Deselect the missing item before closing or close the Class Hierarchy window |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1000943 | Passing 1D and 2D arrays of strings between LabVIEW and TestStand is slow
Passing 1D and 2D arrays of strings between LabVIEW 2020 and TestStand using LabVIEW Run-Time Engine causes slowdowns. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1004078 | Unnecessary Compilation Occurs when a source distribution is set to remove object code
If the Separate compiled code from all source files option is selected when creating a source distribution, LabVIEW compiles the project before saving the source files. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2017 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1009119 | XControls do not load correctly when placed in subVI
When a XControl is placed in a subVI, the XControl may not appear. Workaround: Temporarily fix by redropping the XControl in the subVI, but the problem will return when the VI is loaded again. No workaround for built applications. |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1013965 | Slow application build times for some projects in LabVIEW 2020
Building large projects into applications or other distributables takes longer in LabVIEW 2020 compared to LabVIEW 2019 SP1. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1014647 | LabVIEW hangs when the LabVIEW CLI tries to disconnect from the target LabVIEW instance
Automated build systems using the LabVIEW CLI can cause LabVIEW to hang sometimes when disconnecting in the middle of a build. Workaround: Avoid trying to disconnect while building. |
LabVIEW 2019 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1019181 | Unable to install package: ni-vipm
An error can occur during the LabVIEW 2020 installation which prevents the install of the package ni-vipm Workaround: Deselect VI Package Manager when installing |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1027690 | Upgrading LabVIEW 2019 source to LabVIEW 2020 results in some VIs appearing broken
Upgrading source from LabVIEW 2019 to LabVIEW 2020 breaks some VIs. Workaround: Mass compiling the broken VIs or making cosmetic changes and saving can help in some cases. |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 103315 | Creating a circular link between an Xcontrol and a LVClass can crash LabVIEW.
The circular load leads to VIs that are permanently broken and no matter what you do the run arrow will not become fixed. Workaround: Do not create a circular link from your XControl to your class. In other words, write your class completely and then write your XControl using the class. Do not put the XControl or any property/invoke node for the XControl into member VIs of the class. |
LabVIEW 8.5.1 | N/A | 11/17/2009 |
| 1035177 | Flattening and unflattening variants of a set corrupts name information
When flattening and unflattening the variant data into string data from the Insert Into Set VI, the name information gets corrupted. For example, the first two characters in the name get dropped from the name within the variant data itself or strings of random data get appended to the end of the name. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2019 | N/A | Jan 6, 2021 |
| 1043411 | RFmx Memory leak in LabVIEW 2020
Large RFmx applications could see large memory leaks under some circumstances Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1047200 | VI for Override Throws Error 7 when overriding Packed Library with Debugging Enabled in LabVIEW 2020
Try to create an override VI in a child class which inherits from a parent inside a Packed Project Library and debugging is enabled, it fails with Error 7. Workaround: Build override VI manually. |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1048670 | LabVIEW crashes with id 0xC0000005 when using some forms of error tracing
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1054394 | Restarting a BeagleBone Black using System Configuration causes crash
Connecting to a BeagleBone Black target using the LINX toolkit that is connected to the host via USB LAN can cause the host system to hang and crash. Workaround: There is currently no known workaround for this issue. |
LabVIEW System Configuration: 20.0 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1054835 | SHA-256/SHA-224 results are incorrect for some message sizes
LabVIEW returns the wrong value for a SHA-256 and SHA-224 for message sizes56, 120, ..., (N*64+,56) bytes Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 105509 | The "do not save automatic changes" setting does not affect libraries
The "do not save automatic changes" options setting does not affect any type of library, including classes. Workaround: N/A |
LabVIEW 8.0 | N/A | 06/20/2008 |
| 1055195 | "Casting Utility For Actors.vim" causes dependency issue when used in a PPL
Workaround: Edit new messages to separate from the VIM |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1056583 | Right-clicking on a class wire/terminal/control when when right-click plugins causes crash
When using right-click plugins, LabVIEW can sometimes crash if right clicking on a class wire, terminal, or control. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1057446 | Dynamic Dispatch method overrides do not save updates
In specific situations, changes made to method overrides will not save. Reopening the VI after saving changes will show the previous code. This prevents users from updating Dynamic Dispatch VIs for child classes. Workaround: None |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1059425 | Newly created class overrides of Interface methods will sometimes not save
Sometimes LabVIEW silently fails to save and erases all edits to newly created class overrides of Interface methods. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1066777 | FTP Get Path Info.vi gives incorrect response
Create a \222 directory on your FTP server. If you copy one file to the \222 directory, connect to the server, and input a path such as \111\222, FTP Get Path Info.VI returns the file even though the path does not exist Workaround: Delete the \222 folder and the VI recognizes that the path does not exist. |
LabVIEW 2016 | N/A | Jan 6, 2021 |
| 1072837 | Casting Utility For Actors.vim has incorrect error handling
When messages are created for interfaces there may be incorrect error handling behavior due to wiring in the Casting Utility For Actors.vim Workaround: Modify the VIM manually |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1078977 | LabVIEW 2020 crashes when using the File >> New.. dialog and selecting Class or Interface
Workaround: Add a class by right clicking and selecting New >> Class or Interface |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1079302 | LabVIEW crashes when encountering a broken dynamic dispatch VI called from TestStand
When a TestStand step calls a dynamic dispatch VI, the step is configured to call the base class version of the dynamic dispatch VI. If the dynamic dispatch member VI that corresponds to the class input is broken, LabVIEW may hang and crash. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2019 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1123769 | LabVIEW 2020 may crash on launch on macOS 11.0 Big Sur
LabVIEW 2020 may crash on launch on macOS 11.0 due to a graphics stack issue. Workaround: Run the following commands from Terminal: defaults write com.ni.labview NSGraphicsContextAllowOverRestore -bool YESdefaults write com.ni.labview NSViewAllowsRootLayerBacking&,nbsp,-bool NO |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1126029 | LabVIEW 2020 doesn't display UI feedback correctly on macOS 11.0 (Big Sur)
LabVIEW 2020 incorrectly displays selection rectangles, marching ants selection boundaries, dragged objects, and block diagram wiring feedback when run on Big Sur. Workaround: Run the following command from Terminal: defaults write com.ni.labview NSViewAllowsRootLayerBacking -bool NO |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1135156 | EXE containing Malleable VIs can only run when Enable Debugging and Disconnect Unused Inline SubVIs are selected
Codebases with many classes and Malleable VIs can have problems when building EXEs. In some cases, the EXE process starts but the code never runs. If you build with Enable Debugging selected, the EXE will have a broken run arrow and refers to a broken Malleable VI. Workaround: Build with Enable Debugging and Disconnect unused inline SubVIs selected. |
LabVIEW 2020 | N/A | Jan 6, 2021 |
| 1146185 | LabVIEW fails to save changes when moving a VI between virtual folders
LabVIEW fails to save changes when moving VI from one virtual folder to another within a .lvclass or .lvlib. Workaround: Move the VI to the new virtual folder and change the scope to anything else. Then change it back to the original one. This will save the changes and the next time you open LV, the VI will be in the specified virtual folder.Move the VI to the new virtual folder and change the scope to a different option and then back again. |
LabVIEW 2020 | N/A | Jan 6, 2021 |
| 1146643 | LabVIEW Crashes When Playing Sound File Repeatedly without Calling Sound Output Clear
Playing sound files repeatedly without calling "Sound Output Clear" crashes LabVIEW. Workaround: Call "Sound Output Clear" after playing a sound file. |
LabVIEW 2020 | LabVIEW 2023 Q1 | N/A |
| 1156197 | Play Sound File VI interruption after several thousand iterations
After several thousand iterations, the Play Sound File VI stops playing the sound for one iteration. This behavior repeats every several thousand iterations. Workaround: The issue happens less frequently on 64-bit LabVIEW and could be considered a workaround depending on the application. |
LabVIEW 2020 SP1 | N/A | Jan 6, 2021 |
| 1156638 | Set up for Acquire Sound Express VI in Mac OS 14.10 causes a memory leak
Adding the Acquire Sound Express VI to the block diagram and waiting on the setup window causes memory leak in Mac OS Mojave 14.10. Workaround: Close setup window before the memory leak uses too much memory. |
LabVIEW 2020 | N/A | Jan 6, 2021 |
| 1158778 | NIPM does not discover the LabVIEW 2020 f1 Update
Workaround: Fixed in the LabVIEW 2019 SP1 f3 and LabVIEW 2020 f1 patches. |
LabVIEW 2019 SP1 | LabVIEW 2020 f1 | Aug 31, 2020 |
| 1159698 | LLB does not reliably update when VI is modified post-build
When a post-build action modifies a VI in an LLB and the LLB is copied to another folder, the copied LLB contains an old version of the modified VI and does not match the LLB originally created by the Build Spec. Workaround: The VI in the LLB needs to be modified in something other than a post-build action. |
LabVIEW 2020 | N/A | Jan 6, 2021 |
| 1165082 | Race condition with an array of notifiers and a For Loop
When building an array of notifiers and connecting the Build Array function to a For Loop, the second iteration of the loop will timeout while waiting on a notification. Workaround: Index out the two notifiers and operate on them independently instead of in a For Loop. Make a data dependency so that either Obtain Notifier 1 and/or Send Notification 1 are guaranteed to execute before Send Notification 2. |
LabVIEW 2019 | N/A | Jan 6, 2021 |
| 1166235 | Mic/camera permissions on macOS may not associate properly
A VI requiring mic or camera permissions may not be able to access these system resources or prompt the user for permission. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2019 | LabVIEW: 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 1176457 | Event Structure Always Preserves Space for Event Data Node
An event structure with the Auto Grow option enabled will preserve space for the Event Data Node even if the Event Data Node is not visible. Workaround: There is currently no known workaround for this issue. |
N/A | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 1182809 | IMAQ Create Executes More Slowly with Additional Calls in Built Applications
In a LabVIEW project, the right-click "Replace with" operation on a library can fail to update some VIs in the project. This issue affects VIs that reference the original library only through a dynamic dispatch call to a class method that is inherited from a parent class and not overridden by the child class wired to the call. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2021 SP1 | Nov 2, 2021 |
| 119444 | Multi-column listbox format lost on upgrade
A Multicolumn listbox created in LV 7.1 may lose its format when opened in LV 8.5 or later. Column headers lose their 3D appearance and font formatting might be lost. Workaround: Replace the Listbox and recreate all customizations |
LabVIEW 8.5 | N/A | 07/12/2008 |
| 120686 | Write to LabVIEW Measurement Files (LVM) using Express VIs takes up a lot of memory
The "Write to Measurement File" Express VI consumes a large amount of memory when writing to a Text File (LVM). However, the memory usage is smaller when the same Express VI is used to write a TDM/TDMS File Workaround: Use general LabVIEW VIs (and not Express VIs) to perform an LVM write for large amounts of data. The other option would be to write in smaller chunks. |
LabVIEW 7.1 | N/A | 08/11/2008 |
| 1210828 | Crash When Using Array Size Inside For Loop That Indexes a Set
When running a VI that iterates over a Set of Arrays with a For Loop and uses the Array Size function on an element, LabVIEW will crash. If you save the VI, then LabVIEW will crash when loading the VI. Workaround: Convert the set to an array before operating on the elements. Fixed in the LabVIEW 2019 SP1 f4 Patch. |
LabVIEW 2019 | LabVIEW 2021 | May 6, 2021 |
| 1229501 | Memory Leak When Using "Get Next Non-Text Sibling.vi"
LabVIEW leaks memory when using "Get Next Non-Text Sibling.vi" fromNI_XML.lvlib. Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch. |
LabVIEW 2020 | LabVIEW 2021 | May 6, 2021 |
| 1249120 | Crash if Variant to Data Processes ActiveX Data and the Output Is Not Wired
Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch. |
LabVIEW 2020 | LabVIEW 2021 | May 6, 2021 |
| 1271213 | Slow Execution of Comparison of Variants Containing Large Data
LabVIEW makes unnecessary copies of data when doing comparison operations with Variants, which can result in slower performance in LabVIEW 2017 compared to earlier versions. Workaround: Fixed in the LabVIEW 2019 SP1 f4 Patch. |
N/A | LabVIEW 2021 | May 6, 2021 |
| 1271283 | Some EXEs built in 2017 SP1 do not work with the 2020 RTE
In rare instances, EXEs built in LabVIEW 2017 SP1 with the "Allow future versions of the LabVIEW runtime to run this application" option enabled freeze when using the LabVIEW 2020 Runtime Engine. Workaround: Upgrade to the LabVIEW 2020 SP1 Runtime Engine. |
LabVIEW 2017 SP1 | LabVIEW 2020 SP1 | Feb 22, 2020 |
| 128059 | Shared variable bindings in the same library are not updated properly when copying/renaming the library
If you have shared variables in a library which are bound to I/O servers or other variables that are also in the same library, and you rename or save a copy of the library, the bindings still refer to the original library name. Workaround: Manually rebind the variables after copying or renaming the library. |
LabVIEW 8.0 | N/A | 04/28/2009 |
| 1335783, 1859807, 2065508 | Using the DAQAssistant with DAQmx 2022 Q3 on LabVIEW 2022 Q3 Fails to Generate Code
Using the DAQAssistant on LabVIEW 2022 Q3 with DAQmx 2022 Q3 installed fails to configure the DAQAssistant node and gives the following code generation error: "LabVIEW Code Generation failed to execute.This may occur if the code gen engine is not properly installed, or if you are using a LabVIEW version under development" . Other workflows that use the DAQ Assistant to generate DAQmx tasks also fail. Workaround: Install LabVIEW 2021 SP1LabVIEW 2021 SP1 does not need to be activated, it is sufficient to install LabVIEW 2021 on your system and not activate it Installing just the LabVIEW 2021 SP1 run-time engine will not be sufficient, the LabVIEW ADE needs to be installed |
LabVIEW 2022 Q3 | NI-DAQmx 2022 Q3 | NI-DAQmx 2023 Q1 | N/A | Aug 2, 2022 |
| 136677 | Remote panels do not work if Internet Explorer is embedded in an ActiveX or .NET Container
If a remote panel is built in LabVIEW 8.6 and embedded in an ActiveX or .NET Container in a LabVIEW 8.6 VI it will not display correctly Workaround: Use a remote subpanel. This is actually the recommended way to accomplish this task |
LabVIEW 8.6 | N/A | 10/01/2010 |
| 141699 | NI Distributed System Manager does not show deployed libraries if they contain non-Latin characters.
If a library with non-Latin characters (such as Japanese, Chinese, or Korean) is deployed, it will not show up in the NI Distributed System Manager tree view. Workaround: Rename the library using only the Latin alphabet and re-deploy the library. |
LabVIEW 2009 32-bit | N/A | 02/10/2009 |
| 1484666 | Random Number (Range).vi U64 Can Generate Numbers Greater Than Upper Bound
The U64 instance of the polymorphic Random Number (Range) VI can generate numbers greater than the specified upper bound. Workaround: Test if the generated number is inside the specified range, and generate another value if it isn't. |
LabVIEW 2020 | N/A | Aug 12, 2021 |
| 1500249 | Sets and Maps Incorrectly Treat Some VI References as Equal
Inserting a VI reference as a key into a Set or Map can incorrectly fail and return True for "key already included?" when a different reference to the same VI already exists in the set or map, even if the existing reference was obtained separately and has a different reference value or refers to a different clone instance of the VI than the reference being inserted. Workaround: Use the "Clone Name" property or another unique attribute of the VI rather than a VI reference as the key to a set or map datatype when looking up values based on VI instances. |
LabVIEW 2019 | LabVIEW 2021 SP1 | Oct 14, 2021 |
| 1392758 | TDMS Async VIs Provide Incorrect Data on Last Iteration when Read Channel-by-channel in a Loop
When you use the TDMS Advanced Async VIs to read data out of a file with multiple channels in a For Loop, the final iteration can provide incorrect/missing data. Workaround: Include the Start Asynchronous Read and Stop Asynchronous Read functions inside the loop, so they execute on every iteration. |
LabVIEW 2021 f1 | N/A | Aug 12, 2021 |
| 1510208 | Distributed System Manager Displays Stale Information in LabVIEW Chinese
In LabVIEW Chinese, the Distributed System Manager can show out-of-date information. Workaround: Move the window and the Distributed System Manager will refresh to show current information. |
LabVIEW 2021 | N/A | Aug 12, 2021 |
| 1513139 | Malleable VIs Are Sometimes Erroneously Broken When Operating on Cluster Data Value References
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 1518822 | Change Parent Interfaces Dialog Does Not Allow Removal of Missing Interface
If a class or an interface inherits from an interface that is missing on disk, the Change Parent Interfaces dialog does not provide a way to remove that parent. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 1521038 | LabVIEW for Linux Crashes on Exit after Using RFSA Self-Calibration VIs
In Linux, loading a DLL built in a different version of LabVIEW than the version loading may cause LabVIEW to crash on exit. Using the NI-RFSA Self-Calibration VIs could lead to this crash. Workaround: Fixed in the LabVIEW 2021 SP1 f2 Patch. |
LabVIEW 2021 | LabVIEW 2021 SP1 f2 | Jun 27, 2022 |
| 1528110 | Objects Are Not Added to Sets and Maps If Parent Interfaces Are Present
When adding objects to a set or map, if they inherit from interfaces that are also in the set or map, those objects are erroneously excluded. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 1529057 | Ctrl-Delete Keyboard Shortcut Does Not Remove Array Element
Using the keyboard shortcut Ctrl-Delete can appear to remove an array element but does not update the value of the array. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 SP1 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 153731 | Unhandled Exception can occur if absolute path for system DLL used in CLFN
If you use a specific path to a system DLL (C:\windows\system\user32.dll) and build your VI into an application it will create a copy of the DLL inside the application. This can cause an unhandled exception when running Workaround: LabVIEW searches in the system directory when looking for DLLs. If you are using a system DLL simply put the name in the in DLL Path box in the CLFN properties. In the example above you would simply put "user32.dll" |
LabVIEW 8.6 | N/A | 07/23/2010 |
| 1539898 | LabVIEW Crashes When Removing Class Member VI With Recursive Caller
LabVIEW may crash when removing a dynamic dispatch method VI from a class. This happens if a child class doesn't implement the method but has a recursive call to it. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 1555422 | Changes to MATLAB (.m) File Are Not Reflected after Running a Calling VI That Calls the .m File
When you drag a file from the File Explorer to a Path control or constant, the value of the path will have an extraneous NULL character at the end. Workaround: Manually delete the extra character after completing the drag and drop.Fixed in the LabVIEW 2021 SP1 f2 Patch. |
LabVIEW 2021 SP1 | LabVIEW 2022 Q3 | Jun 27, 2022 |
| 1564621 | Block Diagram Wires Sometimes Misaligned After Repositioning Functions
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 157246 | The Property Node "Bring to Front" doesn't work in Windows Vista
Workaround: N/A |
LabVIEW 8.6.1 | N/A | 04/20/2009 |
| 1596011 | Block Diagram Wire to Malleable VI is Broken Erroneously
A wire to a malleable VI can be broken even though the malleable VI accepts the type of the wire. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2019 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 1597634 | LabVIEW Crashes When Setting Strings[] Property to Empty Array
The Custom Probes section of a wire's context menu does not display probes from <,Documents>\LabVIEW Data\Probes. Workaround: Remove a VI from a subpanel before closing its reference. |
LabVIEW 2020 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 163371 | "Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner library
Old Description :"Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner libraryIf you have a nested library, a library that is owned by another library, and you use Save As:Copy, there is an option to add the duplicate library to the original owner library. If you use this option, the member VIs of the duplicate library are all broken because they are not correctly named as members of the owning library.This bug affects all types of libraries, .lvlib, .lvclass, .xctl and .lvsc. Workaround: Option 1: Do not use the "add to owning library" option and instead add the duplicate library to the owner manually after the copy. Option 2: After the copy operation, open and close one of the new VIs and then move the duplicate library out of the owner library. Browse to any missing VIs that pop up a browse dialog. Move the duplicate library back into the owner library. |
LabVIEW 8.5 | N/A | 09/30/2009 |
| 166204 | LabVIEW Class Property Node Doesn't Update with New Type Definition Name
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 SP1 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 166253 | LabVIEW.app does not show up after LabVIEW 2009 Installation
Workaround: This is only an issue for customers who installed the LabVIEW 2009 Beta for Mac. Delete /Library/Receipts/LabVIEW*9.0.pkg before running the LabVIEW 2009 installer for Mac OS. |
LabVIEW 2009 32-bit | LabVIEW Unknown | 07/31/2009 |
| 166351 | Get Date/Time String does not work for dates beyond 2/5/2040
When trying to get a string for dates 2/6/2040 and beyond, the Get Date/Time String will instead provide an earlier, incorrect date. Workaround: Use the Format Date/Time String VI instead of Get Date/Time String |
LabVIEW 2013 SP1 | N/A | Feb 11, 2020 |
| 166364 | Clicking greyed out option of the Scale Legend when using a Waveform Chart causes LabVIEW to crash
If you add a Waveform Chart to the Front Panel (without wiring anything to it on the Block Diagram) and then expand the Legend to include more Plots, set the Waveform Chart to Stacked Plots, make the Scale Legend visible, and then expand the Scale Legend to show more empty or greyed out y-scales, when you try to select any of the buttons on the greyed out portion, LabVIEW will crash. Workaround: If you wire any 2D array (even an empty 2D array of doubles) to the Waveform Chart before setting the Waveform Chart to Stacked Plots, the crash will not occur. |
LabVIEW 2014 SP1 | N/A | Feb 11, 2020 |
| 166386 | Incorrect behavior when using a Boolean control from the System palette
When using a Boolean control from the System palette and running the VI, you do not see the "hover" picture change. When clicked, the value stays consistent, but the button does not change visually. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2015 SP1 | LabVIEW 2020 | Apr 20, 2020 |
| 166394 | DataSocket Write VI with default timeout can hang before proceeding
When using the DataSocket Write VI with the default 0 second timeout (or wiring in a 0 second timeout), the VI may hang for 10 seconds before completing. Workaround: Wire in a short timeout of several ms to the DataSocket Write VI. |
LabVIEW 2017 SP1 | N/A | Feb 11, 2020 |
| 166505 | Registering for an event for multiple boolean controls can fail in specific configurations
When passing a mixture of strict and non-strict boolean references in a cluster to the event source terminal of the Register For Events node, the input wire will break if any strict references are not the first elements of the cluster. Workaround: Use a Switch mechanical action, group the references with Build Array, or place any strict references at the beginning of the cluster. |
LabVIEW 2016 | N/A | Feb 11, 2020 |
| 166601 | LabVIEW Runtime Engine encounters Worker Thread Limit when using web services on Linux RT-based cRIO
On a Linux RT-based cRIO, the LabVIEW Runtime Engine can get into a deadlocked state waiting for action from the Web Server. This can cause process hangs resulting in a Worker Thread Limit error reported to the user by the Web Server. Workaround: Use a mechanism other than web services. |
LabVIEW 2015 | LabVIEW 2020 | Feb 11, 2020 |
| 1667266 | LabVIEW VI Window Title Only Uses Latin-1 Character Encoding on Linux
LabVIEW 2021 SP1 causes an increase in the memory usage of some applications unnecessarily over time. Workaround: You can disable the performance optimization which caused the memory leak by adding "MemoryManger.UseMasterPointerPool =, FALSE" to the LabVIEW INI file. LabVIEW 2021 SP1 f1 patch fixes the issue by disabling the performance optimization by default. |
LabVIEW 2021 SP1 | LabVIEW 2021 SP1 f1 | Apr 22, 2022 |
| 1667279 | Captions Using Application Font Do Not Display Non-English Characters on Linux
On Linux, LabVIEW defaults to using Helvetica for the Application Font, which cannot correctly display some non-English characters. Starting in LabVIEW 2021 SP1, LabVIEW on Linux tries to match "sans" as the application and system fonts when the LANG does not match "en_*". Workaround: Configure the Application Font to a font that supports non-English characters. |
LabVIEW 2021 | LabVIEW 2021 SP1 f1 | Jan 25, 2022 |
| 1887820 | LabVIEW 2021 SP1 Leaks Memory
LabVIEW 2021 SP1 causes an increase in the memory usage of some applications unnecessarily over time. Workaround: You can disable the performance optimization which caused the memory leak by adding "MemoryManger.UseMasterPointerPool = FALSE" to the LabVIEW INI file. LabVIEW 2021 SP1 f1 patch fixes the issue by disabling the performance optimization by default. |
LabVIEW 2021 SP1 | LabVIEW 2021 SP1 f1 | Apr 22, 2022 |
| 166772 | Special characters (\r,\n, etc.) are not correctly converted to JSON when using LabVIEW Web services
When a LabVIEW Web service is set to the JSON output type, strings with special characters such as tab constant, carriage return constant, and end of line constant are not escaped properly. This does not include the /s character. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2015 SP1 | LabVIEW 2020 | Apr 20, 2020 |
| 168005 | Dynamic Variable API Does Not Support I/O Servers that Use Ranges
You cannot use the Variable classes, properties, and methods or the associated Shared Variable functions (Dynamic Variable API) to dynamically read and write PSP items published by an I/O Server that uses a Range item. For example, Modbus I/O Servers and Lookout Ranges are affected by this issue. Workaround: If you want to use the Dynamic Variable API to read or write one of these PSP items, you can create a network-published shared variable and bind it to the PSP item. Then you can use the Dynamic Variable API to read and write the bound shared variable. |
LabVIEW 2009 32-bit | N/A | 11/10/2009 |
| 168361 | LabVIEW Class is Locked When Not Open in Multiple Contexts
When using the Map Get/Replace Value Structure with the In-Place Element Structure, if you manipulate the value from the "Get" structure with array functions, the key inside the map will not be overwritten with the manipulated data. Workaround: Edit the array data in some way, for example, by indexing and building the array after the "get" of the key.Fixed in the LabVIEW 2021 SP1 f2 Patch. |
LabVIEW 2021 | LabVIEW 2021 SP1 f2 , LabVIEW 2022 Q3 | Jun 27, 2022 |
| 1692754 | LabVIEW Crashes After Adding Parent Interface to Class With Missing Parent Interface
LabVIEW crashes after adding a parent interface to a class if the class inherits from a parent interface that cannot be found. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 169840 | Large matrix operations that utilize the Intel MKL on Linux may crash LabVIEW
When one or more matrix operations consumes most of the system resources, the Intel MKL library produces an unhandled exception that results in a LabVIEW application crashing.This Intel library is used to accelerate fundamental linear algebra operations performed under Linux operating systems. This issue has been reproduced outside the LabVIEW execution environment and a bug report has been submitted to Intel.Because the crash is tied to system resources, it can manifest itself in many ways. For example, we have reliably reproduced the problem by:1. Decomposing a large matrix into multiple large matrices.Specific example: Computing the singular value decomposition (SVD) of a 2500-by-2500 matrix on a system with 256M RAM.2. Simultaneously computing multiple matrix operations using relatively small matrices.Specific example: Computing 30 matrix expressions using 300 x 300 matrices on a system with 512 MB RAM. Workaround: If you have identified one or more matrix operations in your application that exhibit this behavior, you have multiple options to avoid crashing.1. Serialize the matrix operations so that they are not consuming resources in parallel.2. Replace affected matrix arithmetic functions using Basic Linear Algebra Subroutine (BLAS)functions found on the BLAS palette.3. Structure your application so that these operations are not competing with other functions for system resources. |
LabVIEW 2009 32-bit | N/A | 11/10/2009 |
| 1705840 | Bundle by Name in Malleable VI Updates Wrong Cluster Item
If a cluster has a nested element with the same name as an element, a Bundle by Name function that is in a malleable VI and configured to the nested element can access the element instead of the nested element. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2018 | LabVIEW 2020 SP1 | LabVIEW 2021 | LabVIEW 2021 SP1 | Jan 6, 2022 |
| 1708546 | LabVIEW Crashes After Moving TestStand UI Controls Out of Tab Control
Moving TestStand UI controls out of tab controls in a VI panel with a splitter bar may cause LabVIEW to crash. Workaround: Make a temporary change so that the XControl is broken before copying the VI. |
LabVIEW 2019 SP1 | LabVIEW 2021 SP1 | Dec 2, 2021 |
| 1554752 | LabVIEW Cannot Build Packages After Installing 64-bit LabVIEW 2019 SP1 f4 Patch
64-bit LabVIEW 2019 SP1 cannot build packages after you install the LabVIEW 2019 SP1 f4 patch because required support files are missing. Workaround: Fixed in LabVIEW 2019 SP1 f5 patch. |
LabVIEW 2019 SP1 | LabVIEW 2019 SP1 f5 | Dec 2, 2021 |
| 170899 | When building a web service into an EXE and making an installer, some software dependencies are not automatically selected as additional installers
If you build a web service into an EXE that has method VIs with software dependencies, such as the use of a hardware driver, only VIs with dependencies that are included as Startup VIs for the web service will be automatically selected as additional installers. Any method VI that is not a Startup VI will not have its software dependencies automatically selected. Workaround: Build the web service into the installer rather than the EXE or manually include the required software dependencies |
LabVIEW 2015 SP1 | N/A | Feb 11, 2020 |
| 173080 | When a project that contains variables with binding is created in one language and opened in a different language, variables may fail to deploy
Workaround: Open the project in the desired language, double-click on the variables with binding, and re-bind the variables. |
LabVIEW 8.6 | N/A | 09/08/2009 |
| 1753009 | Usable IMAQdx Event Callback VI Cannot Be Created
After wiring an IMAQdx Session reference to the Register Event Callback function, creating a callback VI results in an incorrect callback VI reference. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 1754642 | Startup VI Does Not Run in Applications That Use Web Services and NI Web Server
The Look In Map function can sometimes erroneously use an existing data allocation instead of making a unique copy, thereby producing outputs that break dataflow semantics. Workaround: Use the Always Copy function on any input wire to Look In Map, which is also wired to other functions. |
LabVIEW 2021 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 1759565 | LabVIEW Appends Extraneous NULL Character to Path When You Drag and Drop a File to a Path Control
When you drag a file from the File Explorer to a Path control or constant, the value of the path will have an extraneous NULL character at the end. Workaround: Manually delete the extra character after completing the drag and drop.Fixed in the LabVIEW 2021 SP1 f2 Patch. |
LabVIEW 2021 SP1 | LabVIEW 2021 SP1 f2 | Jun 27, 2022 |
| 176848 | Picture Control Stops Updating After Setting Properties to Default.
Once the picture control's values have reinitialized to default by selecting Data Operations»Reinitialize to Default or programmatically using the method Reinitialize to Default, the mouse position property node stops updating. Workaround: Replace the picture control with a new one from the palette. |
LabVIEW 8.6.1 | N/A | 09/24/2010 |
| 1769482 | LabVIEW Cannot Build a Packed Project Library If VI Without Block Diagram References Malleable VIs
Trying to build a Packed Project Library using a VI that references a malleable VI and does not have a block diagram results in the following incorrect error message. "Error 1073: Unable to for this application. Choose a different option on the Additional Exclusions page and build the application again." Contrary to the error message, there are no build options that will allow the build to succeed. You must remove the malleable VI reference from the VI before removing its block diagram. Workaround: When removing block diagrams from VIs, disconnect any malleable VI references first. |
LabVIEW 2021 SP1 | N/A | Jan 6, 2022 |
| 1777709 | LabVIEW Palette Items, OpenSSH Exec and PuTTY SSH Exec, Are Not Localized
When you drag a file from the File Explorer to a Path control or constant, the value of the path will have an extraneous NULL character at the end. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 SP1 | N/A | Feb 3, 2022 |
| 1783527 | LabVIEW Crashes When New VI Object Uses Type Definition for Owner Refnum
LabVIEW crashes when the scripting function New VI Object uses a reference to a type definition for the owner refnum. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 SP1 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 178494 | Packed Library Compatibility Breaks After Implementing Parent Method
When a class uses Call Parent Class Method, but the parent class doesn't implement that method, then adding an implementation to the parent class needlessly requires the child class to recompile. If the classes are in separate packed libraries (PPLs), the child class PPL must be rebuilt. Workaround: Fixed in the LabVIEW 2019 SP1 f5 patch. |
LabVIEW 2019 SP1 | LabVIEW 2019 SP1 f5 | Dec 2, 2021 |
| 1792822 | XY Graph Can Display Incorrect Interpolated Values
When Tools > Options > Environment > General > End text entry with Enter keyis enabled, Ctrl+,Enter should add a line feed to a string. However, this keyboard shortcut is adding a new array element, if the string is an element in an array. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 181687 | Web publishing tool fails without error
The web publishing tool may fail to start the web server if the port is already reserved, yet not return an error. Workaround: Ensure that the port to be used by the web server is not in use. |
LabVIEW 8.6 | N/A | 08/03/2009 |
| 1836620 | Files Larger than 32 KB Are Truncated When Transferred Using LabVIEW SFTP
If you upload a file larger than 32 KB through SFTP, the connection will close immediately and the destination file will be truncated to 32KB. Workaround: Set block size to 16 KB in SFTP session property node. |
LabVIEW 2021 | LabVIEW 2022 Q3 | Jun 2, 2022 |
| 1847167 | LabVIEW Cannot Connect to a Remote Application to Debug
When the "error in" passed to the Python Node contains a warning, the "error out" changes the status boolean to True, which changes the warning to an error. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 1855766 | Projects That Reference High Resolution Polling Wait VI Report Missing Dependencies Needlessly
The High Resolution Polling Wait VI contains code for multiple platforms. Projects that reference this VI will report missing dependencies, though the missing libraries are for other platforms. Workaround: There is currently no known workaround for this issue. |
N/A | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 185890 | Text on a VI can be mutated to appear as Unicode
After building a project into an executable, various text for controls and indicators changes languages. It appears that the text was interpreted as Unicode.We have not been able to reproduce this in house to find a definite cause. Because of this we will leave this CAR open even though we have created code to recover from the corruption if it happens.Previously tracked as CAR 179683 Workaround: Upgrade the VI to LabVIEW 2011. In 2011 we put in code to only view text on VIs as unicode if the UseUnicode=,True is in the LabVIEW .ini file. |
LabVIEW 8.6.1 | N/A | 07/23/2010 |
| 1863309 | Python Nodes May Incorrectly Execute Serially
Using multiple Python Nodes without dataflow dependencies causes LabVIEW to serialize their execution, causing the VI to run longer than it should. Workaround: Place Python Nodes inside single iteration loops. |
LabVIEW 2021 | LabVIEW 2023 Q1 | N/A |
| 1865552 | LabVIEW 2021 SP1 Installation Fails on Some Linux Desktop Systems
LabVIEW 2021 SP1 causes an increase in the memory usage of some applications unnecessarily over time. Workaround: You can disable the performance optimization which caused the memory leak by adding "MemoryManger.UseMasterPointerPool =, FALSE" to the LabVIEW INI file. LabVIEW 2021 SP1 f1 patch fixes the issue by disabling the performance optimization by default. |
LabVIEW 2021 SP1 | LabVIEW 2021 SP1 f1 | Apr 22, 2022 |
| 186808 | Shared Variable library on PC is undeployed if the a V in the same project is programmatically deployed to a Real-Time target
When programmatically deploying a VI to a Real-Time target the Shared Variable library residing in the same project as the deployed VI will be undeployed. Workaround: Programmatically deploy the shared variable library on the PC after deploying the VI to the real-time controller. |
LabVIEW 2009 32-bit | N/A | 07/20/2011 |
| 1887467 | LabVIEW Community Edition Does Not Install on "Bullseye" Version of Raspberry Pi OS
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 188865 | When making multiple calls to Python function in a For Loop, the Python execution treats the passed data as a list, rather than a NumPy array
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2017 SP1 | LabVIEW 2020 | Apr 20, 2020 |
| 188911 | Control image alignment incorrect when "new report page" VI is used
When using Append Control Image to Report.vi, the alignment of some images are ignored when New Report Page.vi is used between appended images. This problem only exists with Office 2007. Other versions - Office 2003 and Office 2010 do not exhibit this behavior. Workaround: Use a New Report Line.vi between appending the image and the New Page.vi |
LabVIEW 2009 32-bit | N/A | 06/16/2010 |
| 1890126 | Building Applications with "Exclude Dependent Shared Libraries" Option Does Not Exclude .NET Assemblies
When building an executable or a packed library, the option "Exclude Dependent Shared Libraries" under Properties>>Additional Exclusions excludes C and C+,+, DLLs but not .NET DLLs. Workaround: Register the assembly in the Global Assembly Cache (GAC). |
LabVIEW 2021 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 1920163 | LabVIEW Application Using "Enable Enhanced DSC Run-Time Support" Option Crashes
When running an application on a PC connected to a Linux RT system, opening a type definition file from the search results in LabVIEW can cause the application to disconnect from the remote system. Workaround: Fixed in the LabVIEW 2021 SP1 f2 Patch. |
LabVIEW 2021 | NI Linux RT 21.0 | LabVIEW 2021 SP1 f2 | Jun 27, 2022 |
| 1929608 | Subtract Function Erroneously Displays Coercion of Timestamp Inputs
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 SP1 | LabVIEW 2022 Q3 | Jul 26, 2022 |
| 196607 | DTbl Replace Subset VI behavior change between LabVIEW 8.6.1 and 2009
The start input indexes from the replacement data instead of the existing data Workaround: Set the index of data to replace from 0 |
LabVIEW 2009 32-bit | N/A | 10/01/2010 |
| 198717 | Unflatten From XML fails for cluster and arrays that consist of variants
Creating a cluster that contains a variant or building an array of variants, and then trying to flatten it to XML using the Flatten To XML VI and then unflattening it using the Unflatten From XML VI will throw error 1106 Workaround: N/A |
LabVIEW 2009 32-bit | N/A | 02/01/2010 |
| 1993972 | LabVIEW Incorrectly Reads WAV Data Saved in DBL Format
Workaround: Convert DBL values to I16. |
LabVIEW 2021 | LabVIEW 2023 Q1 | N/A |
| 202192 | LabVIEW UDP broadcast is inconsistent across different OS's.
If the UDP Open VI has 0.0.0.0 wired to the Net Address terminal, the behavior varies with OS. Windows XP and NI ETS will send on all interfaces, while Windows Vista, Windows 7, VxWorks, and Linux will send on the default interface. Workaround: N/a |
LabVIEW 8.6.1 | N/A | 07/24/2012 |
| 2051887 | LabVIEW Offline Help Is Unavailable on Windows Server 2016
Workaround: Use the online help from ni.com. |
LabVIEW 2022 Q3 | Software Platform Bundle 2022 Q3 | LabVIEW 2023 Q1 | Jul 27, 2022 |
| 2052750 | Same Version of LabVIEW Is Listed Twice in Software Section of NI MAX
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2022 Q3 | N/A | Jul 26, 2022 |
| 2057366 | Loading a Project Containing RT CompactDAQ Target on LabVIEW 2022 Q3 when LabVIEW RT is Not Installed Crashes LabVIEW
Consider a case where LV 2022 Q3 and DAQmx 22.8 are installed, but not LabVIEW Real-Time. When trying to create a new project andadding an RT CompactDAQ Target to the project, clicking on the newly added target causes LabVIEW to churn for a few seconds and then crash. Steps to reproduce: Install LV 2022 Q3 and DAQmx 22.8. Do not install LabVIEW Real-time. Create a new project Add an RT CompactDAQ Target to the project Click on the newly added Target. LabVIEW will churn away for a bit and then crash. Workaround: Install LabVIEW Real-Time on the system and re-open the project |
LabVIEW NI-DAQmx 2022 Q3 | N/A | Aug 2, 2022 |
| 2058864 | Function That Converts Variant to Flattened String Produces Incorrect String Type for Set Data
Workaround: Not Applicable |
LabVIEW 2019 SP1 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 2059713 | Application Web Service Sometimes Fails to Start
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 SP1 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 2062084 | CompactRIO Single Board Controllers with NI-DAQmx Support and Real-Time Scan Resources Will Fail to Compile Bitfiles on LabVIEW 2022 Q3
Compilation failures with timing violations are likely to occur for users with C Series modules under Real-Time Scan Resources.The targets affected aresbRIO-9603,sbRIO-9608,sbRIO-9609,sbRIO-9626,sbRIO-9629,sbRIO-9638. Workaround: Use LabVIEW 2021 or earlier for these targets |
LabVIEW NI CompactRIO 2022 Q3 | N/A | Aug 2, 2022 |
| 2065508 | Using the DAQAssistant with DAQmx 2022 Q3 on LabVIEW 2022 Q3 Fails to Generate Code
Using the DAQAssistant on LabVIEW 2022 Q3 with DAQmx 2022 Q3 installed fails to configure the DAQAssistant node and gives the following code generation error: "LabVIEW Code Generation failed to execute.This may occur if the code gen engine is not properly installed, or if you are using a LabVIEW version under development" . Other workflows that use the DAQ Assistant to generate DAQmx tasks also fail. Workaround: Install LabVIEW 2021 SP1LabVIEW 2021 SP1 does not need to be activated, it is sufficient to install LabVIEW 2021 on your system and not activate it Installing just the LabVIEW 2021 SP1 run-time engine will not be sufficient, the LabVIEW ADE needs to be installed |
LabVIEW NI-DAQmx 2022 Q3 | N/A | Aug 2, 2022 |
| 208088 | Updating the Labels of a Cluster Written to a Chart Does Not Update the Cluster Used for Chart History
Changing the Label of elements in a cluster written to the Waveform Chart does not update the label of the cluster when read from the Waveform Chart Data History Property. Workaround: Temporarily wire up a completely different data type to the Waveform chart indicator and then rewire the original cluster. The changes will now propagate to the Chart History. |
LabVIEW 2009 32-bit | N/A | 03/09/2010 |
| 2081071 | LabVIEW Occasionally Crashes the Running System Exec Call That Produces Error Output
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2022 Q3 | N/A | Jul 26, 2022 |
| 2081644 | Some Localized Examples Are Missing in Example Finder
Workaround: Copy the contents of the localized exbins folders (such asC:\Program Files (x86) ational Instruments\Shared\Example Finder\1.0\Products\LabVIEW\22.0\exbins\Chinese) into the English folder (C:\Program Files (x86) ational Instruments\Shared\Example Finder\1.0\Products\LabVIEW\22.0\exbins\English),and delete thelocalized folders. |
LabVIEW FPGA Module 2022 Q3 | N/A | Jul 26, 2022 |
| 208364 | LabVIEW built installers created on a 32-bit machine will not install most drivers when run on a 64-bit machine
If you build an installer using LabVIEW on a 32-bit machine that contains National Instruments drivers, the corresponding drivers will not be installed if the installer is run on a 64-bit machine. Drivers such as NI-DAQ, NI-Sync etc. are affected by this issue. Installation on 32-bit machines are not affected by this bug. Workaround: On the deployment 64-bit machine, download and install the missing drivers from the ni.comDrivers and Updatespage. SeeKnowledgeBase 5A8KPKZL: Why Isn't the NI-DAQmx Runtime Installed on a 64-bit System By My Installer? |
LabVIEW 8.5 | N/A | 02/16/2010 |
| 2100578 | Find Parallelizable Loops Does Not Open When Invoked from Tools Menu of a VI
Tools > Profile > Find Parallelizable Loops does not work when invoked from the menu of a VI. Workaround: Invoke the menu item from the Project Explorer window's menu. |
LabVIEW 2021 SP1 | LabVIEW 2022 Q3 | LabVIEW 2023 Q1 | N/A |
| 2104674 | Unable to Install LabVIEW 2022 Q3 on Ubuntu 22.04
A default installation of Ubuntu 22.04 (Jammy Jellyfish) fails to install LabVIEW 2022 Q3 due to missing dependencies such as libncurses5, libldap-2.4-2, and libopenal1. Beginning with version 22.04, these packages are no longer shipped in the Ubuntu distribution. They were included in previous versions of Ubuntu. Workaround: From NI Linux Device Drivers 2022 Q4 or later, install ni-hwcfg-utility. It will provide LabVIEW with updated versions of components that do not rely on the missing legacy components. |
LabVIEW 2022 Q3 | LabVIEW 2023 Q1 | Oct 24, 2022 |
| 2109080 | LabVIEW Cannot Access the Microphone on macOS
Workaround: Fixed in the LabVIEW 2022 Q3 f1 Patch. |
LabVIEW 2022 Q3 | LabVIEW 2022 Q3 f1 Patch | Sep 28, 2022 |
| 213279 | Some nodes may crash or yield incorrect/inconsistent results when Inlined
An Inline public methodVI calling a private-scope method VI, inlined into a non-class caller may give a runtime error when trying to call the private method from the inlined code in the non-class caller. Workaround: Do not try to Inline VIs with these nodes. |
LabVIEW 2010 32-bit | N/A | 02/19/2010 |
| 218083 | VIs with errors may show additional errors for code in disabled frames of Conditional Disable Structure
If you have a VI that has errors in it, there may be additional errors shown. The errors will be in code that is inside of a disabled frame of the Conditional Disable Structure (in the "Default" or "Windows" frame when on RT). Workaround: Fix the other errors in the VI, and the additional errors should go away. |
LabVIEW 2010 | N/A | 07/23/2010 |
| 219819 | Center justified tables display improperly when overlapping with the front panel origin
When you add a table control to the front panel so that it overlaps with the vertical origin of the front panel, LabVIEW displays center justified columns off center when you type text. The cells appear to float or move horizontally until aligned with the vertical origin. Formerly tracked as 50061 and 42NAR8SA Workaround: Move the table away from the front panel's vertical origin. |
LabVIEW 8.0.1 | N/A | 09/01/2007 |
| 221202 | System decoration frame bleeds through system checkbox boolean text
In a System Tab Control with a System Decoration frame, the color bleeds through the boolean text of a system checkbox. Workaround: Use a normal button control configured as an indicator behind the boolean text, and resize it to match the width of the text. |
LabVIEW 2016 | N/A | May 16, 2019 |
| 221253 | Bundle by Name function can send wrong pointer into subVI with Call Library Function Node
If a main VI has the output of a Bundle by Name function connected to a subVI, a Call Library Function node within the subVI can receive the wrong pointer from the wired cluster. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2013 SP1 | LabVIEW 2020 | Aug 7, 2016 |
| 2226492 | LabVIEW Crashes When Changing the Tabbing Order of Front Panel Controls
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2022 Q3 | LabVIEW 2023 Q1 | N/A |
| 2252794 | Constructor Node Lists .NET Methods Instead of Constructors When Selecting Parameter
Clicking on a Constructor Node parameter to choose a different constructor results in the menu listing methods incorrectly. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2021 SP1 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 2254316 | LabVIEW Python Node Returns Error 1672 When Trying to Return an Array with NumPy Library Version 1.24
With the 1.24 release of NumPy,Python Nodes that return arrays are failing with the error code 1672. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q1 | LabVIEW 2023 Q1 | N/A |
| 2262038 | File Dialog Does Not Support Some Patterns That Worked in Earlier Versions
The File Dialog no longer works with NULL characters in the Pattern input to present multiple filters.This change in behavior can affect applications that were built with the option "Allow future version of LV Runtime to run the application." Workaround: There is currently no known workaround for this issue. |
LabVIEW 2022 Q3 | N/A | Feb 9, 2023 |
| 2263807 | Activate Button Does Not Work in LabVIEW Evaluation Reminder Dialog
Workaround: UseHelp>Activate LabVIEW Componentsfrom the LabVIEW menu or run the NI License Manager. |
LabVIEW 2023 Q1 | LabVIEW 2023 Q3 | Feb 9, 2023 |
| 226840 | Formula VI does not execute pow(x,y) function
Workaround: Use the formula node to use the pow(x,y) function. If you need to change this programmatically, use the Power of X function in G code. |
LabVIEW 2009 32-bit | N/A | 10/01/2010 |
| 227030 | Wait on Notification from Multiple function has unexpected behavior when ignoring previous input.
Workaround: See KB |
LabVIEW 8.0 | N/A | 07/23/2010 |
| 227609 | Statically linking a LabVIEW built DLL in a C+,+, project results in error 998 if the DLL is not added to the Delay Loaded DLLs list
Workaround: Go to the Project Property Pages, Configuration Properties»Linker»Input and add the name of your DLL to the Delay Loaded DLLs list. |
LabVIEW 7.1.1 | N/A | 06/16/2010 |
| 229641 | Hang can occur when deploying RT project that has not been check out of VSS
When using VSS source code control for a real time project and trying to deploy code that has not been checked off the deployment window blocks a pop up from VSS saying that the code has not been checked out. The deployment status window is modal so it does not allow you to select to proceed in the VSS window. Workaround: In the LabVIEW project properties disable the prompts from source code control. Or you could make sure that the VIs are saved prior to deploying. |
LabVIEW 2009 32-bit | N/A | 07/23/2010 |
| 232348 | Changes to a library item's access scope sometimes do not update broken callers.
Changing a library item's access scope sometimes does not update callers which are broken only because they were attempting to access an item which was out of scope to them. Workaround: Force recompile (ctrl+,click on the run arrow) any VI which incorrectly believes that access scope forbids access to it's dependency. Changing the access scope to another value, then back to the desired value while the VI is open will also fix the issue. |
LabVIEW 2010 32-bit | N/A | 07/23/2010 |
| 233061 | LabVIEW crashes after working with Simulation Subsystem using a LabVIEW Class
Sometimes LabVIEW will crash after working with a Simulation Subsystems that has a LabVIEW Class as one of its controls or indicators on its connector pane. Usually it is only a problem when working with the Subsystem's caller within a LabVIEW Project. The crash will occur after closing the project, while returning to the initial LabVIEW window. Workaround: Save all work before closing the LabVIEW Project when using LabVIEW Simulation and Classes together. |
LabVIEW 2010 32-bit | N/A | 11/10/2011 |
| 2330658 | Unexpected Error Occurs When Running Sound VIs on LabVIEW for macOS
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q1 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 2331372 | LabVIEW Sometimes Crashes When Labels Contain a Mix of Unicode and Non-Unicode Characters
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2022 Q3 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 2342514 | Open Venv Python Session.vi Does Not Work For Paths With Spaces
Open Virtual Environment Session.vi with the Open Venv Python Session configuration returns error 1671 ("Error creating python session") if the Env path contains any spaces. Workaround: Create a directory hard symlink viamklink /Jthat does not contain spaces and use that path in LabVIEW. |
LabVIEW 2023 Q1 | LabVIEW 2023 Q3 | May 2, 2023 |
| 2345599 | Probes for Queues and Sets Sometimes Show Erroneous Data
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2019 SP1 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 235019 | OpenSSL fatal error when LabVIEW exits
The OpenSSL fatal error possibly occurs when using Search features in LabVIEW for the first time after installation. Workaround: Launch LabVIEW and exit when Getting Started Window opens. The error now goes away in future launchings. |
LabVIEW 2010 32-bit | LabVIEW Unknown | 08/03/2010 |
| 2350519 | New Override VIs Do Not Have Parent Icon
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q1 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 236193 | Crash with invalid input (o or negative values) of "samples per channel" when misusing TDMS Set Channel Information
There are some situations if you set the value of "samples per channel" of TDMS Set Channel Information as 0 or negative values (invalid values), which could cause a crash. Workaround: Avoid using 0 or negative values as "samples per channel". |
LabVIEW 2010 | LabVIEW 2010 CVI | 02/18/2011 |
| 236377 | Dropping XControl from public library breaks XControl
When adding an X control from a public library into the controls palette, it become broken when dropped down to the front panel from the controls palette. Workaround: Include a merge VI in the functions palette |
LabVIEW 2009 32-bit | N/A | 10/01/2010 |
| 236817 | NI-Auth does not work with Firefox
Web Services using NI-Auth work incorrectly in Firefox. A user's log in credentials will never be accepted. Workaround: Use Internet Explorer |
LabVIEW 2010 32-bit | LabVIEW Unknown | 08/03/2010 |
| 238713 | 3D Picture Controls can display transparently or crash LabVIEW on certain graphics cards
The 3D Picture Control is built on aOpenSceneGraphwhich uses OpenGL. Several reports of the 3D picture control crashing LabVIEW have been reported. In almost all cases it was an Intel integrated graphics card involved. This crash is caused by an incompatibility of the graphics hardware.Note: Many of the 3D Graphs use the 3D Picture Control Workaround: There have been several things that have worked for users:Update the video driverTurn on/off hardware accelerationTurn on Aero in Windows 7Turn off Aero in Windows 7 |
LabVIEW 2009 32-bit | N/A | 04/20/2011 |
| 2392126 | List of Objects in Quick Change Dialog Is Not Localized
Workaround: Not Applicable |
LabVIEW 2023 Q3 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 239631 | Memory Growth with TDMS Write
With the standard TDMS API, when TDMS Write VIs are executed the API will build a cache in memory. This may present as a memory leak, as this memory is only cleared in specific situations. Workaround: SeeKnowledgeBase 5WQD51YS: Memory Growth with TDMS Writefor more information. |
LabVIEW 2009 | N/A | 04/27/2012 |
| 239719 | Property page doesn't update when Adapt to Source is coerced to off
If you have a FXP constant with Adapt to Entered Data set and make any modifications to the display format, the resulting constant will not be set to adapt. The property page will not reflect this change before it is closed. Workaround: Always double-check condition of Adapt To Entered Data. |
LabVIEW 2010 | N/A | 08/03/2012 |
| 2398515 | Error 56 Occurs When Using SFTP VIs with Password Authentication on Windows 11
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q1 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 2407732 | Table Control Does Not Respond Correctly to Touchpad Scroll Gestures
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2022 Q3 | LabVIEW 2023 Q3 | Jul 20, 2023 |
| 243468 | Default Namespaces not supported in XML Parsing VIs
When trying to work with XML Parsing VIs you will get error -2768Possible reason(s):LabVIEW: The XPath expression does not conform to XPath syntax. Refer to the W3CXPath Web site at http://www.w3.org/TR/xpath for more information about XPath syntax. Workaround: Remove the default namespace (example: remove xmlns=,"http://www.ieee.org/ATML/2007/TestResults"), |
LabVIEW 2010 32-bit | N/A | 08/17/2010 |
| 2440992 | Using the Right-Click Menu Plugin to Lookup All Shortcut Menu Tags and Types Does Not Display Expected Results
Workaround: Not Applicable |
LabVIEW 2020 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 244551 | Editing large strict type definitions can take a long time to update
When large type definitions are updated, all instances in memory require an update. This update can take many minutes for very large type definitions. Workaround: Use smaller type definitions, or consider using LabVIEW classes to contain your type data. |
LabVIEW 7.1.1 | N/A | 07/23/2012 |
| 245148 | Class Properties dialog sometimes throws timeout error 123 when opening and must be restarted
In LV 2010, there appears to be a timing race condition in the Class Properties dialog for LabVIEW classes. Every once in a while if you try to launch the dialog, the dialog will throw an error dialog reporting error 123 that the dialog has timed out while trying to launch. After you dismiss the dialog, you may see a secondary error dialog. Once you dismiss that, you can relaunch the Class Properties dialog and will generally succeed. There is no danger to your class and no corruption to you class file has occurred. It is solely a bug in trying to launch the dialog. Workaround: Hit Continue or OK button to dismiss all error dialogs that come up then retry opening the Class Properties dialog. |
LabVIEW 2010 32-bit | N/A | 02/18/2011 |
| 245359 | Selecting a newer version of a .NET assembly does not reload assembly
Changing a constructor from an old version of a .NET assembly to a newer version at edit time does not cause the new assembly to be loaded and consequently none of the new functionality is available. Workaround: 1. Remove the old assembly so the .NET Runtime is not able to find it. It will then return the updated version to LabVIEW.2. Load the new assembly in a blank VI before opening your existing VI. This will load the new version into memory prior to you requesting the older version. |
LabVIEW 2010 32-bit | N/A | 08/03/2012 |
| 2461486 | Error While Upgrading SystemLink Server or LabVIEW 2023 Q1 to 2023 Q3 because of SystemLink Message Broker
Users upgrading to SystemLink Server 2023 Q3 (23.5) or LabVIEW 2023 Q3 (23.3) will encounter an installation error due to an issue upgrading the ni-systemlink-message-broker package, if they've previously installed SystemLink Server 20.0 or LabVIEW 2020 (RabbitMQ 3.8.2), then updated to 21.x or 22.x version of SystemLink Server or LabVIEW, before updating to SystemLink Server 2023 Q3 (23.5) or LabVIEW 2023 Q3 (23.3). Workaround: There is currently no known workaround for this issue. |
LabVIEW 2022 Q3 | LabVIEW 2023 Q3 | Feb 9, 2023 |
| 2479826 | Control Can Have Unexpected Default Value When Created Using Double Click During Wiring
When you create a control by double-clicking when wiring from a subVI terminal , the control can have a default value that is different from the displayed value. Workaround: Not Applicable |
LabVIEW 2023 Q3 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 2481419 | Incorrect Value Returned When Reading Class Name Property of Some Event Structure Terminals
Using VI Scripting, reading the Class Name property of the Dynamic Terminal or Timeout Terminal of an Event Structure returns "Generic" instead of "Tunnel." Workaround: Not Applicable |
LabVIEW 2020 SP1 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 248421 | Bitshift does not work correctly in Expression Nodes and Formula Nodes with a data type smaller than I32
Workaround: N/A |
LabVIEW 8.5.1 | N/A | 10/29/2010 |
| 248914 | Changing the order of controls or deleting controls in a type def cluster can change references
When you create a reference for a control in a type defined cluster LabVIEW uses the cluster order to determine what control the reference is referring to. Say you have a type defined cluster with elements A, B, C and D with cluster order 1,2,3 and 4 respectively. On the block diagram of a VI you have control references to each of the controls. If you open the type def and delete control C the block diagram of the VI will only contain 3 references. Moreover, the reference that used to be for control C will now reference control D. This is because the control is based on cluster order Workaround: N/A |
LabVIEW 7.1.1 | N/A | 10/01/2010 |
| 250588 | Warning Generated in a Method or Property of an XControl Appears as an Error in the Top Level VI
If you create a method or a property in an Xcontrol in which you have implemented code to generate a warning it is transformed into an error in the calling VI. Workaround: In the VI look for specific error and transform back to a warning |
LabVIEW 8.5.1 | N/A | 11/02/2010 |
| 251105 | S&,V XControls built as Remote Panel crashes LabVIEW.
Remote panels do not reliably support the Sound and Vibration XControls. Workaround: Use another mechanism for remote viewing. |
LabVIEW 2009 32-bit | N/A | 02/18/2011 |
| 2516141 | 64-bit Values Incorrectly Converted to 32-bit in Expression Node
Workaround: Not Applicable |
LabVIEW 2021 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 2519019 | Built Application Searches for NI_Matrix.lvlib:RealMatrix.ctl When Run
When you run an application built with the matrix datatype, the application searches for NI_Matrix.lvlib:RealMatrix.ctl. Workaround: Not Applicable |
LabVIEW 2023 Q3 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 2519561 | Distributed System Manager Does Not Open When Called from the Tools Menu in LabVIEW
Workaround: Fixed in LabVIEW 2023 Q3 Patch 2. |
LabVIEW 2023 Q3 | LabVIEW 2023 Q3 Patch 2 | Jan 10, 2024 |
| 2543964 | Shared Variable Properties Dialog Is Missing Some Options
The Shared Variable Properties Dialog Box lacks the following categories provided by the LabVIEW Real-Time and LabVIEW Datalogging and Supervisory Control modules: RT FIFO, Alarming, Update Deadband, Initial Value, Logging, and Security. Workaround: Fixed in LabVIEW 2023 Q3 Patch 2. |
LabVIEW 2023 Q3 | LabVIEW 2023 Q3 Patch 2 | Jan 10, 2024 |
| 2552750 | Incorrect Wiring After Inserting Some Functions On Set and Map Wires with Quick Drop
After inserting a Remove From Set or Remove From Map function using Quick Drop, the output wire is not connected to the correct terminal. Workaround: Not Applicable |
LabVIEW 2020 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 255466 | Shared variable moved from a project directly to a tab control is not added to the active page.
Workaround: After dragging the variable to the tab control. Reselect it and drag it slightly until the dotted lines appear around the tab control page and then drop it. The shadow is then removed because the variable has been added to the active page. |
LabVIEW 2010 32-bit | N/A | 12/15/2010 |
| 2558611 | Some Parts of a VI Diagram Do Not Execute in Parallel
In rare cases, some parts of VI diagrams do not execute in parallel when the same code had done so in earlier versions of LabVIEW. Workaround: Fixed in LabVIEW 2023 Q3 Patch 2. |
LabVIEW 2019 | LabVIEW 2023 Q3 Patch 2 | Jan 10, 2024 |
| 2561077 | LabVIEW Crashes When Importing a Shared Library
LabVIEW crashes when using the Import Shared Library tool to import a DLL. Workaround: Fixed in LabVIEW 2023 Q3 Patch 2. |
LabVIEW 2023 Q3 | LabVIEW 2023 Q3 Patch 2 | Jan 10, 2024 |
| 256141 | Windows 7 often shows "(Not Responding)" and will bring other windows to the front during expensive operations
If Windows 7 if a window is unresponsive to user input (e.g. mouse clicks) for five seconds it will ghost the window and display "(Not Responding)".Some operations in LabVIEW run in the UI thread. This is to prevent different operations from happening in parallel (e.g. compiling, edit operations, saving, drawing, etc.). Because large block diagrams can take longer than five seconds to compile or run clean up on Windows can tag LabVIEW as Not Responding.In some cases the ghosted window can move behind the other open windows when it finishes it task. Workaround: Wait until the expensive task as finished before trying to interact with the window. |
LabVIEW 2009 32-bit | N/A | 10/28/2010 |
| 2565540 | Sort 2D Array.vim is Unexpectedly Slow When Operating on a Sorted Array
Workaround: Not Applicable |
LabVIEW 2020 SP1 | LabVIEW 2024 Q1 | Jan 22, 2024 |
| 257194 | Connector pane of a VI can change from LabVIEW 2009 to LabVIEW 2011
If you have a VI with no items in the connector pane and upgrade it straight form LabVIEW 2009 to LabVIEW 2011 then the connector pane may change Workaround: Open in LabVIEW 2010 first |
LabVIEW 2011 32-bit | N/A | 08/02/2011 |
| 257275 | Format Into String does not work with the %d format for numbers larger than I32
The Format Into String VI does not correctly format numbers outside the 32-bit integer (I32) range when using the '%d' format. When the number is outside the I32 range, the resulting string displays either -2147483648 or 2147483647 depending on if the number is negative or positive. Workaround: Use %.0f instead of %d as the format string. |
LabVIEW 2010 32-bit | LabVIEW 2015 | 12/31/2010 |
| 257735 | Class VIs that call shared variables in a library in an auto-populating folder will not be loaded
If a VI in a class calls a shared variable that is in a library in an auto-populating folder, it will not find the shared variable when the project is loaded Workaround: Make the folder a snapshot instead of auto-populating and reopen the project |
LabVIEW 8.6.1 | N/A | 02/01/2013 |
| 2599334 | WebDAV, HTTP, and SMTP Functions Fail to Use Certificates from Files
Configure SSL (WebDAV), Asynchronous Configure SSL (WebDAV), ConfigSSL (HTTP Client), and Config TLS (SMTP) functions fail to use certificate files but do not return errors. Workaround: Copy any needed certificates into the Windows certificate store. |
LabVIEW 2023 Q1 | LabVIEW 2024 Q3 | Jan 22, 2024 |
| 2625975 | LabVIEW Crashes After Clicking the Help Button in Application Properties
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q1 Patch 1 | Jan 22, 2024 |
| 275961 | Silver style Thermometer frame doesn't resize correctly when control is resized.
Workaround: N/A |
LabVIEW 2011 32-bit | N/A | 03/08/2011 |
| 278730 | Web Services ignore the No App switch on RT targets
After deploying the web service to a RT target, it become like a start up executable. Any time the target is reboot, the web services re-starts automatically. However, unlike with start up executables, the web service can't be turned off by the No App switch. Workaround: N/A |
LabVIEW 2011 32-bit | LabVIEW 2015 | 02/10/2011 |
| 279373 | SMTP has been updated to use port 587, LabVIEW makes use of legacy port 25
The SMTP has been updated to use port 587 instead of port 25. LabVIEW still makes use of port 25 with its SMTP VIs. Workaround: Open any SMTP VI, and find the SMTP_CreateSession.vi. Open that VI, you will find a numeric constant on the block diagram that is set to 25. |
LabVIEW 2010 32-bit | N/A | 08/02/2011 |
| 282737 | Applications with Chinese characters in the executable name will throw fatal error on English Windows 7
Workaround: Use a different name for the executable. |
LabVIEW 2010 32-bit | N/A | 08/02/2011 |
| 284289 | Source distributions with block diagrams removed prevents the use of static Shared Variable nodes.
Source distributions that include static Shared Variable nodes with block diagrams removed will return the following error at run-time, "VI has a bad connection to or cannot find a subVI or external routine." Workaround: Use theProgrammatic Shared Variable APIor do not remove the block diagrams. |
LabVIEW 2010 32-bit | N/A | 07/20/2011 |
| 284936 | Breaking one Override VI in LVOOP shows all siblings as broken but does not explain why
When using OOP in LabVIEW, breaking the connector pane of a child class Override VI will make all of its sibling override VI's appear broken even though they are not broken. Hitting run on the broken Run Arrow of any child class Override VI will list all of the child class VIs in the list of "Items with Errors", but none of them will have an error associated with it except for the broken ones. Workaround: Use the red X in the errors window to find the actual broken VI |
LabVIEW 8.6.1 | N/A | 04/20/2011 |
| 289842 | Get Variant Attribute VI returns wrong value if attribute not found
The default value that's returned by the Get Variant Attribute VI is not blank when nothing is wired to the default value terminal. The Get Variant Attribute instead seems to return the last/previous value it returned as the default value. Workaround: Use the Found? output and logic to return a blank variant if necessary |
LabVIEW 8.6.1 | N/A | 03/21/2011 |
| 290105 | Text Labels in Silver Control are not in silver style
Workaround: N/A |
LabVIEW 2011 32-bit | N/A | 04/05/2011 |
| 294285 | Type Defined Shared Variable not found in Executable
When a VI is made with the following conditions:1) Uses a Shared Variable attached to a type definition2) The type defined control (attached to the shared variable) is not in the main project directory (ie, it is in a different folder)3) The VI uses dynamic data (or waveform to dynamic data function)A created executable seems to not include the *.ctl file defining the shared variable type. This missing type definition causes the run time engine, when starting the executable, to search for and (if the control is not located in the searched directories) fail to find the *.ctl file. If the location of the *.ctl file is specified, the executable runs without issues. Workaround: Disconnect from Type Def during the build. |
LabVIEW 2010 32-bit | N/A | 08/02/2011 |
| 305978 | Save As Duplicate with Include All Dependencies makes a Copy of the instr.lib Folder.
Include All Dependencies option in Save As does not ignore files from laview\instr.lib folder. Workaround: Choose "Select contents to copy" and uncheck instr.lib |
LabVIEW 2010 32-bit | N/A | 08/02/2013 |
| 314082 | Listbox Control With Transparent Cell Background Does not Grey Disabled Item
n/a Workaround: Make the background color of the cells match the background of the panel, instead of making them transparent. |
LabVIEW 2011 32-bit | N/A | 09/07/2011 |
| 316372 | Newly created typedefs are not automatically added to library
When creating a subVI from a VI contained within a library, the subVI is added to the caller VI's library. When creating a typedef from a control in the same VI, the typedef is not added to the library. Workaround: Manually add the typedef to the library. |
LabVIEW 2010 32-bit | N/A | Feb 17, 2020 |
| 316382 | When using a LabVIEW-built .NET Interop Assembly in an ASP .NET application, the first call to the assembly will return a NullReferenceException
Workaround: The exception only occurs on the first call to the assembly, so using a try-catch block to handle the exception will allow subsequent calls to behave normally. |
LabVIEW 2015 SP1 | LabVIEW 2021 | Feb 14, 2020 |
| 316578 | Aborting a VI can leave VIs targeted by a Call By Reference node reserved permanently
Workaround: Close the project to unreserve the VI |
LabVIEW 2013 | LabVIEW 2020 | Feb 18, 2020 |
| 316598 | Mass Compile causes LabVIEW crash
LabVIEW 2018 64-bit crashes during Mass Compile if Vision VIs are included, but the Vision Development Module is not installed. Workaround: Install the Vision dependencies that are required. |
LabVIEW 2018 | N/A | Aug 13, 2018 |
| 316619 | .NET Constructor Node cannot differentiate between functions with different enums at the same position
Workaround: Create a wrapper assembly to call from LabVIEW |
LabVIEW 2014 | N/A | Jun 16, 2015 |
| 317117 | 3D Surface Graph incorrectly blends colors when interpolating
In certain situations when viewing a projection onto a 2D plane, the 3D Surface Graph can incorrectly blend colors instead of displaying them in a straight line. Workaround: N/A |
LabVIEW 2011 32-bit | N/A | 05/22/2017 |
| 317596 | Cannot Scroll Array Indicator with Mouse Wheel in Running VI
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2017 | LabVIEW 2023 Q1 | N/A |
| 320200 | EXE including 'Std Deviation and Variance' VI is unloadable
Building an executable including a VI that uses the 'Std Deviation and Variance' VI results in an error: "(Hex 0x464) VI is not loadable". Workaround: There is currently no known workaround for this issue. |
LabVIEW 2018 | LabVIEW 2020 | N/A |
| 320485 | User Events Created from Objects Cause Broken Packed Library VIs
If you are using an object as a user event, it works fine while in the LabVIEW environment. However, when compiled into a packed library, the user event refnum has a broken wire. Workaround: N/A |
LabVIEW 2010 SP1 32-bit | N/A | 08/02/2011 |
| 322914 | Formula VI does not execute pow(x,y) function
Workaround: Use the formula node to use the pow(x,y) function. If you need to change this programmatically, use the Power of X function in G code. |
LabVIEW 2009 32-bit | N/A | 10/01/2010 |
| 335576 | Play Waveform Express VI gives error 4803 with Sample Rate 3125, 6250, 12.5K, 25K, 50K, 100K, 200K Hz
n/a Workaround: Instead of using the "Play Waveform" Express VI, use the code from the example Generate Sound.vi. |
LabVIEW 2010 SP1 32-bit | N/A | 08/03/2012 |
| 339230 | Newly created typedefs are not automatically added to library
When creating a subVI from a VI contained within a library, the subVI is added to the caller VI's library. When creating a typedef from a control in the same VI, the typedef is not added to the library. Workaround: Manually add the typedef to the library. |
LabVIEW 2010 32-bit | N/A | 03/05/2018 |
| 347272 | Executables built (without SSE2) in LV 2011 on an Intel Core Duo machine throw Error 57 when run on a machine with an AMD Athlon 3200+, processor.
n/a Workaround: Build the executable on the Athlon 3200+, computer. |
LabVIEW 2011 32-bit | N/A | 08/03/2012 |
| 351506 | [Mac] Test Device option on Play Waveform Express VI Configuration page doesn't output test tone
N/A Workaround: N/A |
LabVIEW 2011 32-bit | N/A | 05/07/2012 |
| 351741 | Panes 'Top' pixel coordinates will vary when Windows 'Aero' is enabled/disabled
If the Windows Vista/7 option to "Use visual styles on windows and buttons" is enabled, a VI property node for Front Panel Window:Panel Bounds will return a different 'Top' value. Workaround: If you are calculating the position of elements within your VI based on this value, check the deployed OS, and subtract an offset value. |
LabVIEW 2011 32-bit | N/A | 05/07/2012 |
| 353261 | Conditional Indexing Terminal on Parallel For Loop with Shift Registers Runs with "Memory is Full Error"
Workaround: Use the Build Array in a Case structure |
LabVIEW 2012 32-bit | N/A | 08/03/2012 |
| 355840 | "Get Image" method is unreliable on .NET controls in LabVIEW (64-bit)
Calling the 'Get Image' method on a .NET control works correctly on 32-bit versions of LabVIEW, but will fail to return an image intermittently when LabVIEW (64-bit). Workaround: n/a |
LabVIEW 2011 64-bit | N/A | 08/03/2012 |
| 356420 | Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name
Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name Workaround: Move the manifest file to a new location |
LabVIEW 2012 | N/A | 07/13/2012 |
| 356656 | Crash when compiling VIs that call into a certain class based VI hierarchies
Some VIs that call into a formerly non-dynamic dispatch member of a class whose parent is missing may crash when saved or mass compiled. Workaround: Open the class first, then open the VI and save it. |
LabVIEW 2011 32-bit | N/A | 08/03/2012 |
| 357785 | Mouse cursor does not scale properly on a 4k monitor
The mouse size shrinks when entering the block diagram or front panel when using a 4K monitor but is the correct size on the menu bar. Workaround: Set the display settings to 100% scaling and 1080p resolution. |
LabVIEW 2019 | N/A | Jan 6, 2021 |
| 359662 | Some dotted scripting property calls can crash LabVIEW if earlier properties error
If you access the property LinkedControl.ClassName on an object that does not have a linked control error 1308 will be thrown. If you access the property 3 times, LabVIEW will crash. Workaround: Separate into two calls, e.g. change a property of LinkedControl.ClassName into a call to LinkedControl, which emits a reference and, if successful, wire that to a second property node to get ClassName. |
LabVIEW 2010 SP1 32-bit | N/A | 07/11/2012 |
| 361311 | "Natural log of 1 +, x" primitive incorrectly returns NaN for small positive values
n/a Workaround: n/a |
LabVIEW 2011 32-bit | LabVIEW 2015 | 08/03/2012 |
| 364338 | "Error while retrieving database: Forbidden" connecting to a RT target via the web configuration.
If you change the admin password for an RT target and reboot the target before saving, you may receive the error "Error while retrieving database: Forbidden." Workaround: Refresh the web page hosting the web configuration. |
LabVIEW 2012 | N/A | 08/03/2012 |
| 364845 | Streaming data to a Digital Display Chart data occasionally incorrectly displays zero even when the data is non-zero
N/A Workaround: N/A |
LabVIEW 2012 | N/A | 01/29/2013 |
| 367249 | It is not possible to customize the Run-Time Shortcut menu of a 3D Graph
N/A Workaround: N/A |
LabVIEW 2012 | N/A | 01/29/2013 |
| 369142 | Front Panels may stop updating with 3+, monitors with Windows Aero enabled
With Windows Aero enabled on a machine with 3 or more monitors the front panel may stop drawing. This issue has been seen in limited cases and is usually after hours of operation. The application itself continues to run. Moving or minimizing the window causes it to start updating again. Workaround: Disable Windows Aero by selecting a non-Aero theme. |
LabVIEW 2010 SP1 | N/A | 09/01/2012 |
| 377385 | Error 1390 on Dynamic VI Call to Friend Library
The error is returned when two Community scoped LabVIEW Libraries are Friends to each other, and one Library performs a dynamic call to a VI in the other Library. Workaround: Change the dynamic call to a static call, or change the scope to Public on the Library containing the callee VI. |
LabVIEW 2012 | N/A | 01/28/2013 |
| 381128 | The MonthCalendar .NET control automatically resizes to the incorrect size when the VI is run
N/A Workaround: At the beginning of the code write to the Container Bounds property node "ContBounds" for the .NET container. While the code is running the calendar will have the right size |
LabVIEW 2012 | N/A | 02/01/2013 |
| 381656 | Adding or subtracting timestamps causes a conversion to double and precision loss
N/A Workaround: Cast the timestamps to clusters of U64 'seconds since epoch' and I64 'fractions of a second' before the operation and then cast back to timestamp after the operation |
LabVIEW 2011 | N/A | 01/29/2013 |
| 384591 | A password protected VI accessing a password protected community scoped VI is broken if the VIs are set to separate compiled code from source code
This only happens if the VI source-only option set to true: Tools -> Options -> Environment Settings -> Separate Compiled Code from New Files set to true, or via the VI Properties window Workaround: Do not separate the compiled code from the source code or remove the password |
LabVIEW 2011 SP1 | N/A | 05/09/2014 |
| 388446 | Eval Parsed Formula Node.vi returns incorrect results
Incorrect results are possible if preceding Parse Formula Node.vi contains too many C-style comments. Workaround: Reduce the amount of comments used in formula input to Parse Formula Node.vi |
LabVIEW 2012 | N/A | 08/02/2013 |
| 389041 | Error -314250 from Create Network Stream Writer Endpoint
Error is returned when data type is set with a SGL value that has a unit label defined. Workaround: Change representation or DBL, or remove the unit label. |
LabVIEW 2013 | N/A | 08/02/2013 |
| 390021 | An inlined VI can not be placed on the block diagram of a VI with subroutine priority unless it also has subroutine priority
Inlined VIs should ignore the Priority setting in VI properties, however an inlined VI dropped in a subroutine priority VI will break the run arrow unless the inlined VI is also set to subroutine priority. Workaround: Set the inlined subVI to subroutine priority |
LabVIEW 2012 | N/A | 03/11/2014 |
| 391455 | Applying an icon to LabVIEW class overwrites the icons of its methods
The icon for a LabVIEW class appears to be only the banner, but when it is applied it overwrites the entire icon of the method VIs Workaround: N/A |
LabVIEW 2012 | N/A | 08/02/2013 |
| 39161 | The device ID input of the Play Sound File VI does not work on Windows
On Windows, LabVIEW ignores the device ID input of the Play Sound File VI. This VI plays sound only on the default sound card. Workaround: Use the Sound Output Configure VI and the Sound Output Write VI with the Sound File Open VI and the Sound File Read VI or the Sound File Simple Read VI. Refer to the Sound File to Sound Output example VI for an example of this workaround. |
LabVIEW 8.0.1 | N/A | 09/01/2007 |
| 391784 | Memory Lead when Sound VIs are Called Dynamically
Sound Input Configure.vi and Sound Input Clear.vi leak memory when called dynamically Workaround: Use a static call to these VIs. |
LabVIEW 2012 | N/A | 08/02/2013 |
| 392232 | Autopreallocate Arrays and Strings VI Property Can Crash LabVIEW when not in FPGA Context
Changing an FPGA VI to run in a context other than FPGA does turn off the VI property to Autopreallocate arrays and strings if it was previously turned on. Running a VI that has this property on and manipulates arrays or strings can cause LabVIEW to crash. Workaround: Uncheck the Autopreallocate arrays and strings VI property for the VI. |
LabVIEW 2010 | LabVIEW 2015 | 08/02/2013 |
| 392446 | Installing LabVIEW on a Windows Laptop Decreases Battery Life
Even with NI applications closed, services installed by LabVIEW request high resolution timers. These timers prevent the hardware from sleeping, and requires more power. Workaround: N/A |
LabVIEW 2012 SP1 | LabVIEW 2015 | 08/02/2013 |
| 392545 | Timed Loop crashes LabVIEW after exiting
A timed loop that meets these criteria can crash LabVIEW after finishing execution.1) The Timed Loop must write to the "Offset" input node inside the loop2) The Timed Loop must have set the "Mode" input node to anything else other than "No Change" or "Discard missed periods, ignore original phase" before the loop begins Workaround: Configure the Timed Loop once at the beginning of execution instead of each iteration. |
LabVIEW 2012 | N/A | 08/02/2013 |
| 394454 | Data Binding: Path property can change bindings in other VI clones
Writing to a Data Binding: Path can change binding path for other instances of the control if clones of the VI are already open Workaround: Use programmatic Shared Variable access to update front panel controls instead of Data Binding. |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 398998 | 3D Surface Axis Labes not Visible when Dialog Font Changed
Some fonts cause the Axis Labels to be visible on 3D Surface controls when the Dialog Font is changed from default. For example MS Sans Serif causes the issue. Workaround: Use a Dialog font that doesn't cause the issue. |
LabVIEW 2012 | N/A | 08/02/2013 |
| 399068 | Double Numeric Slide can not be Set to 0 when it has Defined Limits with Mouse
A user can not slide a Double Numeric Slide to 0 when it has defined increment, maximum, and minimum properties. Instead of 0, a value very close to 0 will be entered ie: 5.55112E-16. Workaround: Do not set both defined maximum and minimum for the slide. Instead, change one of them to Inf or -Inf. Also a value of 0 can be entered into the digital slide. |
LabVIEW 2012 | N/A | 08/02/2013 |
| 400736 | Error -4403 returned from Write Palette.vi for Template VIs
Template VIs can not be added to the palettes with the Write Palette.vi, error -4403 will be returned. Workaround: Add Template VIs to the palettes manually through Tools»Advanced»Edit Palette Set... |
LabVIEW 2013 | LabVIEW 2015 | 08/02/2013 |
| 401078 | Opening any non-VI dialog, such browse for files or one button dialog, may block web service requests from executing.
The most common form of this issue seen when Show Method URL Dialog Box blocks requests to a LabVIEW Web Service. This only affects LabVIEW web services deployed to the debug server or embedded in a LabVIEW executable. Workaround: Close the dialog box to allow requests to continue |
LabVIEW 2013 | N/A | 12/01/2014 |
| 401421 | Updates to Global Variables Not Visible when Remote Debugging a LabVIEW Built Stand-Alone Application
If the updates occured before connecting to the Remote Application with the debugger, the updates won't be visible. Updates to the Global Variable after connection with the debugger is establish will be visible. Workaround: Change the build specification for the stand-alone application to wait for debugger on launch, so no Global Variable updates can happen until a debug session is started. |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 401689 | Constrained Non-Linear Optimization VI has Potential for Infinite Loop
Depending on the function data, Constrained Non-Linear Optimization can execute indefinitely. No checks are done in subVI for infinite loop. Workaround: Enter in your own check to see infinite loop is occurring. |
LabVIEW 2012 SP1 | LabVIEW 2015 | 08/02/2013 |
| 403182 | Sound Output.vi Does Not Support more than 2 Audio Channels on Windows 7
Error 4811: "can not support sound format" will be returned from the VI when executed on Windows 7. Workaround: More than 2 Channels are supported on Windows XP. |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 403727 | Repeated Dynamic Calls to VI in Packed Project Library Can Cause Error in VI Call
After over a million Dynamic Calls to a VI contained in a Packed Project Library, a error can be thrown that LabVIEW attempted a recursive call. Workaround: The error does not occur on regular project libraries. |
LabVIEW 2011 SP1 | N/A | 08/02/2013 |
| 405271 | Boolean Mechanical Actions Don't Work as Expected on Windows 8 Touch Screen
Switch Until Released and Latch Until Released don't behave as expected for touch and hold gesture. Boolean controls will not toggle on touch and hold gesture, until finger is dragged outside the bounds of the control. Other Boolean mechanical actions behave as expected. Workaround: N/A |
LabVIEW 2012 | N/A | 08/02/2013 |
| 406311 | VI.Control Value.Set will Crash LabVIEW When Value Non-Variant Data is Used for Value Parameter
The crash will happen when VI.Control Value.Set is invoked upon a VI reference that has been opened by Open VI Reference. Workaround: Cast data to variant before wiring to Value parameter. |
LabVIEW 2012 | N/A | 08/02/2013 |
| 407614 | Control.Delete Method Crashes LabVIEW When Used on Grouped Pictures and Free Labels
LabVIEW will crash when VI scripting method Control.Delete is invoked on pictures or Free Labels that are grouped on the front panel. Workaround: N/A |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 407633 | Set Cell Value Method Returns Error 1604
Set Cell Value method for tables returns error 1604 if method executes at the same time that a user changes the value of a Picture Ring Control. Workaround: Architect code so table is not updating continuously to reduce risk that user changes Picture Ring value at the same time that Set Cell Value is executing. |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 408391 | Non-printable Characters in the Description of Will Corrupt LabVIEW Classes and Libraries
Non-printable characters can be inserted into the description of LabVIEW Classes and Libraries with the Description Property Node. This will corrupt the .lvclass or .lvlib file. Workaround: The .lvclass or .lvlib file can be opened in a text editor, and the description can be manually deleted to recover the files. |
LabVIEW 2012 | N/A | 08/02/2013 |
| 408790 | Palette Editor Cannot Add LabVIEW Classes
LabVIEW Classes are an available option to be added to palettes, but adding them will not take effect. Workaround: If your goal is to allow dropping of the class control or constant, you can create a custom control (not a typedef) that has the class on it's panel and add the custom control to the palettes. If your goal is to add the LabVIEW Class as a linked library, you can do so programmatically with Write Palette.vi. |
LabVIEW 2009 | N/A | 08/02/2013 |
| 408891 | Getting an Entire Column of Data from a 2D Array in the MATLAB® Script Node Returns Only 1 Element
In the context of the MATLAB® Script Node, attempting to return an entire column of data from an array using a command like "column1 =, array2D(:,1)," returns only a single element. This same operation on a row "row1 =, array2D(1,:)," , returns the entire row successfully. Workaround: Transpose the array, and get the data in it's context as a row. |
LabVIEW 2012 | N/A | 10/16/2013 |
| 410360 | LabVIEW Classes Become Corrupt When Multiple Files With Same File Name are Added to the Class
When a LabVIEW Class is saved with multiple files sub-files that have the same file name, the .lvclass file will become corrupt. Workaround: N/A |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 410479 | Grouping ActiveX containers removes inserted ActiveX objects
When populated ActiveX containers are grouped with other front panel objects, the inserted ActiveX object will be removed. Workaround: Re-insert the ActiveX object after it has been grouped with another object, or group a blank ActiveX container, then insert the object. |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 410904 | Print.VI to Printer Method Always Prints Header in LabVIEW Built Applications
The Page Headers? parameter for Print.VI to Printer is always true when running as a LabVIEW Built Application. The parameter is used properly when the method is ran in the LabVIEW development environment. Workaround: 1. Select Operate»Print at Completion to print the front panel of a VI when it finishes running.2. Select File»VI Properties.3. Select Print Options from the Category pull-down menu.4. Place a checkmark in the Automatically Print Panel Every Time VI Completes Execution checkbox.5. Uncheck Print header (name,date,page number) box6. Click the OK button. |
LabVIEW 2012 SP1 | N/A | 08/02/2013 |
| 412979 | Flatten to XML String does not properly escape single and double apostrophes in a string input (' and ")
These should be escaped to "apos" and "quot" but are not. Other special characters including &,,<,, and > are correctly escaped. Workaround: Parse the string manually for apostrophes to escape them |
LabVIEW 2012 SP1 | N/A | 10/17/2013 |
| 415924 | Double precision numeric constants set to "bar" units sometimes use Pa units
Double precision numeric controls and indicators using "bar" units work correctly, but block diagram constants use Pa instead of bar. Workaround: Create the constant from a control with "bar" units and then change the unit label from Pa to bar to get a constant that uses bar. |
LabVIEW 2012 SP1 | N/A | 10/14/2013 |
| 420582 | Typing Obtain in Quick Drop populates with an unexpected selection
Workaround: Disable 'relevancy-based search' in the Quick Drop configuration options |
LabVIEW 2013 | N/A | 07/31/2014 |
| 420965 | Adding a tooltip for a tab control after configuring the tab to show text and image can cause the tooltip to appear in the wrong position
If you configure a tab control for text-image content, and then add an image and change the tooltip, the tooltip will appear far away from the tab control. Workaround: View the tooltip after adding the image and before changing the default tooltip |
LabVIEW 2012 SP1 | N/A | 10/14/2013 |
| 422507 | Entering an integer into a numeric control that has a time display format does not update the control
Double clicking inside a time display numeric control and typing a new value does not update to the new value, and the control reverts to its original value. This happens for controls with a display format of either %t or the default Relative Time format. Workaround: If the display format is %t, enter values with a decimal point after the number (as a double)If the display format is the default Relative Time, single click on the hour or minute fields and update individually or enter the value in the format HH:MM with the colon to successfully update |
LabVIEW 2013 | N/A | 10/23/2013 |
| 424089 | The advanced analysis Kummer Function returns 'NaN' instead of correct values for certain combinations of input parameters.
Check the following forum for more information and a possible workaround Workaround: Check the following forum for more information and a possible workaround:http://forums.ni.com/t5/LabVIEW/Bug-in-the-Kummer-Function/m-p/2387522#U2387522 |
LabVIEW 2013 | LabVIEW 2015 | 05/09/2014 |
| 424382 | Path controls in LabVIEW for Mac OS X treat .app files as folders instead of files
Workaround: None |
LabVIEW 2013 | N/A | 10/16/2013 |
| 425313 | Selecting the option to hide grid lines when using Export Simplified Image with a waveform graph will not hide all grid lines when using multiple axis
When using the waveform graph right-click option to Export Simplified Image with the option to hide grid lines, some of the grid lines will still be visible if there are multiple axis Workaround: Disable the grid of the additional axis through the scale tab of the graph properties |
LabVIEW 2013 | N/A | 03/11/2014 |
| 425562 | Scan from String requires a space between modifiers when using SI notation
Scan from String requires a space between the modifier and the unit. For example, %pV will throw an error with an input string of 10mV, but it works correctly with %p V and an input string of 10m V. Workaround: Add an additional space after the modifier |
LabVIEW 2012 | LabVIEW 2015 | 10/16/2013 |
| 426157 | VI invoke node Find CtrlWitkKeyFocus don't work with typdefs
Workaround: None |
LabVIEW 2013 | LabVIEW 2015 | 02/09/2016 |
| 428515 | On Scientific Linux 6.3 with updated Mesa Drivers, 3D Picture Controls display an inverted image
Workaround: Downgrade the Mesa drivers or manually invert the image.If your 3rd-Party Mesa driver version is between 7.11 and 9.2.1, you need to add the LabVIEW INI token "Invert3DPictImage=,True". Driver version 7.11 and earlier, and version 9.2.1 and later, do not need the INI token. |
LabVIEW 2013 | N/A | 10/23/2013 |
| 428914 | The Y-Axis of a Mixed Signal Graph will not correctly scale when the graph is set to "Scale Object with Pane" and the user decreases the size of the VI Front Panel.
Increasing the size of the pane will result in the graph growing and scaling its axes correctly, but decreasing the size of the pane will only shrink the graph without scaling the Y-Axis. The Y-Axis will now have a scroll bar due to not scaling. Workaround: Use the "Plot Area" Property Node to shrink the graph to appropriate size. |
LabVIEW 2013 | N/A | 03/31/2014 |
| 430758 | It is not possible to save a VI with the name of another VI in memory, even if they are in different libraries
LabVIEW does not check the library namespace when determining if a VI is being saved with a name that is already in use. If a VI is in memory, it is not possible to save another VI with the same name in the same project even if they are in different libraries. Workaround: Close the other VIs with the same name so they are not in memory. |
LabVIEW 2013 | N/A | 03/14/2014 |
| 432182 | Custom labels on a 3D bar chart do not display properly in a 2D view
Custom labels on a 3D bar chart will revert to a numeric value when viewed in a 2D Projection Workaround: N/A |
LabVIEW 2013 | N/A | 03/14/2014 |
| 432523 | Reordering elements of a cluster within the private data of a class can break VIs that reference the class
If you have a cluster within the private data of a class and you reorder the elements of the cluster, VIs that reference the class can become broken. Workaround: Close and reopen the LabVIEW project after reordering the cluster |
LabVIEW 2013 | N/A | 05/22/2017 |
| 433596 | The 3D Surface Plot does not draw correctly when the input data is an array of the same value
The plot is completely blank if the array contains only the same value. Changing one value correctly draws the 3D Surface Plot Workaround: Manually or programmatically toggle the Z-Axis range, or turn off Auto Scaling on Z-Axis, and the plot will appear |
LabVIEW 2013 | N/A | 03/31/2014 |
| 437390 | File Path control does not display "Browse" dialog if Start Path is an invalid network path.
LabVIEW may hang while waiting for Windows to locate an invalid network directory. The control's owning VI may hang while it searches for the directory, or it may appear that the "Browse" button does not have any affect and does not invoke a dialog. This can happen if the Start Path input in Browse Options... is an invalid path or if the Start Path in blank and the control's value is invalid. Workaround: Make sure the Start Path input is valid before selecting the Browse button. If the Start Path input is blank, change the File Path control's value to a known valid path before browsing. |
LabVIEW 2012 | N/A | 03/24/2014 |
| 438751 | Renaming a group in a Mixed Signal Graph crashes LabVIEW once there is a plot containing data
Workaround: Create a Strict Type Definition from a new Mixed Signal Graph. Change and update the Type Def to change the name of the group |
LabVIEW 2013 | LabVIEW 2015 | 12/01/2014 |
| 442745 | RF-RIO Instr Default Personality 5646R.lvproj's FPGA VI will hang on save.
Instrument driver\RFSA\5645R\Public\Apply Digital Correction.vi located in RF-RIO Instr Default Personality 5646R.lvproj will hang on save. This happens when removing the diagram disable structure. In addition, the VI cannot compile. Workaround: Currently, using the structure wrap included in the example code is recommended. If you only use one instance of the polymorphic VI, re-arrange the instances such that the instance you wish to use appears first in the list. |
LabVIEW 2013 | N/A | 07/31/2014 |
| 443165 | Modifying the dependencies of a Packed Project Library (PPL) may cause LabVIEW to crash
N/A Workaround: To avoid the crash, rebuild the PPL after modifying the dependencies. |
LabVIEW 2013 | LabVIEW 2015 | 01/30/2014 |
| 447789 | "RecipeBkUp::SanityCheck()" Crash in LabVIEW
Workaround: None |
LabVIEW 2013 | LabVIEW 2015 | 02/09/2016 |
| 449383 | Interaction between dragged project items and subdigram labels
Dragging project items over subdiagram labels on loops or other structures prevents the user from placing the item on the block diagram. Examples of project items affected by this include shared variables and I/O nodes. Workaround: Avoid moving your mouse over the subdiagram label when dragging items from the project. |
LabVIEW 2012 | N/A | 08/08/2016 |
| 449869 | "ICallPiccCallback" 0x89B93EF0 crash in LabVIEW
Workaround: Remove all "attached object" arrows |
LabVIEW 2013 | LabVIEW 2015 | 02/09/2016 |
| 451059 | "CProjectItemWrapper::GetPropertyBag(IlvProjectPropertyBag**)" crash in LabVIEW
Workaround: None |
LabVIEW 2012 SP1 | LabVIEW 2015 | 02/09/2016 |
| 453489 | Minimizing the lvlib group in VI Hierarchy messes up the entire VI hierarchy.
Workaround: None |
LabVIEW 2014 | LabVIEW 2015 | 02/09/2016 |
| 457854 | Aborting a VI can leave VIs targeted by a Call By Reference node reserved permanently
N/A Workaround: Close the project to unreserve the VI |
LabVIEW 2013 | N/A | 08/08/2016 |
| 458973 | Writing a negative number to single point float Network Shared Variables through the OPC I/O Server fails.
Workaround: Use Double precision shared variables instead. |
LabVIEW 2013 | N/A | 03/31/2014 |
| 460106 | In certain cases, there is a memory leak when a .NET object is used in a LabVIEW Interop Assembly
Workaround: N/A |
LabVIEW 2013 SP1 | LabVIEW 2014 SP1 | 11/20/2014 |
| 461969 | When using a class containing a DAQmx Physical Channel control, it will not properly load that information from an XML file.
The control can be changed and saved to the XML as expected and seen when opening the XML. However, when you try to load the channel from the XML it appears blank. Workaround: If you place the class cluster in an additional cluster the DAQmx Physical Channel control saves and loads as expected. |
LabVIEW 2013 | N/A | 05/07/2014 |
| 462021 | In LabVIEW for Mac, filtered menu tracking is not cancelled until the event's case finishes executing
If you are the filter event "Menu Activation?" and you discard the event, the menu activation will not be cancelled until that case in the event structure finishes executing. This may cause the menu to appear momentarily before it disappears. Workaround: Programmatically hide or disable the menu instead of filtering an event for it. |
LabVIEW 2014 | N/A | 07/31/2014 |
| 462029 | LabVIEW crashes when typecasting a RIO handle to a VISA handle
Workaround: Cast RIO handle to string and pass it into a VISA resource VI, or use the flatten to string/unflatten to string VIs. |
LabVIEW 2013 SP1 | N/A | 07/31/2014 |
| 464572 | Reading a datalog file truncated from more than 128 records returns error 4 "End of file encountered"
Workaround: N/A |
LabVIEW 2011 SP1 | N/A | 05/09/2014 |
| 465422 | In certain cases, LabVIEW Crashes When Deleting a Subdiagram Label From a Merged Flat Sequence Structure
Workaround: Do not merge frames with Subdiagram Labels or hide the labels before merging. |
LabVIEW 2012 SP1 | LabVIEW 2015 | 05/07/2014 |
| 467735 | "Format into File" produces Error 1 when appending to a file that has a size of 4 GB
See thisNI Communitypage for more information. Workaround: Use "Format Into String" and "Write to Binary File". |
LabVIEW 2013 | N/A | 12/01/2014 |
| 468062 | Path to URL.vi does not handle network path
Workaround: Use the attached Path to URL.vi and \vi.lib\Platform\browser.llb\Open URL in Default Browser core.vi in your code. |
LabVIEW 2013 SP1 | LabVIEW 2015 | 12/01/2014 |
| 468139 | .NET Callback Event VI keeps the Callback VI reserved even after calling a Close Reference VI is called
For example, when running the "Passing data to a .NET Event Callback.vi" example, after stopping the main example VI, the "Callback - EventHappened.vi" is still reserved. Workaround: I've come up with a work around for this problem. GC.Collect() can be called manually from the invoke node in a separate VI(Or the user could call it after un-registering the callback). This would un-reserve the callback VI. Steps : 1. Drop an invoke node in an empty VI 2. Right click on the node and in the menu under "Select Class" -> ".NET" choose Browse. 3. In the Class browser dialog navigate to mscorlib(4.0.0.0) assembly in the drop down 4. Once selected in the list below expand the system namespace and choose GC class. 5. Once this is done you can choose the Collect() static method. 6. You can unreserve the callback VI by running this VI. |
LabVIEW 2013 SP1 | N/A | 05/07/2014 |
| 468921 | Auto-populating folders may not update their contents correctly
Saving a web page file (.htm) from certain programs can result in the auto-populating folder displaying the web page file as a ".ht_" file, which can cause errors in build specifications and other parts of the program that rely on the files. Workaround: Close and reopen the project to correctly update the files in the auto-populating folder. Or, press f5 to refresh the project window. |
LabVIEW 2013 SP1 | LabVIEW 2015 | 04/30/2014 |
| 469070 | In some cases, Fract/Exp String To Number VI does not convert the string correctly
Examples:"1E-9999" should return 0 but returns Inf"1E-12000" sould return 0 but returns 1E-1200"1E9999" should return Inf but return 0"1E12000" should return Inf but returns 1E1200 Workaround: N/A |
LabVIEW 2013 | LabVIEW 2015 | 07/31/2014 |
| 469268 | Formula Node and MathScript Node variable labels can shift to become misalligned
After opening and closing its VI, the label will no longer look centered inside its owning box Workaround: This should not affect functionality. Recreate the variable on the node's border to recenter the label |
LabVIEW 2013 SP1 | N/A | 05/02/2014 |
| 470218 | LabVIEW (64-bit) for Mac, does not show the login prompt for Revision History when starting LabVIEW
In Tools>>Options, you can set the "User Name to Record in VI Revision History" to "LabVIEW registration name" which adds the token "history.whereToGetName=,LabVIEW" to the LabVIEW.ini or LabVIEW.app file, for Windows and Mac OS X respectively. Changing the token to "history.whereToGetName=,prompt" should invoke a login dialog each time LabVIEW starts, but the dialog does not appear in LabVIEW (64-bit) for Mac. Workaround: After LabVIEW finishes launching, select Tools>>User Name to view the login dialog. |
LabVIEW 2014 | N/A | 07/28/2014 |
| 470533 | When creating a property accessor method of an EndevoGOOP400 type for a Simple DVR Template Class in the LabVIEW GOOP suite, LabVIEW generates Error 7
Workaround: Manually create the property accessor. |
LabVIEW 2013 SP1 | N/A | 07/30/2014 |
| 471675 | Inverse FFT Function is very slow if inputs have NaN values
Workaround: Programmatically detect if the array has NaN in it by using the "NaN Path Refnum?" VI and a OR Array Elements and case structure the inverse FFT function. |
LabVIEW 2013 SP1 | N/A | 05/15/2014 |
| 471706 | Cannot paste into destination name of installer properties in LabVIEW
Workaround: Manually type the destination |
LabVIEW 2013 | LabVIEW 2015 | 02/09/2016 |
| 473149 | In certain cases, flattening or unflattening a large cluster and class hierarchy may result in Error 1403
Workaround: N/A |
LabVIEW 2014 | N/A | 07/31/2014 |
| 473389 | Unable to delete Waveform Chart or Graph plot entries
Workaround: Change the number of plots visible. More information at: http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/pl_number/ |
LabVIEW 2013 SP1 | N/A | 07/31/2014 |
| 474764 | A VI can hang at Occurrences if Allow Debugging is Disabled
N/A Workaround: Enable debugging |
LabVIEW 2012 SP1 | LabVIEW 2015 | 04/24/2015 |
| 476362 | With an Actor Framework project in LabVIEW 2013 SP1 and the LabVIEW GOOP Development Suite, LabVIEW may crash when exiting if the Message Classes are Updated.
Workaround: Right click and run LabVIEW as Administrator. |
LabVIEW 2013 SP1 | N/A | 07/31/2014 |
| 476710 | Opening a VI Server Reference to two or more identically named VIs, contained in separate LabVIEW libraries in a running executable, can result in Error 1031
From a LabVIEW development environment, opening a VI Server Reference to two or more identically-named VIs, contained in separate LabVIEW libraries in a running executable, results in one successful VI reference and Error 1031 from all other Open VI Reference functions. Workaround: Rename the referenced VIs so there are no name duplicates across LabVIEW libraries |
LabVIEW 2013 | LabVIEW 2014 SP1 | 06/24/2014 |
| 476714 | The INI file created for a LabVIEW built executable contains a truncated list of VIs in the "server.vi.access=," line when enabling TCP/IP with multiple Exported VIs
Workaround: Manually list the missing VIs in the INI file |
LabVIEW 2013 | LabVIEW 2015 | 07/30/2014 |
| 477112 | If you cancel the file dialog in Write to Measurement File Express VI, it will never be displayed again.
Workaround: None |
LabVIEW 2013 SP1 | LabVIEW 2015 | 02/09/2016 |
| 477265 | Large input for "byte count" causes decrease in performance for VISA Read on Linux RT
Workaround: N/A |
LabVIEW 2014 | N/A | 07/31/2014 |
| 477278 | The [VersionNumber] Tag throws error 7 when used in an RT-EXE build specification.
Workaround: None |
LabVIEW 2013 | LabVIEW 2015 | 02/09/2016 |
| 477280 | When using [VersionNumber], Application Builder post-build VIs do not get passed the proper path
For example the build spec may have a app builder destination directory of:\Builds\[VersionNumber]The files are built into a directory like this:\Builds\1.0.0.3\And the path that is passed to the post build VI is:\Builds\[VersionNumber] Workaround: Parse the build path from one of the files generated from the build |
LabVIEW 2013 | LabVIEW 2015 | 04/24/2015 |
| 477352 | In the TDMS File Viewer VI, the menu becomes partially hidden after making the plot legend visible
Workaround: Restart the VI containing the TDMS File Viewer and the menu should be fully visible |
LabVIEW 2013 SP1 | LabVIEW 2015 | 07/31/2014 |
| 477864 | When a number of controls are grouped on a tab control page, switching to that page takes a long time, proportional to the number of controls grouped
Workaround: Ungroup controls on tab pages |
LabVIEW 2013 | LabVIEW 2015 | 07/30/2014 |
| 477954 | VI Analyzer throws error 1 when analyzing project with a Networked Computer under the Target Folder.
Workaround: Don't have this folder type in your project |
LabVIEW 2013 | LabVIEW 2015 | 02/09/2016 |
| 47819 | 2GB file size limit of datalog files
The maximum size of datalog files is 2 GB. Workaround: N/A |
LabVIEW 8.0 | N/A | 09/01/2007 |
| 478232 | In certain cases, LabVIEW may incorrectly crisscross wires during loop creation
When adding a loop around existing code, LabVIEW may reconnect wires to the incorrect tunnels on the border of the loop Workaround: Manually reconnect the appropriate wires and tunnels |
LabVIEW 2014 | N/A | 06/19/2014 |
| 479161 | Error 7 When Building Installer for EXE with Custom Destinations
Workaround: Don't use custom internal destinations for dynamically called VIs |
LabVIEW 2014 | LabVIEW 2015 | 02/09/2016 |
| 48016 | Unsigned int32 loses value in formula node when you write to the most significant bit
If you wire a hex value greater than x7FFFFFFF as an unsigned, 32-bit integer to a Formula Node, LabVIEW coerces the value to 0. If you use a negative number for U32 input/output variable, LabVIEW will coerce the value to 0. Workaround: 1. Use the Mathscript node or LabVIEW code for the operation that involves an unsigned, 32-bit integer.2. Use signed 32-bit integers instead of unsigned 32-bit integers in the formula node. |
LabVIEW 8.0 | N/A | 09/01/2007 |
| 480165 | Concurrent calls of reentrant Data Value Reference accessors crashes LabVIEW on Windows and Real-Time
Workaround: setting the methods to be non-reentrant or statically-dispatched prevents the crash |
LabVIEW 2013 SP1 | LabVIEW 2015 | 02/09/2016 |
| 480386 | ActiveX call to open PDF (Adobe Reader 11.0.07) results in LabVIEW crashing
More information at https://forums.adobe.com/message/6396203#6396203 Workaround: Downgrade to an earlier versions of Adobe Reader (11.0.6 and earlier) |
LabVIEW 2013 | N/A | 07/31/2014 |
| 480480 | Invoke Node shows the English shortname at the first drop in German LabVIEW
N/A Workaround: N/A |
LabVIEW 2014 | LabVIEW 2015 | 04/24/2015 |
| 480921 | Unable to delete and re-add a desitnation folder successfully in build specification of a LabVIEW Installer
Workaround: Delete the build specification from the project explorer and create a new one |
LabVIEW 2013 SP1 | LabVIEW 2015 | 04/24/2015 |
| 481414 | In the LabVIEW GOOP design suite, you are unable rename a method of a GOOP class under an RT target from the project
Workaround: Double click the method, open the VI, and navigate through top menu bar Tools >> GOOP >> Create VI Icon to rename the method |
LabVIEW 2013 SP1 | N/A | 07/31/2014 |
| 485336 | Deleting a second y-axis on a waveform graph with a cursor crashes LabVIEW
When using a waveform graph indicator, it is possible to crash LabVIEW with an access violation error 0xC0000005 at EIP=,0x00FE9E79 by creating two y-axis scales, creating a graph cursor, changing the cursor's associated y-axis, and then deleting the original y-axis scale. Workaround: Remove the scale from the waveform graph, remove the unwanted y-axis scale, then recreate the cursor. |
LabVIEW 2013 SP1 | N/A | 06/17/2015 |
| 487258 | A LabVIEW 2014 Web Service does not run when it is built into an executable and then installed via an NI Installer
A LabVIEW component is missing from the 2014 installer which is necessary to run the LabVIEW Web Service. Workaround: This is fixed in the LabVIEW 2014 f1 Patch. SeeLabVIEW 2014 Patch Detailsfor more information. |
LabVIEW 2014 | LabVIEW 2014 SP1 | 11/13/2014 |
| 489848 | "Remove empty cases" option in case structure disappears when Subdiagram Label is visible.
Workaround: N/A |
LabVIEW 2014 | LabVIEW 2015 | 02/09/2016 |
| 491159 | Type Definition instance does not require manual update (new to LabVIEW 2014) if last element of enum was deleted
Workaround: Rename the element to trigger a manual update |
LabVIEW 2014 | LabVIEW 2014 SP1 | 11/13/2014 |
| 491225 | Installing the LabVIEW 2014 Run-Time Engine via an NI Installer can prevent the NI System Web Server from starting if older versions of LabVIEW are also present or installed.
Installing the LabVIEW 2014 RTE on a system with older components, such as LabVIEW 2013 Development System and LabVIEW 2014 Run-Time Engine, are the only systems affected. Systems with the full LabVIEW 2014 Development System are not affected. Workaround: Include "NI Web-Based Configuration and Monitoring 14.0" in your NI Installer.This issue has been fixed in the LabVIEW 2014 f2 Patch. |
LabVIEW 2014 | LabVIEW 2014 SP1 | 11/13/2014 |
| 491714 | Using Probes while Remote Debugging with General Error Handler VI present can cause LabVIEW 2014 to hang.
Workaround: Remove the General Error Handler VI |
LabVIEW 2014 | LabVIEW 2014 SP1 | 11/13/2014 |
| 492341 | LabVIEW TDMS Advanced Asynchronous Write does not return error when target disk is full.
Workaround: Use the TDMS Reserve File Size Function to allocate disk space before writing |
LabVIEW 2014 | N/A | 12/01/2014 |
| 492898 | Open VI Reference hangs on second call
Workaround: This issue has been fixed in the LabVIEW 2014 f2 Patch. |
LabVIEW 2014 | LabVIEW 2014 SP1 | 09/23/2014 |
| 493624 | Change of .NET assembly version requires manual relink of static class methods/properties
Workaround: N/A |
LabVIEW 2013 SP1 | N/A | 06/17/2015 |
| 493662 | dotNET Constructor Node cannot handle overloads with different enum parameter types
Workaround: Create a wrapper assembly to call from LabVIEW |
LabVIEW 2014 | N/A | 06/17/2015 |
| 493664 | Free Label arrow pointing to a wire inside a structure, such as For Loop or While Loop, will crash LabVIEW if user selects the structure and attempts to Clean Up Diagram before VI is saved
Workaround: Save the VI before selecting Clean Up Diagram |
LabVIEW 2014 | N/A | 12/01/2014 |
| 494409 | WebDAV Open Session VI does not output an error if unable to open a session
Workaround: Use the Path Info VI after the Open Session VI. It should timeout with Error 56 if the session is invalid. |
LabVIEW 2014 | N/A | 12/01/2014 |
| 497131 | The WebDAV Put.vi when executed on a cRIO target can lead to a memory leak
Workaround: N/A |
LabVIEW 2014 | LabVIEW 2015 | 11/20/2014 |
| 497755 | Cannot reset the values of Build Specification Version in Set Build Specification Version VI to zero
Workaround: The version can be reset in the build specification directly in the LabVIEW Project |
LabVIEW 2014 | LabVIEW 2015 | 12/01/2014 |
| 502081 | Ctrl+,shift+,E (find in project) doesn't work for clone VIs.
Workaround: N/A |
LabVIEW 2014 | LabVIEW 2015 | 02/09/2016 |
| 504066 | Save for previous fails if file path is too long
Save for previous copies the folder being saved to a temp location, if the resulting file paths exceed the limit defined by the OS, the function fails. Workaround: Copy the folder being saved to the root directory to reduce the file path length and Save for Previous from that location. |
LabVIEW 8.5 | N/A | Feb 18, 2020 |
| 50420 | Update the Pulse Transition Measurement Express VI
The terminology and measurement definitions for the Transition Measurements VI comply with IEEE Standard 181-2003, IEEE Standard on Transitions, Pulses, and Related Waveforms. However, the Timing and Transition Measurements Express VI does not comply with this IEEE Standard. Workaround: The Slew rate refers to the transition slope. The Preshoot refers to the pre-transition undershoot (rising pulse) or the pre-transition overshoot (falling pulse). The Overshoot refers to the post-transition undershoot (rising pulse) or the post-transition overshoot (falling pulse). |
LabVIEW 8.5 | N/A | 09/01/2007 |
| 504716 | Advanced Asynchronous Write function does not return an error when target disk is full or removed
N/A Workaround: Use the TDMS Reserve File Size Function to allocate disk space before writing |
LabVIEW 2014 | N/A | 08/08/2016 |
| 507856 | Replacing an Intensity Graph with z-axis autoscaling enabled with a Waveform Graph or XY Graph causes LabVIEW to crash
Workaround: Delete the Intensity Graph and add a Waveform Graph or XY Graph rather than using the replace option. |
LabVIEW 2014 | N/A | 06/17/2015 |
| 508651 | Custom conditional disable symbols not copied to EXE when debugging and enhanced DSC run-time support are enabled
Workaround: Disable either debugging or enhanced DSC run-time support. |
LabVIEW 2014 | N/A | 06/17/2015 |
| 509173 | Unhandled Exception can occur if absolute path for system DLL used in CLFN
If you use a specific path to a system DLL (C:\windows\system\user32.dll) and build your VI into an application it will create a copy of the DLL inside the application. This can cause an unhandled exception when running Workaround: LabVIEW searches in the system directory when looking for DLLs. If you are using a system DLL simply put the name in the in DLL Path box in the CLFN properties. In the example above you would simply put "user32.dll" |
LabVIEW 8.6 | N/A | Feb 17, 2020 |
| 509876 | Bundle by Name function can send wrong pointer into subVI with Call Library Function Node
If a main VI has the output of a Bundle by Name function connected to a subVI, a Call Library Function node within the subVI can receive the wrong pointer from the wired cluster. Workaround: Remove the Bundle by Name function or the subVI OR Replace the control input to the Bundle by Name function with a constant |
LabVIEW 2013 SP1 | LabVIEW 2019 SP1 | 08/08/2016 |
| 510218 | Create Mask.vi does not work in conjunction with the Get Image Subset.vi in LabVIEW
Workaround: Swap the Dimension Size inputs of the Reshape Array in the Case Structure at the bottom of Get Image Subset.vi. |
LabVIEW 2012 SP1 | N/A | 06/17/2015 |
| 510881 | LabVIEW Crash when saving Library containing Shared Variables with Class Object in Typedef.
Workaround: Don't add class objects to typedefs used for Shared Variables |
LabVIEW 2013 SP1 | LabVIEW 2015 | 02/09/2016 |
| 511646 | In rare cases, Mixed Signal Graph and Digital Waveform Graph cause a memory leak
Workaround: N/A |
LabVIEW 2014 | N/A | 11/20/2014 |
| 511691 | In specific cases, creating source distribution with myRIO can cause LV 2014 to crash
Workaround: If none of the additional exclusions are applied, then the source distribution should build successfully. This would only be viable for systems with dependencies in vi.lib, user.lib, and instr.lib directories already present on the target system. |
LabVIEW 2014 | N/A | 06/17/2015 |
| 51179 | Error 6 occurred at Create Folder in Create Directory Recursive.vi when building an application (EXE), shared library (DLL), source distribution or web service
When building a Build Specification, the build process fails with Error 6 at Create Folder in Create Directory Recursive.vi. This usually happens if the path one of the files generated by the build (temporarily during the build process or as part of the output) is too long. The operating system requires paths for files to be less than 255 characters. Workaround: 1. Use a shorter path for your build destination (i.e. c:\build\) and if necessary copy the output to the final location you need.2. A. For application (EXE) and shared library (DLL) build specifications, place a checkmark in the Use LabVIEW 8.x file layout checkbox on the Advanced page of the Properties dialog box.2. B. For source distribution or web service build specifications, uncheck the Preserve disk hierarchy checkbox on the problem Destination on the Destinations page of the Properties dialog box. |
LabVIEW 8.2.1 | N/A | 10/06/2008 |
| 51185 | Cannot save VI as the same name as missing library member VI
If a library contains a VI and the VI is missing, you should be able to save a VI as the same name as the missing VI in order to rebuild the missing VI. Currently, LabVIEW does not allow this. Workaround: Delete the item from the library, save the new VI as the same name as the missing VI and then move the VI into the library. |
LabVIEW 8.5 | N/A | 09/01/2007 |
| 511987 | In certain cases, VI Merge crashes with Custom Control files
Workaround: Select Options...Uncheck "Auto-resolve", "Block Diagram cosmetic changes", "Make space for block diagram changes", and "Link block diagram to front panel changes" |
LabVIEW 2013 | N/A | 06/17/2015 |
| 512464 | After making a change in Format Into String, the containing VI does not recompile automatically.
Since the VI does not recompile automatically, it may appear incorrectly broken or able to run when the opposite is true. Workaround: Attempt run the VI to see the updated changes or used CTRL +, RUN to force a recompile on the containing VI. |
LabVIEW 2014 | LabVIEW 2015 | 04/24/2015 |
| 51311 | LabVIEW does not maintain child-only item setting when dragging an item within a tree
If you have a tree item with the child-only setting, and then drag it within the tree, LabVIEW loses the child-only setting. Workaround: Use tree events to (1) get the child-only flag setting when the user begins a drag, and (2) reset the child-only flag after completing a drop. |
LabVIEW 8.2.1 | N/A | 09/01/2007 |
| 513188 | Improved Bookmark Manager performance by adding additional caching.
Workaround: N/A |
LabVIEW 2013 | LabVIEW 2015 | 02/09/2016 |
| 513457 | "Change to Array" menu option should not appear on tab controls or XControls.
Workaround: N/A |
LabVIEW 2012 | LabVIEW 2015 | 02/09/2016 |
| 514789 | Autotuning PID Online.VI Example Reads Proportional Gain 'NaN' with the Relay Technique.
When running the Autotuning PID Online.vi example, with the Relay Technique the "Tuned PID gains" output of proportional gain (Kc) shows "NaN" when the program believes tuning is completed by flashing "tuning completed?". Workaround: Tune the individual terms first. Start by first tuning for P until the response is stable. Then continue to tune by switching to PI. Lastly, repeat the process for PID. |
LabVIEW 2014 | N/A | 02/04/2015 |
| 515054 | Icon transparency of VIs is not maintained when building a Source Distribution
Workaround: Unknown (use some other distribution method?)Opening and closing the Icon Editor for the effected VIs fixes transparency issues |
LabVIEW 2014 | LabVIEW 2015 SP1 | 04/24/2015 |
| 515300 | NamedBundler function in LV Scripting does not work properly when the reference is opened from a New VI function
Workaround: Use the Open VI Reference and Save A Copy functions, rather than New VI function, to create a new instance of a vi from a template. |
LabVIEW 2014 | N/A | 06/17/2015 |
| 515779 | Invoke node Append String returns error 1043 while display style set to backslash "\" codes
Workaround: Toggle to a different display style before using the Append String method |
LabVIEW 2013 | LabVIEW 2015 | 03/11/2015 |
| 516144 | A VI used in a LabVIEW Remote Front Panels may hang when it calls the "Strings[]"Property Node
Workaround: If before opening the VI's Front Panel, use the lock.RP property node and unlock it after the Front Panel has been opened. |
LabVIEW 2014 | N/A | 06/17/2015 |
| 516217 | The WebDAV Put.vi when executed on a cRIO target can lead to a memory leak
Workaround: N/A |
LabVIEW 2013 | LabVIEW 2015 | 11/20/2014 |
| 516227 | UI Thread LabVIEW code cannot execute while a Time Stamp Control's 'Set Time and Date' window is visible.
Workaround: N/A |
LabVIEW 2014 | LabVIEW 2015 | 02/09/2016 |
| 517128 | Error 1357 when building using two VIs with the same name and only capitalization differences.
Workaround: Make sure your VIs have exactly the same name (so that LabVIEW catches that and gives them their unique directories) or make sure the VIs' names differ in more than capitalization. |
LabVIEW 2013 SP1 | LabVIEW 2015 | 07/20/2015 |
| 519216 | LabVIEW crash when closing subVI Icon Editor that was opened from VI Hierarchy.
Workaround: Open the subVI icon editor from the subVI's front panel |
LabVIEW 2014 | LabVIEW 2015 | 02/09/2016 |
| 52027 | Cannot use the 'New>>VI for Override...' dialog to create override of password-protected VI unless you have the password
You use the 'New>>VI for Override...' dialog to override an ancestor VI in a LabVIEW class if the VI you want to override is password-protected. Workaround: Make a public VI which wraps the functionality of the private VI, and instruct others to override the public VI. |
LabVIEW 8.5 | N/A | 09/01/2007 |
| 521856 | Rare LabVIEW crash when using "Panel Close?" filtering event and "Quit LabVIEW" function
N/A Workaround: Either do not use the "Panel Close?" event, do not open the front panel of the VI being closed, or turn off scrollbar visibility using a property node. |
LabVIEW 2014 SP1 | N/A | 08/08/2016 |
| 522606 | Error Ring does not adhere to dataflow in an executable or in a VI with debugging disabled
See this forum for more details: http://forums.ni.com/t5/LabVIEW/Error-ring-excluded-in-executable/td-p/3100932 Workaround: Use an error constant |
LabVIEW 2013 | N/A | 06/17/2015 |
| 52263 | Some operations on integer waveforms lose dt value
Some functions, such as Absolute Value and Logarithm Base 10 operate as you expect with DBL Waveforms, but when you apply the same functions to an I16 waveform, for example, the Absolute Value function works as you expect while the Logarithm Base 10 function loses the sampling interval dt value. LabVIEW resets the sampling interval dt value to 1.00. If the input waveform to the log function has a time stamp for t0, that value is also lost. Workaround: Extract the Y-array of the waveform and perform the needed operations on Y before re-building the waveform. |
LabVIEW 8.0.1 | LabVIEW 2015 | 09/01/2007 |
| 525685 | Error -2628 is returned when parsing an XML file with a Document Type Definition file
Workaround: N/A |
LabVIEW 2014 | N/A | 06/17/2015 |
| 526044 | VISA Resource and DAQmx resource controls in VIs called using COM interface sometimes incorrectly retain their value from a previous VI call rather than using the value provided as input.
Workaround: Configure your VI to dynamically unload the VI, set the "resvForCall" input to be false in the GetVIReference method, or typecast a string of the desired name to the desired IO Resource type before sending it to the call method. |
LabVIEW 2014 | LabVIEW 2015 | 05/06/2015 |
| 528963 | File Dialog Express VI crashes when passed a null hex string as the pattern input
The File Dialog Express VI crashes LabVIEW when a null string is passed as the pattern (all files) input. The crash report states that an "Exception: Noncontinuable exception (0xC0000025) at EIP 0x000000" occurs. Workaround: Avoid passing the hexadecimal code for a null string to this input terminal. Programmatically detect these error situations and handle them appropriately. |
LabVIEW 2013 SP1 | N/A | 08/08/2016 |
| 529278 | MATLAB Script Node can output different data in LabVIEW 32-bit vs. 64-bit
N/A Workaround: Use LabVIEW 32-bit for MATLAB Script Nodes |
LabVIEW 2014 SP1 | N/A | 08/08/2016 |
| 529943 | Incorrect behavior when creating a .NET Interop Assembly with typedefs
When you have multiple different typedefs with identical definitions (i.e, multiple numeric typedefs), only one of them is exported to a .NET typedef. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2016 | N/A | Feb 14, 2020 |
| 530156 | Setting binding properties of a control within a preallocated clone subVI or XControl sets the property for all instances of the subVI or XControl
If the BindingPath property is set on a control within a preallocated clone subVI or XControl, all instances of the controls in the subVI or XControl update their BindingPath rather than the one where the property was set Workaround: Create a unique SubVI or XControl for each instance |
LabVIEW 2016 | N/A | Feb 17, 2020 |
| 530520 | Error -2548 is returned when TDMS Create Scaling information is applied on all channels
Workaround: Call Set Channel Information after calling TDMS Create Scaling Information.vi. |
LabVIEW 2014 | N/A | 06/17/2015 |
| 530595 | Not a Refnum Primitive returns incorrect value when evaluating a specific type of "Invalid Refnum"
Workaround: Use a property node, which should give you an error when attempting to use the reference, or implement your solution without the primitive by following this implementation: https://lavag.org/topic/15546-are-you-misusing-the-not-a-refnum-function-and-putting-your-app-at-risk/ |
LabVIEW 2012 SP1 | N/A | 06/17/2015 |
| 534471 | When building a packed project library containing classes, changes in class inheritance do not propagate to calling VIs
Workaround: This is fixed in the LabVIEW 2015 f1 Patch |
LabVIEW 2015 | LabVIEW 2015 SP1 | 11/24/2015 |
| 534812 | "Create from Data Type" Method Crashes LabVIEW if the data type is a Type Definition.
N/A Workaround: Before using a variant data type as an input, use "DisconnectFromTypedef.vi" from the VI.lib folder. |
LabVIEW 2014 SP1 | N/A | 08/08/2016 |
| 536763 | Popup Menu can appear only limited number of times before LabVIEW crashes.
The number of of times the popup menu can be accessed before the crash depends on the number of items within a menu and how many times this menu is populated. Workaround: N/A |
LabVIEW 2010 SP1 | N/A | 08/08/2016 |
| 537078 | Case Structure auto-complete functions incorrectly when used with Enum Controls in LabVIEW 2015
If the user triple-clicks on the case to change the Selector Label and types more than 5 letters, the subsequent letters are appended to the label immediately following the final letter of the auto-completed value. For example, "Boolean" becomes "Booleanna". Workaround: Use quotation marks: Type - "Boolean" (including the quotes), for example. |
LabVIEW 2015 | LabVIEW 2015 SP1 | 11/24/2015 |
| 537859 | LabVIEW 64-bit crashes when selecting a result from the Search text box on Windows 10
Workaround: Use LabVIEW 32-bit or search the LabVIEW Help, LabVIEW Palettes, etc. separately |
LabVIEW 2015 | LabVIEW 2015 SP1 | 11/24/2015 |
| 538332 | Make Space/Remove Space does not work when Bookmark Manager is open and there is a bookmark in the VI.
N/A Workaround: This issue has been fixed in the LabVIEW 2015 f2 Patch |
LabVIEW 2015 | LabVIEW 2015 SP1 | 11/24/2015 |
| 542232 | LabVIEW executables with ActiveX Server enabled do not have read-only properties
A LabVIEW 2015 executable that has the ActiveX server option enabled will be missing several ActiveX properties, such as "ApplicationDirectory" and "AppName". Workaround: This issue has been fixed in the LabVIEW 2015 f2 Patch. |
LabVIEW 2015 | LabVIEW 2015 SP1 | 11/24/2015 |
| 542436 | Block Diagram Cleanup on the Receive Message.VI in Actor Framework can cause an access violation crash within LabVIEW.
Opening\vi.lib\ActorFramework\Actor\Receive Message.vi and using Clean Up Diagram can cause LabVIEW to crash with an access violation. Workaround: 1. Excluding the bottom comment when doing a block diagram cleanup on this vi will avoid a crash. |
LabVIEW 2015 | N/A | 08/08/2016 |
| 542858 | In rare cases, LabVIEW applications that contain a Web Service may crash on exit.
Workaround: No workarounds at this time. |
LabVIEW 2013 | LabVIEW 2015 SP1 | 11/24/2015 |
| 543507 | DAbort 0x2CADF6E3 caused by scrolling the mouse wheel within an array
N/A Workaround: This issue has been fixed in the LabVIEW 2015 f2 Patch |
LabVIEW 2015 | LabVIEW 2015 SP1 | 11/24/2015 |
| 544257 | Inplace issue can occur when using LabVIEW 32-bit on a 64-bit operating system.
Running a VI that calls a subVI containing a Call Library Function Node to the kernel32.dll IsWow64Process can cause the returned value of the dll to be incorrect. Workaround: Adding an "Always Copy" dot before the control that is wired to the Front Panel Terminal within the subVI fixes the issue. |
LabVIEW 2014 | N/A | 08/08/2016 |
| 544623 | LabVIEW 64-bit for Mac OS can improperly create special characters.
LabVIEW 64-bit for Mac OS improperly creates special characters such as the 'degree' symbol and 'micro' symbol that cannot be read correctly. Workaround: Avoid using special characters. |
LabVIEW 2015 | N/A | 08/08/2016 |
| 545175 | In some cases, using Sort 1D Array and Array Max &, Min or Less Than on a cluster would report incorrect data
Workaround: This issue has been fixed in the LabVIEW 2015 f2 Patch |
LabVIEW 2015 | LabVIEW 2015 SP1 | 11/24/2015 |
| 545835 | LabVIEW Runtime Engine encounters Worker Thread Limit when using web services on Linux RT-based cRIO
On a Linux RT-based cRIO, the LabVIEW Runtime Engine can get into a deadlocked state waiting for action from the Web Server. This can cause process hangs resulting in a Worker Thread Limit error reported to the user by the Web Server. Workaround: Use a mechanism other than web services. |
LabVIEW 2015 | N/A | 08/08/2016 |
| 552304 | SMTP Client VI Example incorrectly converts some characters when placed in subject line
Email sent using the SMTP Client VI shipping example converts "!", ":", and "~" to "?" in the subject line of emails. Workaround: N/A |
LabVIEW 2013 SP1 | N/A | 08/08/2016 |
| 552345 | In rare cases, updating an IMAQ indicator and a LabVIEW Listbox at a high rate in two different, but visible, VIs can cause LabVIEW to crash
Workaround: This has been fixed in the LabVIEW 2015 f3 Patch and LabVIEW 2014 SP1 f5 Patch. |
LabVIEW 2014 | LabVIEW 2015 SP1 | 11/24/2015 |
| 558774 | Constructor node for FolderDialogBox from Windows.System.Forms (4.0.0) causes hang during execution
In recent versions of LabVIEW, placing a constructor for a FolderDialogBox object from Windows.System.Forms (4.0.0) will work successfully, but the containing VI will hang during execution. Workaround: Do not use FolderDialogBox objects. |
LabVIEW 2012 SP1 | N/A | 08/08/2016 |
| 558890 | LabVIEW 2015 leaks memory when copying an empty array of strings into a non-empty array of strings
Workaround: Change the empty array of strings to a 1-element array.This has been fixed in the LabVIEW 2015 f3 Patch. |
LabVIEW 2015 | LabVIEW 2015 SP1 | 12/08/2015 |
| 558891 | In some scenarios, LabVIEW Menu positions within a VI or project are offset in Windows 10
For multiple displays, Windows 10 allows you to set different "size for text and other items" (magnification) for each display. In the case you have different magnifications between displays, the drop down menus of a VI or project are offset to the right and down. This can be dramatic (even off the screen) when the two magnifications are very different. Workaround: Use a consistent magnification level for all displays. |
LabVIEW 2014 SP1 | N/A | 08/08/2016 |
| 559606 | In rare cases, leaving the Index input of Index Array function retrieves correct data but can cause other math functions to return incorrect results.
Workaround: Wire the index terminal of the Index Array function. |
LabVIEW 2013 | LabVIEW 2015 SP1 | 02/03/2016 |
| 561615 | In specific cases, building a LabVIEW executable with shared variables causes Error 1003 during the build.
The user will get an error saying, "VI containing Shared Variable node needs to be loaded in a project" on the Build Errors Dialog. Workaround: Save the VIs in the project that contain shared variables. |
LabVIEW 2015 SP1 | N/A | 03/03/2016 |
| 563825 | In certain rare cases, the Not A Number/Path/Refnum? function can cause LabVIEW 64-bit to crash, LabVIEW 32-bit is unaffected. Note: A recompile of the VI using the function is required to apply the fix.
Workaround: This has been fixed in the LabVIEW 2014 SP1 f5 Patch |
LabVIEW 2014 | LabVIEW 2015 SP1 | 02/03/2016 |
| 565884 | When creating .NET assemblies in LabVIEW, 1-dimension arrays of doubles or strings are represented as 2-dimension arrays of rank 1
When creating .NET assemblies in LabVIEW, 1-dimension arrays of doubles or strings are represented as 2-dimension arrays of rank 1. This can create an issue when the assembly is used in Visual Studio 2015 which will not accept 2-dimensional arrays of rank 1. Workaround: Pass a 2D array in LabVIEW instead of a 1D array. |
LabVIEW 2013 SP1 | N/A | 08/08/2016 |
| 567353 | When an XNode output is wired to the Loop count of a Parallel For Loop the VI breaks.
Connecting the output of an XNode (such as Match Regular Expression) to the count terminal of a Parallelized For Loop will result in a broken VI. The error list will also be empty in this situation. Workaround: Put an "Always Copy" between the output of the XNode and the Parallel For Loop count terminal |
LabVIEW 2012 SP1 | N/A | 08/08/2016 |
| 570102 | Calling the "Web Server: Server Active" property causes a small memory leak.
Calling the "Web Server: Server Active" property on any supported platform (including RT) creates a small memory leak. Workaround: Restart the application to allow the OS to reclaim the memory, or do not call this property often. |
LabVIEW 2014 | N/A | 08/08/2016 |
| 570754 | Linear Fit produces NaN result if X input value is too large
Linear Fit produces NaN result if X input value is too large. Values above around 2.2x10^9 in LabVIEW 32 bit or 4.9x10^7 in LabVIEW 64 bit may exhibit this behavior. Workaround: Modify your data to smaller absolute values before using this function. |
LabVIEW 2015 | N/A | 06/10/2016 |
| 571353 | XNode can cause Dirty Dot when no parameters are modified
When abilities of XNodes are called, LabVIEW can erroneously report that changes have been made to the VI and prompt the user to save. Workaround: N/A |
LabVIEW 2015 | N/A | 08/08/2016 |
| 574329 | Error 4 thrown in executable but not in development environment
Sometimes after manipulating the format specifier on the Open/Create/Replace primitive and then saving and reopening the VI, the VI can throw Error 4: End of File encountered on the next run. This may also occur when the application is run as an executable. Workaround: N/A |
LabVIEW 2015 | N/A | 08/08/2016 |
| 574488 | Upgrading to Mac OS X 10.11 (El Capitan) prevents Source Control in LabVIEW from finding Perforce
Mac OS X El Capitan no longer allows third party applications to be installed in /usr/sbin or /usr/bin. This is the default directory where many third-party applications have been stored in the past including Perforce. OS X El Capitan actually strips out any files from this directory that were user installed. Therefore, if you have Peforce installed in /usr/sbin, are running OS X 10.10, and upgrade to OS X 10.11, it strips out the Perforce files. Workaround: Manually copy Peforce back to /usr/bin (need admin rights). |
LabVIEW 2015 SP1 | N/A | 03/01/2016 |
| 576990 | Assembly created by Web Service Importer from WSDL throws error 1172
In certain cases, it is possible for the Web Service Importer tool in LabVIEW to throw error 1172 when trying to import a WSDL schema. Workaround: Remove complex data types from the WSDL file. |
LabVIEW 2015 | N/A | 08/08/2016 |
| 578085 | Saving a very large VI in LabVIEW 2015 and later can take longer than in previous versions
When compared to save times in earlier versions of LabVIEW, saving a large VI in LabVIEW 2015 and later takes a longer amount of time to complete. Workaround: Try the steps listed in this KB to minimize save time: http://ae.natinst.com/public.nsf/web/searchinternal/e43b32c14030c3b686256c1e0044d9b6?OpenDocument |
LabVIEW 2015 | N/A | 08/08/2016 |
| 583670 | If LabVIEW 2016 is installed, installers built in any version of LabVIEW will not work on Windows 7 RTM and older
See the following KB for details: http://knowledge.ni.com/KnowledgeArticleDetails?id=,kA00Z0000019LkCSAU?OpenDocument Workaround: Do not install LabVIEW 2016 on a computer which builds installers for Windows 7 RTM, Windows Vista, Windows XP SP3, and older. |
LabVIEW 2015 SP1 | N/A | 08/08/2016 |
| 584455 | Certain Silver Controls appear differently on Front Panel versus Print Output
When using the File >> Print option to print a Front Panel containing a Silver Boolean Control or Silver Meter Indicator, the printed version might not match up with the real values or style. Workaround: Use other style controls |
LabVIEW 2016 | N/A | 08/08/2016 |
| 584837 | Mass compiling a project from project explorer in certain cases can cause LabVIEW to hang.
Mass compiling a project from project explorer with an unsaved VI can cause LabVIEW to hang. Workaround: N/A |
LabVIEW 2012 SP1 | N/A | 04/29/2016 |
| 585867 | LabVIEW 64-bit can crash while closing a VI containing certain ActiveX containers
Certain ActiveX containers such as Microsoft InkEdit Controls can cause complications when they are unloaded from memory in LabVIEW 64-bit, such as when the containing VI is closed. Workaround: N/A |
LabVIEW 2015 | N/A | 08/08/2016 |
| 590224 | In some cases, using an XControl in a PPL can cause LabVIEW to hang
If you build an XControl into a PPL and include the XControl on the front panel of a VI that is also built into the PPL, the VI can hang in some cases. Workaround: N/A |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 596788 | The struct ErrorCluster from InteropAssembly throws case sensitivity error in Visual Basic
The user gets the following error when using the struct ErrorCluster in Visual Basic: "'Status' is ambiguous because multiple kinds of members with this names exist in structure 'ErrorCluster'". The struct NationalInstruments.LabVIEW.Interop.ErrorCluster defined in the DLL NationalInstruments.LabVIEW.Interop.dll has the following variable definition: Public code As Integer Public source As String Public status As Boolean Public Sub New(statusIn As Boolean, errorCode As Integer, errorMessage As String) Public ReadOnly Property Code As Integer Public ReadOnly Property Source As String Public ReadOnly Property Status As Boolean The first three members have the same name of the last three aside from the capitalization of the first letter. Although MSIL is case-sensitive, VB is case-insensitive, which is therefore causing the error. Workaround: 1. Use the generic .NET Exception, which will have the same information as the ErrorCluster. 2. Build a wrapper in C#, then use that in VB.NET |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 599746 | When building a web service into an EXE and making an installer, some software dependencies are not automatically selected as additional installers
If you build a web service into an EXE that has method VIs with software dependencies, such as the use of a hardware driver, only VIs with dependencies that are included as Startup VIs for the web service will be automatically selected as additional installers. Any method VI that is not a Startup VI will not have its software dependencies automatically selected. Workaround: Build the web service into the installer rather than the EXE or manually include the required software dependencies |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 602529 | Open/Create/Replace File does not return an error when attempting to create a file name that is restricted by the OS
When attempting to create a file with the Open/Create/Replace File primitive, the file will not be created but LabVIEW will not return an error. Examples of file names that are restricted by the OS are COM8.txt, LPT4.txt, etc. Workaround: N/A |
LabVIEW 2010 SP1 | N/A | 05/22/2017 |
| 603204 | When using a cylindrical coordinate system on a 3D scatter plot, the color ramp legend does not reflect the displayed color gradient
After changing the coordinate system to cylindrical, the graph will correctly display the color gradient according to distance from the origin. However, the legend will display the color ramp based on the minimum and maximum values of the z axis. Workaround: N/A |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 606191 | Building a .NET Interop Assembly with an array of classes as an output fails
When an exported VI has an array of classes as an output, attempting to build the .NET Interop Assembly results in error 1172. Workaround: Extract the data from the classes then bundle and output the data as an array of clusters |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 607058 | Flattening an EXT representation numeric to JSON causes loss of precision
N/A Workaround: Use Format Into String followed by Flatten to JSON |
LabVIEW 2013 SP1 | N/A | 05/22/2017 |
| 607411 | When using a LabVIEW-built .NET Interop Assembly in an ASP .NET application, the first call to the assembly will return a NullReferenceException
N/A Workaround: The exception only occurs on the first call to the assembly, so using a try-catch block to handle the exception will allow subsequent calls to behave normally. |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 613423 | Registering for an event for multiple boolean controls can fail in specific configurations
When passing a mixture of strict and non-strict boolean references in a cluster to the event source terminal of the Register For Events node, the input wire will break if any strict references are not the first elements of the cluster. Workaround: Use a Switch mechanical action, group the references with Build Array, or place any strict references at the beginning of the cluster. |
LabVIEW 2016 | N/A | 05/22/2017 |
| 614154 | Renaming a shared variable with a special character in its name (ö/ü/ä/ß) fails when the project is reopened
If you attempt to rename a shared variable that has a special characters in its name, the name will revert to the original name when the project is reopened Workaround: Do not use special characters in shared variable names |
LabVIEW 2016 | N/A | 05/22/2017 |
| 616849 | LabVIEW files are saved without an extension after attempting to save with an invalid character
If you attempt to save a LabVIEW file with an invalid character (such as ?), the file is correctly not saved. However, if you remove the invalid character and save the file, it will be saved with no extension on disk. Workaround: After saving, add the correct extension to the file |
LabVIEW 2010 SP1 | N/A | 05/22/2017 |
| 617826 | LabVIEW will not generate a Key Down event if the mouse is held down on a cell inside a table control
If you hold the left mouse button down on a cell inside of a table control, LabVIEW will not generate a Key Down event on the first key press. Subsequent key presses will generate the event as normal Workaround: N/A |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 618568 | Reference leaks with the Audio DataPlugin
Calling the Write Data [Channel] Express VI with the Audio DataPlugin in a loop causes LabVIEW to leak references, causing memory growth over time Workaround: N/A |
LabVIEW 2016 | N/A | 05/22/2017 |
| 619819 | Icon transparency of VIs is not maintained when building a Packed Library
Workaround: This seems to be okay in LabVIEW 2014 but not 2015 or 2016 |
LabVIEW 2016 | LabVIEW 2018.0 | 01/23/2018 |
| 624802 | Setting binding properties of a control within a preallocated clone subVI or XControl sets the property for all instances of the subVI or XControl
If the BindingPath property is set on a control within a preallocated clone subVI or XControl, all instances of the controls in the subVI or XControl update their BindingPath rather than the one where the property was set Workaround: Create a unique SubVI or XControl for each instance |
LabVIEW 2016 | N/A | 05/22/2017 |
| 625718 | The Web Publishing Tool has incompatibility issues with Internet Explorer 11
When the Web Publishing Tool tries to create a pop-up dialog box or a window, the pop-up dialog box or window will be blocked, and Internet Explorer hosting the Web Publishing Tool may hang or crash. This issue was detected in Internet Explorer 11. Workaround: On Internet Explorer 11, select Internet options from the Tools menu, switch to the Security tab, remove the checkmark from Enable Protected Mode, and restart Internet Explorer. |
LabVIEW 2017 | N/A | 05/22/2017 |
| 627783 | Using TCP Open Connection with a Timeout of 0 can cause connection failures
When you specify a Timeout of 0 for TCP Open Connection, it will return error 56. However, in some cases, a connection can still be established. This will cause subsequent connection attempts to fail, even when they have a nonzero timeout. Workaround: Always use nonzero timeouts |
LabVIEW 2010 SP1 | N/A | 05/22/2017 |
| 629032 | Wiring a 2D array with an empty string to the property names input of the TDMS Set Properties function causes data for that channel to be unreadable
If a 2D array with an empty string is wired to the property names input of the TDMS Set Properties function, the TDMS Read function is unable to retrieve data from the channel with the empty name. The TDMS Read function will return error 1. Workaround: Do not include empty strings in the 2D array of property names |
LabVIEW 2016 | N/A | 05/22/2017 |
| 629258 | In some cases, reading from a corrupt TDMS file will delete the file from your machine
After opening a corrupt TDMS file and attempting to read from it, closing the reference to the TDMS file can delete the file from disk in some cases. Workaround: Open the TDMS file as read-only |
LabVIEW 2010 SP1 | LabVIEW 2018.0 | 05/22/2017 |
| 631422 | Regenerate Channel Instances stop responding
In some situations, channel wires can hang LabVIEW when trying to regenerate channel instances. The hang will not end until LabVIEW is forced to close. Workaround: Open smaller subVIs containing channel wires first allowing the channels to regenerate. Once all of these are complete, open the calling VI. The smaller instances already regenerated their channel instances. |
LabVIEW 2017 | N/A | 03/12/2018 |
| 631762 | Using Export data to Excel on a Waveform Chart that contains an empty waveform can cause LabVIEW to crash
N/A Workaround: Do not plot empty waveforms or add a data point that is out of range that can be manually removed from the Excel sheet |
LabVIEW 2016 | N/A | 05/22/2017 |
| 631802 | Exporting typedef array of numerics to Excel may crash LabVIEW
When using the right-click menu option to export a non-empty, typedef numeric array's data to Excel, LabVIEW will crash. Workaround: N/A |
LabVIEW 2010 SP1 | LabVIEW 2018.0 | 05/22/2017 |
| 633309 | Waveform graphs can resize at runtime
For very large floating point numbers in a waveform graph, the control can permanently resize itself in an attempt to fit the large numbers in the axis label Workaround: Use Automatic or Scientific as the format type for the Y Axis with large floating point numbers |
LabVIEW 2017 | N/A | 05/22/2017 |
| 633648 | LabVIEW crashes when replacing the Actor Framework library with a packed library
Building a packed library from the Actor Framework libraries and selecting "Replace with packed library..." in a project crashes LabVIEW. Workaround: N/A |
LabVIEW 2016 | N/A | 01/23/2018 |
| 634015 | Certain operations will not let the System Exec VI return on Windows 10
Certain commands, such as renaming a file, will cause the System Exec VI to indefinitely wait for a response on Windows 10. The IDE will continue to be responsive and the VI may be aborted. This will only occur with "Wait Until Completion" is set to True. Workaround: Set "Wait Until Completion" parameter to False |
LabVIEW 2016 | N/A | 05/22/2017 |
| 634261 | The Block Diagram.Get Image Scaled method displays subVIs as black rectangles if the image depth is less than 8.
Workaround: Use a depth greater than 8 |
LabVIEW 2017 | N/A | 01/23/2018 |
| 634287 | Incorrect behavior when creating a .NET Interop Assembly with typedefs
When you have multiple different typedefs with identical definitions (i.e, multiple numeric typedefs), only one of them is exported to a .NET typedef. Workaround: N/A |
LabVIEW 2016 | N/A | 05/22/2017 |
| 634531 | Template methods in a C+,+, DLL do not appear in the Function Name drop down list of the Call Library Function Node.
Some C+,+, DLLs include methods which are created from a template during compilation. These template methods will not appear in the list of function names when using the Call Library Function Node. Workaround: 1. Create wrapper functions that call the template methods, then call the wrapper functions using the Call Library Function Node. 2. Manually specify the function prototype in the function name field of the Call Library Function Node. |
LabVIEW 2015 SP1 | N/A | 04/18/2017 |
| 635510 | Adding a diagram disable structure to a VI can cause the reported code coverage to be 100%
Workaround: N/A |
LabVIEW 2015 SP1 | N/A | 01/23/2018 |
| 638070 | LabVIEW crashes when calling the Children[] Property Node in a VI with reentrancy set to "Shared clone reentrant execution."
N/A Workaround: Use the Search Variable Container VI instead of the Children[] Property Node. The regular expression and class inputs can help filter the results. |
LabVIEW 2015 SP1 | N/A | 05/22/2017 |
| 639000 | LabVIEW crashes when updating the radix of a numeric control on an Actor Core VI that is running
Workaround: Update the display format of the control using a property node |
LabVIEW 2015 SP1 | N/A | 01/23/2018 |
| 639524 | Changing font to Application font can shrink constants inside of structures
In Japanese LabVIEW, changing the font of items on the block diagram from a non-default font to Application Font can cause constants within a structure to shrink Workaround: Select all items on the block diagram and press Ctrl+,1 to set them to Application Font again |
LabVIEW 2014 SP1 | N/A | 05/22/2017 |
| 640089 | DETT reports a reference leak when using the Open Data Storage express VI and Close Data Storage express VI
N/A Workaround: N/A |
LabVIEW 2016 | N/A | 05/22/2017 |
| 640243 | XY graph pointers do not copy correctly using Copy Data operation
When a graph annotation is displayed on an XY graph and the user copies the data using Data Operations>Copy Data, the image that is pasted does not properly display the pointers. Workaround: Use a waveform graph instead of an XY graph when possible |
LabVIEW 2012 SP1 | N/A | 05/22/2017 |
| 641269 | Interleaved TDMS Write with duplicate channel names fails to write data without returning an error
If you use the interleaved data layout with a TDMS Write, passing duplicate channel names in an array can cause some data to not be written to the TDMS file. Workaround: Use unique channel names in your array, or place the TDMS Write into a For Loop and index through each channel individually |
LabVIEW 2010 SP1 | N/A | 05/22/2017 |
| 643107 | Changing multiple plots' line styles does not work as expecting in XY graphs
In an XY graph with N data sets, changing the line style of data sets 2 through N will revert the line style for data set 1 to small dash Workaround: N/A |
LabVIEW 2012 SP1 | LabVIEW 2018.0 | 01/23/2018 |
| 647354 | Opening a new shared variable connection can block reading from other connected variables
When attempting to open a shared variable connection that times out, read operations happening in parallel may stall until the time out occurs. Workaround: N/A |
LabVIEW 2015 SP1 | N/A | 01/23/2018 |
| 648582 | Express VIs cannot be created in certain localized versions of LabVIEW
Workaround: N/A |
LabVIEW 2015 SP1 | LabVIEW 2018.0 | 01/23/2018 |
| 652898 | LabVIEW crashes when attempting to open detailed help for an EXE
If the Help path property of a VI points to a PDF file, LabVIEW will crash when trying to open the detailed help of the EXE Workaround: N/A |
LabVIEW 2015 SP1 | N/A | 01/23/2018 |
| 654057 | When using clusters with a reference to the same control to register for multiple events, LabVIEW does not properly handle all events.
After bundling a control reference into a cluster and registering for different events using the same cluster, only the first event registered will be handled by the event structure. Workaround: Use separate Register for Events nodes for each event you want to register for, then bundle the event registration refnums into a cluster |
LabVIEW 2017 | N/A | 01/23/2018 |
| 655865 | The VI Method Save.For Previous fails to maintain the status of the "Separate compiled code from source file" attribute
When you use the Save.For Previous method on a VI with the "Separate compiled code from source file" attribute set to true, the saved VI will have this attribute set to false. Workaround: Saving for previous through the File menu works as expected |
LabVIEW 2016 | N/A | 01/23/2018 |
| 656572 | In some cases, some primitives may not properly display coercion dots when converting between integer representations
Workaround: N/A |
LabVIEW 2012 SP1 | N/A | 01/23/2018 |
| 664649 | Accessing a DVR and deleting its reference in parallel can, in certain circumstances, cause LabVIEW to crash
Workaround: N/A |
LabVIEW 2016 | LabVIEW 2018.0 | 01/23/2018 |
| 670209 | Changing XControl state may lock XControl permanently
When changing XControl states in ways that conflict with pre-existing properties, it is possible to lock the state typedef and all of the property VIs. Unless the workaround applies, these VIs become permanently locked and the contained typedefs will be unable to update. Workaround: Right-click an instance of the state typedef that exists prior to the edit on non-locked VI and choose Review and Update from Typedef. This will fix all of the VIs, even locked VIs. |
LabVIEW 2014 SP1 | N/A | 03/12/2018 |
| 673954 | LabVIEW-built EXEs can crash when using channels that depend on type definitions.
Workaround: N/A |
LabVIEW 2017 | LabVIEW 2018.0 | 01/23/2018 |
| 674079 | Packed Libraries that have debugging enabled and use XNodes load slowly
Workaround: N/A |
LabVIEW 2013 SP1 | N/A | 01/23/2018 |
| 674968 | LabVIEW does not automatically detect the LabWindows/CVI Runtime installer as a required dependency when building an installer from an EXE that requires the LabWindows/CVI Runtime
Workaround: Manually include the LabWindows/CVI Runtime |
LabVIEW 2017 | N/A | 01/23/2018 |
| 676013 | LVMerge returns error 53 when the VI has a dependency on an XControl
Workaround: N/A |
LabVIEW 2017 | N/A | 01/23/2018 |
| 677020 | Channel wires do not automatically update minor changes in core data type (Not A Bug)
Minor changes in non-typedef data types passed to a channel wire do not automatically update the channel wires. As an example, changing the name of a string contained in a cluster will not update the type: creating an indicator from the channel wire's downstream endpoint will still show the original names of the cluster. This is not a bug. The situation is identical to using a queue, notifier, user event, or any other type-with-subtype that passes through a subVI terminal. If you have a queue of type cluster and you pass that queue into a subVI, then you change the field names of the upstream cluster, LabVIEW does not rewrite the terminal of the subVI. The only types that propagate changes to subVIs are typedefs. The endpoints of channels are subVIs and follow the same rules. LabVIEW does provide ways to request an update to the endpoints (see workaround). Workaround: Option 1. Right click on the channel endpoint and chose "Adapt To Element Type". This will rescript the endpoint to exactly match the core type. You will need to repeat this on the other endpoint(s) of the channel. Option 2. Using a typedef or strict typedef as the channel's core type will ensure the types always match. Any changes made to the typedef will be made to the channel. |
LabVIEW 2017 | N/A | 03/12/2018 |
| 678334 | Changing the keyboard shortcut of the Bookmark Manager to Ctrl+,Shift+,3 does not launch the Bookmark Manager when the shortcut is pressed.
Workaround: N/A |
LabVIEW 2013 SP1 | N/A | 01/23/2018 |
| 678964 | Nested XControls require recompile when built into Packed Project Libraries
When an XControl contains another XControl as part of its Facade.vi and is built into a Packed Project Library, it will error out and request a recompile. The recompile requires building the Packed Project Library a second time. The error will persist. Workaround: Either avoid nesting XControls or use their source directly and do not build them into a Packed Project Library |
LabVIEW 2015 SP1 | N/A | 03/05/2018 |
| 678973 | Tools->Synchronize with ni.com icon library fails in the LabVIEW Icon Editor
When attempting to synchronize the Icon Editor with the ni.com icon library, the operation fails. Workaround: Manually add the XML file found at http://www.ni.com/swf/iconlib/icons_filtered.xml |
LabVIEW 2010 SP1 | LabVIEW 2018.0 | 01/23/2018 |
| 684847 | Nested PPL VIs cannot be found when debugging built executable
PPLs containing VIs from other PPLs can successfully build into an executable. If a debuggable version of the executable is built, LabVIEW will show the VIs as not found. This prevents debugging from seeing the block diagram for the nested VIs. They will continue to run as programmed. Workaround: N/A |
LabVIEW 2016 | N/A | 03/14/2018 |
| 686080 | Replacing ActorFramework.lvlib with a packed project library causes LabVIEW crash
Replacing the ActorFramework.lvlib with a built version of ActorFramework.lvlibp in any project puts LabVIEW into an unstable state and leads to a crash breaking Actor Framework. Workaround: Delete the AFDebug folder from\resource. Delete the ActorFramework folder from\vi.lib. Repair the LabVIEW installation. |
LabVIEW 2017 SP1 | N/A | 03/12/2018 |
| 686273 | Sound Output VIs can cause LabVIEW to freeze on Mac OS
Using Sound Output Stop followed by Sound Output Write can cause LabVIEW to freeze when developing for Mac OS. Workaround: Use the Clear Buffer VI and then re-initialize task to restart the sound rather than pause playback. |
LabVIEW 2016 | N/A | 03/12/2018 |
| 686379 | Objects flattened to XML may revert data to default value
When passing a class to the Flatten to XML VIs, data may be reverted to the default value rather than the value passed on when calling Unflatten from XML later. Workaround: Wire the output from a setter VI to the Unflatten to XML instead of a constant. Use other means to flatten the VI to a generic data type. |
LabVIEW 2015 SP1 | N/A | 03/12/2018 |
| 686923 | Bring to Front Invoke Node may not bring window to front
Some operating systems will bring the window in front of all LabVIEW windows but not any other windows. If LabVIEW is not the active window at the time of this call, the window may not come on top of other running windows. Workaround: Use operating specific calls to find the window and bring it in front of all other windows. |
LabVIEW 2017 | N/A | 03/05/2018 |
| 688771 | Cannot add CA-signed certificates to LabVIEW Web Services
LabVIEW Web Services only accept certificates created by the LabVIEW API. Valid certificates will not appear as options to add to web services pushing design decisions to use LabVIEW certificates, even when not the best solution.. Workaround: Create a certificate with an identical name of the key for the signed certificate. Install the certificate selecting your root CA certificate. Create a new virtual host with the previously made certificate. Replace the LabVIEW generated private key with your correct private key in certstore. |
LabVIEW 2017 SP1 | N/A | 03/12/2018 |
| 691608 | Match Pattern primitive does not find matches if the Input String is empty.
Match Pattern function will return -1 as the offset past match if the input string is empty and the regular expression is ".*" Workaround: Use the Match Regular Expression function instead. |
LabVIEW 2014 SP1 | N/A | 09/10/2018 |
| 701859 | [Linux Red Hat 6.x] libniPythonInterface.so* symlinks are set to absolute paths
libniPythonInterface.so, libniPythonInterface.so.1 , libniPythonInterface.so.1.0.0 are linked in /usr/local/lib64/ with absolute paths instead of relative paths like the other .so files in the folder. This means that if the RTE is moved out of the root directory, then the EXE will not execute correctly. Workaround: Manually change the link targets for libniPythonInterface.so, libniPythonInterface.so.1, and libniPythonInterface.so.1.0.0 from specific file paths to relative paths. This should allow the RTE to execute in a non-root directory. |
LabVIEW 2018 | N/A | 09/14/2018 |
| 703331 | LabVIEW Built Application will crash at launch if contained in a folder that has any character not supported in the system codepage
If you use a non-native locale, a LabVIEW executable with a folder name that contains Unicode in its path will crash immediately when run. Workaround: Do not use any characters not supported in the legacy code page in the folder name containing the EXE. |
LabVIEW 2014 SP1 | N/A | 09/10/2018 |
| 704478 | Adding array manipulation functions between signed and unsigned numeric arrays incorrectly removes coercion dots
When wiring numeric arrays between unsigned and signed integers of the same bitness, introducing an array manipulation such as Transpose 2D array, Reverse 1D array, Array Subset, and Decimate will remove any coercion dots on subsequent indicators. However LabVIEW is still performing an in-place coercion to the data in the indicator. The data itself is coerced correctly, but the coercion dot is not shown. This can affect the results from VI Analyzer. Workaround: N/A |
LabVIEW 2010 SP1 | N/A | 09/14/2018 |
| 706182 | Mass Compile causes LabVIEW crash
LabVIEW 2018 64-bit crashes during Mass Compile if Vision VIs are included, but the Vision Development Module is not installed. Workaround: Install the Vision dependencies that are required. |
LabVIEW 2018 | N/A | 08/14/2018 |
| 706545 | Clicking greyed out option of the Scale Legend when using a Waveform Chart causes LabVIEW to crash
If you add a Waveform Chart to the Front Panel (without wiring anything to it on the Block Diagram) and then expand the Legend to include more Plots, set the Waveform Chart to Stacked Plots, make the Scale Legend visible, and then expand the Scale Legend to show more empty or greyed out y-scales, when you try to select any of the buttons on the greyed out portion, LabVIEW will crash. Workaround: If you wire any 2D array (even an empty 2D array of doubles) to the Waveform Chart before setting the Waveform Chart to Stacked Plots, the crash will not occur. |
LabVIEW 2014 SP1 | N/A | 09/14/2018 |
| 706578 | LabVIEW RTE crashes when calling a VI that calls an ActiveX object
LabVIEW Run-Time Engine crashes when calling into a mass compiled VI that calls into an ActiveX object. Workaround: Register Utilities\InstrumenSimulation.dll as an ActiveX server before mass compiling the VI. |
LabVIEW 2018 | N/A | 05/17/2019 |
| 715295 | DataSocket Write VI with default timeout can hang before proceeding
When using the DataSocket Write VI with the default 0 second timeout (or wiring in a 0 second timeout), the VI may hang for 10 seconds before completing. Workaround: Wire in a short timeout of several ms to the DataSocket Write VI. |
LabVIEW 2017 SP1 | N/A | 05/17/2019 |
| 723354 | Remote debugged EXE returns error when attempting to save class changes
After remote debugging an executable that contains a class, clicking Save on the prompt results in an error. Workaround: 1. Lock the classes you use before compiling an executable 2.Do not do remote debugging 3. Kill the process |
LabVIEW 2018 | N/A | 05/17/2019 |
| 724157 | [Linux] Build Specifications in Shipping examples may not be runnable by double-clicking
Most Linux shipping examples contain Build Specifications that default to a target output of 'main.exe'. This may not be directly runnable by double-clicking on a Linux OS. Workaround: 1. Change the name of the 'Target destination' in the build specs and remove '.exe' 2. Change name of built executable and remove the '.exe' 3. Run 'Main.exe' via the command line 4. Delete the default build spec and create a new one |
LabVIEW 2018 SP1 | N/A | 05/17/2019 |
| 727256 | LabVIEW doesn't make a local copy of lvanlys.dll when building a PPL
When building a Packed Project Library that includes a VI in the LabVIEW analysis library (lvanlys.dll), a local copy is not made to the output directory. Workaround: Copy the lvanlys.dll (...National Instruments\LabVIEW 2018\resource) to the PPL output directory. |
LabVIEW 2018 | N/A | 05/17/2019 |
| 727406 | LabVIEW UDP broadcast is inconsistent across different OS's.
If the UDP Open VI has 0.0.0.0 wired to the Net Address terminal, the behavior varies with OS. Windows XP and NI ETS will send on all interfaces, while Windows Vista, Windows 7, VxWorks, and Linux will send on the default interface. Workaround: There is currently no known workaround for this issue. |
LabVIEW 8.6.1 | N/A | Feb 17, 2020 |
| 729952 | Get Date/Time String does not work for dates beyond 2/5/2040
When trying to get a string for dates 2/6/2040 and beyond, the Get Date/Time String will instead provide an earlier, incorrect date. Workaround: Use the Format Date/Time String VI instead of Get Date/Time String |
LabVIEW 2013 SP1 | N/A | 05/17/2019 |
| 732570 | System decoration frame bleeds through system checkbox boolean text
In a System Tab Control with a System Decoration frame, the color bleeds through the boolean text of a system checkbox. Workaround: Use a normal button control configured as an indicator behind the boolean text, and resize it to match the width of the text. |
LabVIEW 2016 | N/A | 05/17/2019 |
| 733608 | Class VIs that call shared variables in a library in an auto-populating folder will not be loaded
If a VI in a class calls a shared variable that is in a library in an auto-populating folder, it will not find the shared variable when the project is loaded Workaround: Make the folder a snapshot instead of auto-populating and reopen the project |
LabVIEW 8.6.1 | LabVIEW 2014 | Feb 18, 2020 |
| 758319 | Selecting a newer version of a .NET assembly does not reload assembly
Changing a constructor from an old version of a .NET assembly to a newer version at edit time does not cause the new assembly to be loaded and consequently none of the new functionality is available. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2010 32-bit | N/A | Feb 14, 2020 |
| 782272 | Some nodes may crash or yield incorrect/inconsistent results when Inlined
An Inline public methodVI calling a private-scope method VI, inlined into a non-class caller may give a runtime error when trying to call the private method from the inlined code in the non-class caller. Workaround: Do not try to Inline VIs with these nodes. |
LabVIEW 2010 32-bit | N/A | Feb 17, 2020 |
| 783045 | Updating the Labels of a Cluster Written to a Chart Does Not Update the Cluster Used for Chart History
Changing the Label of elements in a cluster written to the Waveform Chart does not update the label of the cluster when read from the Waveform Chart Data History Property. Workaround: Temporarily wire up a completely different data type to the Waveform chart indicator and then rewire the original cluster. The changes will now propagate to the Chart History. |
LabVIEW 2009 32-bit | LabVIEW 2015 | Feb 14, 2020 |
| 783080 | It is not possible to customize the Run-Time Shortcut menu of a 3D Graph
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2012 | N/A | Feb 17, 2020 |
| 783247 | The MonthCalendar .NET control automatically resizes to the incorrect size when the VI is run
Workaround: At the beginning of the code write to the Container Bounds property node "ContBounds" for the .NET container. While the code is running the calendar will have the right size |
LabVIEW 2012 | N/A | Feb 14, 2020 |
| 783456 | Double Numeric Slide can not be Set to 0 when it has Defined Limits with Mouse
A user can not slide a Double Numeric Slide to 0 when it has defined increment, maximum, and minimum properties. Instead of 0, a value very close to 0 will be entered ie: 5.55112E-16. Workaround: Do not set both defined maximum and minimum for the slide. Instead, change one of them to Inf or -Inf. Also a value of 0 can be entered into the digital slide. |
LabVIEW 2012 | N/A | Feb 17, 2020 |
| 783469 | Updates to Global Variables Not Visible when Remote Debugging a LabVIEW Built Stand-Alone Application
If the updates occured before connecting to the Remote Application with the debugger, the updates won't be visible. Updates to the Global Variable after connection with the debugger is establish will be visible. Workaround: Change the build specification for the stand-alone application to wait for debugger on launch, so no Global Variable updates can happen until a debug session is started. |
LabVIEW 2012 SP1 | N/A | Feb 14, 2020 |
| 783573 | The "do not save automatic changes" setting does not affect libraries
The "do not save automatic changes" options setting does not affect any type of library, including classes. Workaround: There is currently no known workaround for this issue. |
LabVIEW 8.0 | N/A | Feb 18, 2020 |
| 783680 | Non-printable Characters in the Description of Will Corrupt LabVIEW Classes and Libraries
Non-printable characters can be inserted into the description of LabVIEW Classes and Libraries with the Description Property Node. This will corrupt the .lvclass or .lvlib file. Workaround: The .lvclass or .lvlib file can be opened in a text editor, and the description can be manually deleted to recover the files. |
LabVIEW 2012 | N/A | Feb 18, 2020 |
| 783687 | Editing large strict type definitions can take a long time to update
When large type definitions are updated, all instances in memory require an update. This update can take many minutes for very large type definitions. Workaround: Use smaller type definitions, or consider using LabVIEW classes to contain your type data. |
LabVIEW 7.1.1 | N/A | Feb 18, 2020 |
| 783924 | Listbox Control With Transparent Cell Background Does not Grey Disabled Item
Workaround: Make the background color of the cells match the background of the panel, instead of making them transparent. |
LabVIEW 2011 32-bit | N/A | Feb 17, 2020 |
| 788957 | 2GB file size limit of datalog files
The maximum size of datalog files is 2 GB. Workaround: There is currently no known workaround for this issue. |
LabVIEW 8.0 | N/A | Feb 17, 2020 |
| 792659 | Getting an Entire Column of Data from a 2D Array in the MATLAB® Script Node Returns Only 1 Element
In the context of the MATLAB® Script Node, attempting to return an entire column of data from an array using a command like "column1 =, array2D(:,1)," returns only a single element. This same operation on a row "row1 =, array2D(1,:)," , returns the entire row successfully. Workaround: Transpose the array, and get the data in it's context as a row. |
LabVIEW 2012 | LabVIEW 2015 | Feb 14, 2020 |
| 792730 | Formula VI does not execute pow(x,y) function
Workaround: Use the formula node to use the pow(x,y) function. If you need to change this programmatically, use the Power of X function in G code. |
LabVIEW 2009 32-bit | N/A | Feb 17, 2020 |
| 795241 | Adding or subtracting timestamps causes a conversion to double and precision loss
Workaround: Cast the timestamps to clusters of U64 'seconds since epoch' and I64 'fractions of a second' before the operation and then cast back to timestamp after the operation |
LabVIEW 2011 | N/A | Feb 17, 2020 |
| 819647 | Deleting a second y-axis on a waveform graph with a cursor crashes LabVIEW
When using a waveform graph indicator, it is possible to crash LabVIEW with an access violation error 0xC0000005 at EIP=,0x00FE9E79 by creating two y-axis scales, creating a graph cursor, changing the cursor's associated y-axis, and then deleting the original y-axis scale. Workaround: Remove the scale from the waveform graph, remove the unwanted y-axis scale, then recreate the cursor. |
LabVIEW 2013 SP1 | LabVIEW 2016 | Feb 17, 2020 |
| 819764 | VI.Control Value.Set will Crash LabVIEW When Value Non-Variant Data is Used for Value Parameter
The crash will happen when VI.Control Value.Set is invoked upon a VI reference that has been opened by Open VI Reference. Workaround: Cast data to variant before wiring to Value parameter. |
LabVIEW 2012 | LabVIEW 2016 | Feb 17, 2020 |
| 819932 | It is not possible to save a VI with the name of another VI in memory, even if they are in different libraries
LabVIEW does not check the library namespace when determining if a VI is being saved with a name that is already in use. If a VI is in memory, it is not possible to save another VI with the same name in the same project even if they are in different libraries. Workaround: Close the other VIs with the same name so they are not in memory. |
LabVIEW 2013 | LabVIEW 2016 | Feb 18, 2020 |
| 847135 | Error 6 occurred at Create Folder in Create Directory Recursive.vi when building an application (EXE), shared library (DLL), source distribution or web service
When building a Build Specification, the build process fails with Error 6 at Create Folder in Create Directory Recursive.vi. This usually happens if the path one of the files generated by the build (temporarily during the build process or as part of the output) is too long. The operating system requires paths for files to be less than 255 characters. Workaround: There is currently no known workaround for this issue. |
LabVIEW 8.2.1 | LabVIEW 2015 | Feb 14, 2020 |
| 859021 | When creating .NET assemblies in LabVIEW, 1-dimension arrays of doubles or strings are represented as 2-dimension arrays of rank 1
When creating .NET assemblies in LabVIEW, 1-dimension arrays of doubles or strings are represented as 2-dimension arrays of rank 1. This can create an issue when the assembly is used in Visual Studio 2015 which will not accept 2-dimensional arrays of rank 1. Workaround: Pass a 2D array in LabVIEW instead of a 1D array. |
LabVIEW 2013 SP1 | LabVIEW 2017 | Feb 14, 2020 |
| 882096 | Certain operations will not let the System Exec VI return on Windows 10
Certain commands, such as renaming a file, will cause the System Exec VI to indefinitely wait for a response on Windows 10. The IDE will continue to be responsive and the VI may be aborted. This will only occur with "Wait Until Completion" is set to True. Workaround: Set "Wait Until Completion" parameter to False |
LabVIEW 2016 | LabVIEW 2018 | Feb 18, 2020 |
| 882110 | Template methods in a C++ DLL do not appear in the Function Name drop down list of the Call Library Function Node.
Some C+,+, DLLs include methods which are created from a template during compilation. These template methods will not appear in the list of function names when using the Call Library Function Node. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2015 SP1 | LabVIEW 2018 | Feb 17, 2020 |
| 883542 | Flattening an EXT representation numeric to JSON causes loss of precision
Workaround: Use Format Into String followed by Flatten to JSON |
LabVIEW 2013 SP1 | LabVIEW 2018 | Feb 18, 2020 |
| 885959 | Waveform graphs can resize at runtime
For very large floating point numbers in a waveform graph, the control can permanently resize itself in an attempt to fit the large numbers in the axis label Workaround: Use Automatic or Scientific as the format type for the Y Axis with large floating point numbers |
LabVIEW 2017 | N/A | Feb 17, 2020 |
| 886685 | Calling the "Web Server: Server Active" property causes a small memory leak.
Calling the "Web Server: Server Active" property on any supported platform (including RT) creates a small memory leak. Workaround: Restart the application to allow the OS to reclaim the memory, or do not call this property often. |
LabVIEW 2014 | N/A | Feb 19, 2020 |
| 889219 | Type Defined Shared Variable not found in Executable
Workaround: Disconnect from Type Def during the build. |
LabVIEW 2010 32-bit | N/A | Feb 18, 2020 |
| 95055 | Save for previous fails if file path is too long
Save for previous copies the folder being saved to a temp location, if the resulting file paths exceed the limit defined by the OS, the function fails. Workaround: Copy the folder being saved to the root directory to reduce the file path length and Save for Previous from that location. |
LabVIEW 8.5 | N/A | 11/17/2009 |
| 953790 | Session Timeout value from Create Session.vi should be I32
When a Web Session is created via the Create Session.vi, the default value for a time out is U32 but should be an I32 instead. The session is invalid if a value in the upper half of the U32 range is used. Workaround: Only use values in the I32 range. |
LabVIEW 2016 | N/A | Jan 6, 2021 |
| 991959 | Performance degradation in Channel Wire generation time
Generating Channel Wires causes performance degradation in LabVIEW 2020. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 997053 | LabVIEW Crashes after Using Clean Up Diagram When Label with Bookmark Is Attached to Wire inside a Loop
LabVIEW crashes when the "Clean Up Diagram" on a VI has a label containing a bookmark that is positioned outside a loop but is attached to a wire inside the loop. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2019 | LabVIEW 2022 Q3 | Jan 6, 2021 |
| 997305 | LabVIEW can crash or display incorrect text characters when "Use Unicode UTF-8" option enabled in Windows
On systems that have the Windows option "Beta: Use Unicode UTF-8 for worldwide language support" enabled in Region settings, LabVIEW can crash or display garbled text in some languages. To find the Region settings go to Control Panel > Region > Administrative > Change system locale...This option causes the system default code page to be UTF-8, which LabVIEW does not support.R&,D made changes in the LabVIEW 2020 f1 patch to prevent the crash, but some text will still display incorrectly in some languages. Workaround: Disable the "Beta: Use Unicode UTF-8 for worldwide language support" option in Windows. |
LabVIEW 2020 | LabVIEW 2020 f1 | Aug 5, 2020 |
| 997357 | Slowdown in loading PPLs in LabVIEW 2020 from TestStand
Calling LabVIEW 2020 built PPLs from TestStand causes slowdowns if the PPLs are loaded dynamically into memory and unloaded after the step executes. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2020 | LabVIEW 2020 SP1 | Dec 2, 2020 |
| 2619768 | Duplicate Block Diagram Constant Differences in Compare VI Results
When comparing VIs, the same change to a block diagram constant can appear multiple times. Workaround: Fixed. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q1 Patch 1 | Mar 8, 2024 |
| 2643576 | Incorrect VI Reference Opened by Open VI Reference When Created from an Existing Strict VI Reference
When passing a strict VI reference to the VI path parameter of Open VI Reference, the VI reference output forms incorrectly. The wire's data type is a strict VI reference, but the reference is non-strict. Passing this reference to functions that require a strict VI reference, such as Start Asynchronous Call, will result in a run-time error. Workaround: Fixed. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q1 Patch 1 | Mar 8, 2024 |
| 719917 | Sound File Open for Write Can Produce Unexpected Values
Sound File Write Open.vi can produce unexpected values since it rounds sample rates down rather than to the nearest. Workaround: Fixed. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q1 Patch 1 | Mar 8, 2024 |
| 2645388 | Building a Packed Library May Fail Due to Incorrect Path to .NET DLL
In LabVIEW 2024 Q1, building a packed library can fail because LabVIEW incorrectly resolves a relative path to a .NET DLL. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 221246 | LabVIEW Does Not Propagate Type Definition Changes to Containers, Causing Unexpected Run-Time Behavior
After you change a type definition's qualified name (for example, by removing it from a class), LabVIEW may fail to apply such change to event refnums or other container data types that include that type definition. VIs that reference the affected container data type won’t show as broken, but may have unexpected run-time behavior Workaround: There is currently no known workaround for this issue. |
LabVIEW 2016 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2597746 | LabVIEW Fails to Create Probe for Cluster that Contains IMAQ Image
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q3 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2663212 | VI Block Diagram Wires Sometimes Draw Incorrectly on Ubuntu
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2675593 | LabVIEW (64-bit) Sometimes Gives Incorrect Results When Converting Timestamps to Strings with Fractional Seconds Exceeding 19 Digits
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2682003 | Resizing Loops Sometimes Moves Tunnels Unnecessarily
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2687156 | Compare VIs Does Not Report Differences in Window Transparency Values
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2694996 | Quick Drop Shortcuts Do Not Work When Placing VIs Shipped with LabVIEW
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2695155 | LabVIEW Can Display the Wrong Portion of a VI Block Diagram During Debugging When Diagram is Zoomed In
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2707687 | In Multi-Monitor Systems, LabVIEW Sometimes Fails to Display the Review and Update from Type Def. Dialog
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q3 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2713392 | Compare VIs Does Not Report Adding a Custom Run-time Menu on a Control as a Difference
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2016 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2714418 | LabVIEW Sometimes Cannot Display File Dialog After Creating Override Methods in a Class
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q3 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2717959 | LabVIEW Controls Do Not Receive Mouse Wheel Event with Ctrl Key Pressed
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2023 Q3 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2731705 | On Property and Invoke Nodes, the Right-click Help Menu for the Selected Property or Method is Missing
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2742395 | LabVIEW Crashes When Comparing VIs with Different Passwords
When comparing VIs that are protected with different passwords, LabVIEW crashes after you enter the passwords. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2748388 | Compare VIs Does Not Report Difference When Label Changes Attached Object
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2752615 | LabVIEW Editor Responds Slowly with Navigation Window Open and Block Diagram Zoomed
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2767151 | Mass Compile Does Not Update Cache for Some VIs Installed in LVAddons
Mass compile doesn't update the compile cache for VIs installed in the shared LVAddons folder if the VIs are in read-only LLBs. Without an updated cache, TestStand cannot run the VIs using the LabVIEW Run-Time Engine. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 | Jul 17, 2024 |
| 2781966 | Unexpected Save Dialogs When Maintaining Projects in Older Save Version
LabVIEW may prompt you to save changes when editing VIs in a project maintained in an older version. For example, using DQMH for operations such as creating Private Events or validating a DQMH module will trigger a prompt to save VIs, indicating that the VI's source save version has changed. Workaround: There is currently no known workaround for this issue. |
LabVIEW 2024 Q3 | N/A | Jul 17, 2024 |
| 2785983 | LabVIEW Sometimes Prompts You to Save Unedited VIs
LabVIEW may prompt you to save VIs that reference shared libraries, including some VIs in the Electrical Power Toolkit. If you do not save the VIs, deployment to Real-Time targets can fail. Workaround: Save the VIs when prompted. You may need to modify the VI permissions or run LabVIEW as an administrator to save the VIs. |
LabVIEW 2024 Q3 | N/A | Jul 17, 2024 |
| 2786419 | Palette Categories Are Visible Even When Empty
All the palette categories are visible by default. Workaround: On a pinned palette, go to Customize > Change Visible Palettes, and select or deselect palettes to show or hide them. Fixed in LabVIEW 2024 Q3 Patch 1. |
LabVIEW 2024 Q3 | LabVIEW 2024 Q3 Core Patch 1 | Jul 17, 2024 |
| 2798144 | MATLAB Script Nodes Break VIs
VIs containing MATLAB Script Nodes are broken because the script support DLL is not found. Workaround: Fixed in LabVIEW 2024 Q3 Patch 1. |
LabVIEW 2024 Q3 | LabVIEW 2024 Q3 Core Patch 1 | Jul 17, 2024 |
| 2799931 | Command Prompt Window Appears Briefly During Launch of LabVIEW on Windows
Workaround: Fixed in LabVIEW 2024 Q3 Patch 1. |
LabVIEW 2024 Q3 | LabVIEW 2024 Q3 Core Patch 1 | Jul 17, 2024 |
| 2800868 | LabVIEW Numeric Control Fails to Paste Values Copied from Microsoft Outlook or Word
Workaround: Fixed in LabVIEW 2024 Q3 Patch 1. |
LabVIEW 2024 Q1 | LabVIEW 2024 Q3 Core Patch 1 | Aug 7, 2024 |
| 2811695 | LabVIEW Class Becomes Corrupted After Editing Private Data Control and Saving from Unsaved Changes Dialog
Workaround: Fixed in LabVIEW 2024 Q3 Patch 1. |
LabVIEW 2024 Q3 | LabVIEW 2024 Q3 Core Patch 1 | Aug 7, 2024 |
| 812117 | Find Parallelizable Loops Does Not Analyze VIs Under Targets
Workaround: There is currently no known workaround for this issue. |
LabVIEW 2009 SP1 | LabVIEW 2024 Q3 | Jul 17, 2024 |