Archived: LabVIEW 2013 Patch Details

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

The LabVIEW 2013 f3 Patch is the latest update available for LabVIEW 2013 (64-bit) Development Environment. The LabVIEW 2013 f2 Patch is the latest available for LabVIEW 2013 (32-bit) Development Environment for Windows. 

The patch fixes the issues listed in the table below. NI strongly recommends this patch for all LabVIEW 2013 installations. Patches are cumulative, so the LabVIEW 2013 f2 Patch also includes all of the fixes from the LabVIEW 2013 f1 patch.

Note: The LabVIEW 2013 f2 patch installs automatically if you update to LabVIEW 2013 through NI Update Service. To install the patch manually, refer to the Drivers and Updates links below.

Issues Fixed in LabVIEW 2013 f3 (64-bit)

434571In LabVIEW 2013 (64-bit), manipulating arrays with the array subset node can cause LabVIEW to crash.


Issues Fixed in LabVIEW 2013 f2

427033In the LabVIEW 2013 FPGA Module, using <+-,32,16> fixed point values can cause VI corruption.
429282In LabVIEW 2013, including VIs from libraries that have unsatisfied dependencies cause building an installer to fail with error 1 "Error Generating Preview."
429724Under certain conditions, an internal race condition can cause the LabVIEW UI thread to stop updating front panel objects.
429726LabVIEW crashes when a .NET event callback calls a VI that has already been deregistered in LabVIEW.
230811.NET events leak memory when registered and unregistered repeatedly.

Issues Fixed in LabVIEW 2013 f1

422680Publishing a Web service in LabVIEW 2013 to the Application Web Server will fail if your primary network adapter is a 802.11 (WiFi) network adapter.
415901When repairing LabVIEW 2013 the Service Locator dependency is uninstalled.
408955Crash when deleting a newly created comment with Automatic Tool Selection turned off.
423385In LabVIEW 2013, once a Type Definition is made a Strict Type Def, it can not be made non-strict.
423373Under certain conditions, a compiler optimization will cause array shift registers to share memory space.

Related Links: 
Drivers and Updates: LabVIEW 2013 (32-bit) f2 Patch
Drivers and Updates: LabVIEW 2013 (64-bit) f3 Patch