LabVIEW 2016 Patch Details

This document contains information about all patches available for the following LabVIEW products:

  • LabVIEW 2016 (32-bit and 64-bit) for Windows, OS X, and Linux
  • LabVIEW 2016 Run-Time Engine (32-bit and 64-bit) for Windows, OS X, and Linux

All issues fixed in each patch are listed in the tables below. NI strongly recommends that you install the latest patch to all LabVIEW 2016 installations.


Issues Fixed in LabVIEW 2016 f7 Patch


680767(Windows) In rare cases, LabVIEW can accept ActiveX connections before the ActiveX server has fully initialized.
715178(Windows) Reduced the overhead for drawing images and text on Windows 10. This was most noticeable when there were many different controls with text and/or images to draw.
715347Reduced the overhead for updating front panel controls with new data from the block diagram. This was most noticeable for applications with a large number of VIs.
716611In rare cases, LabVIEW can crash when you place a probe after certain licensed typedefs.

Issues Fixed in LabVIEW 2016 f6 Patch


649952In rare cases, LabVIEW can crash while repeatedly unflattening data from a string.
670440When a VI with user events registered leaves memory, there is a potential for the event to still be processed and LabVIEW throws a Null Window error.
674999Variants running in parallel have the potential to force execution into a single thread.
681894In rare cases, LabVIEW can crash when you access the menu bar if a URL is stored in the clipboard.
691392In rare cases, LabVIEW can crash when searching within a VI for text using Find and Replace while VIs are unloaded from memory.

Issues Fixed in LabVIEW 2016 f5 Patch


Note: This patch was made available on NI Update Service.


619333Simultaneous calls of the .NET Object to Variant VI had the potential to crash LabVIEW on Windows.
659963Typecasting from a string to an IVI or VISA IO Control in parallel crashes LabVIEW.
635495Menus within the LabVIEW environment may not display correctly on systems with display scaling set to greater than 100%.
607006On Windows 10 Anniversary Edition (release 1607) with a different application as the current focus, LabVIEW will receive clicks as making LabVIEW the focused window rather than processing the area clicked.
627910Saving very large projects with complex dependency relationships may take significantly longer than expected.
638772In certain cases, making edits to particular wires can cause the LabVIEW environment to go unresponsive.
639388In certain cases, expanding a class property node will cause LabVIEW to be momentarily unresponsive.
663538LabVIEW may fail to unreserve VIs called by dynamically loaded classes, which makes LabVIEW crash.
597858In some cases, you may receive File Permissions Error 44 when saving a LabVIEW file to a Windows Server from a computer running Windows 10.
670018VIs within an LLB fail to load if the VI's uncompressed size is larger than 4 MB.


Issues Fixed in LabVIEW 2016 f4 Patch


653897Make LabVIEW more robust when presented with corrupted resource files.


Issues Fixed in LabVIEW 2016 f2 Patch


Note: This patch was made available on NI Update Service.


615288Using "Save for Previous" with VIs containing some classes can cause a LabVIEW load error in the previous version.
613416The installer of the LabVIEW evaluation version for Mac OS X places some files in the improper place when you use it on a system that has a previous version installed.
611838The abort behavior of the Accumulator Tag channel wire does not match that of other implementations.
611810"Save for Previous" does not work correctly with VIs containing some types of channel wires.
611315Queues, notifiers, rendezvous and semaphores may return an unexpected timeout when used in particular ways. For more information, please see details regarding timeout behavior for these mechanisms in LabVIEW.
609551"This VI" may return incorrect references when returned from an asynchronously called sub VI.
606365Dragging a control or indicator to the edge of the block diagram can cause duplication of the front panel object.
603576In some instances channel wire endpoints for classes or type definitions can load broken.
603562Using dynamically dispatched VIs with unwired input terminals can, in some cases, cause crashes.
615195Resizing the "Add Variant Attribute Get / Replace" border node on the In Place Element structure can cause a crash.
617917In some cases, particularly with TestStand Fast Loading enabled, loading some classes may cause LabVIEW to crash.
624957Memory corruption, usually resulting in an immediate crash, can occur when loading a file containing invalid data. See TALOS-2017-0269 (External Link) for more information.


Issues Fixed in LabVIEW 2016 f1 Patch


599478LabVIEW may not update classes on real-time targets after changing the inplaceness of a connector pane terminal for a VI within those classes.
595814When passed strings containing specific combinations of variant data, the Unflatten From String VI may take at most several minutes to return error 116.
584378LabVIEW has the potential to crash when simultaneously setting multiple variant attributes to empty variant constants.
602230Channel wires may not break appropriately when two conflicting channel sinks are wired together.
603092After rearranging the tabs in a tab control, LabVIEW has the potential to crash when running or saving that VI.
603023Channel wire templates do not adapt to type changes of event registration refnums.


Issues Fixed in LabVIEW 2016 Installation Patch

Note: This patch only applies to the LabVIEW 2016 (32-bit and 64-bit) Development Environment for Windows. This patch was made available on NI Update Service.


598630Installing LabVIEW 2016 from a Distribution or Suite Development Environment over a previous 2016 installation will incorrectly inform the customer "Please uninstall LabVIEW 2016 Beta Software".