This document contains information about all patches available for the following LabVIEW products:
All issues fixed in each patch are listed in the tables below. NI strongly recommends that you install the latest patch to all LabVIEW 2017 SP1 installations.
Issues Fixed in LabVIEW 2017 SP1 f4 Patch
| ID | Description |
| 659963 | Typecasting from a string to an IVI or VISA IO Control in parallel crashes LabVIEW. |
| 661720 | Tunnels remain on borders of case structures after you drag wired items out of the structure. |
| 673108 | LabVIEW can disconnect wires from tunnels when dragging items between frames of a Flat Sequence Structure. |
| 673910 | Unnecessary tunnels are created when you drag wired items into and out of structures. |
| 677297 | LabVIEW can change the settings of a tunnel when dragging items connected to the tunnel between structures. |
| 679673 | LabVIEW can crash when dragging a node between frames of a Flat Sequence Structure. |
| 680767 | (Windows) In rare cases, LabVIEW can accept ActiveX connections before the ActiveX server has fully initialized. |
| 682179 | LabVIEW can disconnect wires from tunnels when dragging items between structures. |
| 7120211 | LabVIEW can crash when you drag nodes out of a Flat Sequence structure. |
| 713011 | LabVIEW may crash when you drag elements into structures within In Place Element Structures. |
| 714264 | LabVIEW can crash when you drag structures out of a Flat Sequence structure. |
| 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. |
| 715347 | Reduced 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. |
| 715760 | LabVIEW can crash when you drag items out of nested structures. |
| 716611 | In rare cases, LabVIEW can crash when you place a probe after certain licensed typedefs. |
Issues Fixed in LabVIEW 2017 SP1 f3 Patch
Note: This patch was made available on NI Update Service.
| ID | Description |
| 670440 | When 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. |
| 674999 | Variants running in parallel have the potential to force execution into a single thread. |
| 681894 | In rare cases, LabVIEW can crash when you access the menu bar if a URL is stored in the clipboard. |
| 686077 | In rare cases, malleable VIs can find their way into an infinite compile. |
| 687146 | Malleable VIs have the potential to store additional debugging data. |
| 687250 | Attempting to use Find Instrument Drivers from the Help menu could fail to connect. |
| 688061 | Nested malleable VIs have the potential to create unintended shared instances of dependencies. |
| 688072 | VI sanity checks sometimes take place additional times. |
| 688094 | Malleable VIs have the potential to start a compile when removed from memory. |
| 688384 | When you apply changes to type definitions, additional compiles may take place. |
| 688992 | In rare cases, a race condition can affect simultaneous remote VI Server open and close calls to the same VI. |
| 691392 | In rare cases, LabVIEW can crash when searching within a VI for text using Find and Replace while VIs are unloaded from memory. |
| 691991 | In rare cases, Type Specialization structures may get out of order until VI is recompiled. |
Issues Fixed in LabVIEW 2017 SP1 f1 Patch
Note: This patch was made available on NI Update Service.
| ID | Description |
| 671753 | The LabVIEW Application Builder has the potential to hang when building malleable VIs with subarray or substring inputs. |
| 672120 | Malleable VIs may not properly break after you rename a class method that the mallable VI calls when performing class substitution. |
| 672133 | Non-required terminals on Malleable VIs fail to revert to their default data type after removing the input of a different data type. |
| 672594 | The LabVIEW Application Builder may incorrectly return error 13 when building a build specification that uses malleable VIs. |
| 673694 | LabVIEW may return old array data from a Call Library Function Node when the error in parameter contains an error. |
| 675386 | LabVIEW has the potential to crash when closing a packed project library containing a child class that references its parent class in its private data control. |
| 676190 | LabVIEW has the potential to crash when loading a VI that has a coercion dot on a class wire when the target class is missing. |
| 677003 | In rare circumstances LabVIEW may hang when you use queue functions with a timeout value of zero. |
| 681475 | LabVIEW has the potential to crash when renaming a VI that calls a preallocated reentrant clone VI if you create a new VI with the old VI's name that calls the same reentrant VI. |
Patch Downloads
Download LabVIEW and LabVIEW Patches