Company Events Academic Community Support Solutions Products & Services Contact NI MyNI

LabVIEW 2016 Readme for Windows

June 2016

This file contains important information about LabVIEW 2016 for Windows, including system requirements, installation instructions, a partial list of bugs fixed for LabVIEW 2016 for Windows, and known issues.

Refer to the NI website for the latest information about LabVIEW.

Refer to the labview\readme directory for readme files about LabVIEW add-ons, such as modules and toolkits.

System Requirements

Installation Instructions

Product Security and Critical Updates

LabVIEW 2016 (64-bit)

Known Issues

Bug Fixes

Accessing the Help

Additions to the LabVIEW Help

Finding Examples

Automating the Installation of NI Products

Using NI Software with Microsoft Windows 10

Using NI Software with Microsoft Windows 8.1

NI Software Support for Microsoft Windows 7, Windows Vista, Windows XP, and Windows Server 2003

Legal Information


System Requirements

LabVIEW 2016 has the following requirements:

Windows Run-Time Engine Development Environment
Processor Pentium III/Celeron 866 MHz (or equivalent) or later (32-bit)
Pentium 4 G1 (or equivalent) or later (64-bit)
Pentium 4M (or equivalent) or later (32-bit)
Pentium 4 G1 (or equivalent) or later (64-bit)
RAM 256 MB 1 GB
Screen Resolution 1024 x 768 pixels 1024 x 768 pixels
Operating System Windows 10/8.11/7 SP12
Windows Server 2012 R21
Windows Server 2008 R2 SP12
Windows 10/8.11/7 SP12
Windows Server 2012 R21
Windows Server 2008 R2 SP12
Disk Space 620 MB 5 GB (includes default drivers from the NI Device Drivers media)
Color Palette N/A LabVIEW and the LabVIEW Help contain 16-bit color graphics. LabVIEW requires a minimum color palette setting of 16-bit color.
Temporary Files Directory N/A LabVIEW uses a directory for storing temporary files. NI recommends that you have several megabytes of disk space available for this temporary directory.
Adobe Reader N/A You must have Adobe Reader installed to search PDF versions of all LabVIEW manuals.
1 NI software installs VC2015 Runtime and .NET 4.6.1. Windows 8.1 and Windows Server 2012 R2 require Microsoft updates to support these items. Refer to Microsoft KB2919442 and KB2919355 for more information about how to install these updates.

2 NI software is signed with a SHA-256 certificate. Windows 7 SP1, Windows Embedded Standard 7 SP1, and Windows Server 2008 R2 SP1 require Microsoft updates to support SHA-256. Refer to Microsoft KB3033929 for more information about how to install this security update.

Note  You cannot access LabVIEW using a Guest account on Windows.

Installation Instructions

Depending on whether you are installing LabVIEW for the first time or upgrading from a previous version, refer to one of the following documents for information about installing LabVIEW:

You can access the LabVIEW Installation Guide and the LabVIEW Upgrade Notes at ni.com as well as on the installation media.

Note

Product Security and Critical Updates

Visit ni.com/security to view and subscribe to receive security notifications about NI products. Visit ni.com/critical-updates for information about critical updates from NI.

LabVIEW 2016 (64-bit)

When run on Windows (64-bit), LabVIEW 2016 (64-bit) provides access to more memory than a 32-bit operating system or a 32-bit application can provide. LabVIEW 2016 (64-bit) is available in English only.

Supported Hardware

Refer to the NI website for information about drivers compatible with LabVIEW 2016 (64-bit). For GPIB devices, you must use at least NI-488.2 2.6 for Windows. Refer to the specific hardware documentation for more information about compatibility with LabVIEW 2016 (64-bit).

Supported Modules and Toolkits

LabVIEW 2016 (64-bit) supports a limited number of modules and toolkits. The following list compares the modules and toolkits available on the LabVIEW Platform installation media.

Product LabVIEW 2016 (32-bit) LabVIEW 2016 (64-bit)
Advanced Signal Processing Toolkit
Control Design and Simulation Module
1
Database Connectivity Toolkit
DataFinder Toolkit
Datalogging and Supervisory Control Module
Desktop Execution Trace Toolkit for Windows
Digital Filter Design Toolkit
FPGA Module
MathScript RT Module
2
Report Generation Toolkit for Microsoft Office
Real-Time Module
Robotics Module
SoftMotion Module
Statechart Module
Sound and Vibration Measurement Suite
Unit Test Framework Toolkit
VI Analyzer Toolkit
Vision Development Module
1 The Control Design and Simulation Module (64-bit) does not support the System Identification VIs, System Identification Assistant, and Control Design Assistant.

2 The MathScript RT Module (64-bit) does not support the libraries class of MathScript RT Module functions.

You can install modules and toolkits supported by LabVIEW 2016 (32-bit) using the LabVIEW Platform installation media. To install modules and toolkits supported by LabVIEW 2016 (64-bit), refer to the NI website for available web downloads or use the LabVIEW 2016 (64-bit) installation media. Refer to the NI website for information about obtaining a copy of LabVIEW 2016 (64-bit).

Refer to the readme of each product for more information about 32-bit and 64-bit support, system requirements, installation instructions, and activation. For information about products not listed in the previous table, refer to the user documentation of those products.

Known Issues

You can access the software and documentation known issues list online. Refer to the NI website for an up-to-date list of known issues in LabVIEW 2016.

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed in LabVIEW 2016. This is not an exhaustive list of issues fixed in the current version of LabVIEW. If you have a CAR ID, you can search this list to validate that the issue has been fixed.

ID Fixed Issue
333388 Incorrect highlight execution order with LVOOP property node
405304 Menu Item VIs can cause LabVIEW to crash
425622 Edit Events menu for Event Structures can delete the new event you are trying to create
434420 Leading zeros are not allowed in Numeric Case Selector values
463239 Resizing the front panel in an EXE and running Quit LabVIEW.vi causes an access violation
468139 .NET Callback Event VI keeps the Callback VI reserved even after calling a Close Reference VI is called
518954 Unconstrained Downhill Simplex ignores some stopping conditions
519216 LabVIEW crash when closing subVI Icon Editor that was opened from VI Hierarchy
526175 Spreadsheet String to Array VI crashes when an empty string is wired to delimeter input
530595 Not a Refnum Primitive returns incorrect value when evaluating a specific type of "Invalid Refnum"
533890 lvinput.dll crashes on Surface Pro 3
534553 Quit LabVIEW function closes VI if you choose cancel
539895 File Dialog Express VI alters error chain
544435 1-D Array Probe Display Window has issues with high resolutions
544526 Fatal Internal Error 0x89B93EF0: "drawmgr2.cpp" when running Mac application for extended time
544533 Scripting dynamic events on an event structure returns Error 1
544907 Delaunay Triangulation hangs on certain input data
546555 Error 1025 when creating Override VI for an already open parent class
547120 Incorrect VI dataflow when using an Error Wire with a parallelized For Loop
548355 Running a VI using the 'DataSocket Select URL.VI', navigating to a remote machine on the network, and browsing to the DataSocket Server Item can cause LabVIEW to crash
549429 DAbort 0x34E86741 ConvertNum called with non-numeric
554381 Sort items in the Choose Implementation class dialog alphabetically
555317 In rare cases Waveform Charts can show different sets of data when pulling from the same source
555758 Using the 'Unflatten From String Function' to unflatten an "invalid" string within LabVIEW x64 can cause the computer to become unresponsive
555788 Using "Fast File Format" to build an executable could result in error 2208 in some cases
555868 Using the Tree Control 'Drag Starting? Event' allows you to Delete the reference to the item you are dragging and can result in a LabVIEW crash
561615 In specific cases, building a LabVIEW executable with shared variables causes Error 1003 during the build
564219 Sometimes if RFmx continuously modifies the loading state of the UI thread, a race condition can occur and potentially cause a crash
564417 Special characters in Control names can cause Unit Tests to not recognize cluster elements in some cases
567369 LabVIEW crashes when getting the properties of a class containing a member VI with certain connector pane configurations.
569362 In cases of extreme load on a TCP server, LabVIEW can miss new connection notifications, causing a timeout
569793 Rare persistent Error 56 at TCP Read
570547 Bluetooth Read, Write, and Close primitives have TCP icon
571421 In certain cases, dynamically calling a VI containing a SubVI can cause a memory leak. The size of the memory leak scales with the size of the SubVI and its dependencies
571556 Showing Visible Items on Waveform Chart probe does not resize chart in the probe window
571713 Scripting a Value Change event for an IVI Logical Name control crashes LabVIEW
571935 Closing a project library containing a class with unsaved changes does not prompt for save
573160 The German, Chinese, and Japanese LabVIEW registry files have the incorrect LabVIEW version
573195 If applications called from SystemExec.vi crash, it can affect LabVIEW TCP communication
573539 In some cases, DNS name resolution in LabVIEW can block other TCP calls
574048 Error 8 when trying to create an actor under an unsaved library
575278 Error 1019 when creating a message, if the actor contains a never-before-saved method
578899 LabVIEW 64-bit Development Environment has the potential to crash while running certain RFmx examples
580210 Remote debugging sessions that involve packed project libraries can stop unexpectedly
580212 Remote debugging VIs that were built without front panels can close the session unexpectedly
581199 Unflatten From String throws error 74, does not update indicators
585229 LabVIEW packed project library can cause calling executable to break when rebuilt

Accessing the Help

Refer to the LabVIEW Help, accessible by selecting Help»LabVIEW Help from LabVIEW, for information about LabVIEW 2016.

Additions to the LabVIEW Help

The following list contains additional changes to LabVIEW that are not included in the LabVIEW Help, the LabVIEW Upgrade Notes, or both:

Finding Examples

Select Help»Find Examples from LabVIEW to launch the NI Example Finder. You can modify an example VI to fit an application, or you can copy and paste from one or more examples into a VI that you create.

Automating the Installation of NI Products

You can automate the installation of most NI products using command-line arguments to suppress some or all of the installer user interface and dialog boxes. However, starting with the August 2012 releases (products using NI Installers version 3.1 or later), you may need to perform additional steps before or during a silent installation of NI software.

If the NI product you are installing uses Microsoft .NET 4.0, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.0 separately before you install NI software.

For more information about automating the installation of NI products, refer to the following KnowledgeBase articles:

Using NI Software with Microsoft Windows 10

Microsoft Windows 10 is the latest version of the Windows operating system and features significant changes compared to previous versions. Windows 10 introduces several new capabilities and also combines features from both Windows 7 and Windows 8. For more information about NI support for Windows 10, visit ni.com/windows10.

Using NI Software with Microsoft Windows 8.1

When you install NI software on Microsoft Windows 8.1, you will notice a few additional tiles in the Apps view, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (NI MAX), and NI Launcher. For more information about NI support for Windows 8.1, visit ni.com/windows8.

LabVIEW 2016 Drops Support for Microsoft Windows 7 RTM, Windows Vista, Windows XP, and Windows Server 2003

With this release, LabVIEW drops support for Microsoft Windows 7 RTM (with no service pack), Windows Vista, Windows XP, and Windows Server 2003. LabVIEW 2016 and later will not install or run on Windows 7 RTM (with no service pack), Windows Vista, Windows XP, or Windows Server 2003. For detailed information about NI application software product life cycles, visit ni.com/info and enter one of the following Info Codes:

Product Info Code
LabVIEWlifecycle
LabWindows™/CVI™cvi_lifecycle
Measurement Studiomstudiolifecycle
TestStandtslcp
DIAdemddlcp
SignalExpressselcp
VeriStandnivslifecycle

Legal Information

Copyright

© 2004–2016 National Instruments. All rights reserved.

Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.

NI respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.

End-User License Agreements and Third-Party Legal Notices

You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:

U.S. Government Restricted Rights

If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.

IVI Foundation Copyright Notice

Content from the IVI specifications reproduced with permission from the IVI Foundation.

The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.

Trademarks

Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on NI trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.

Patents

For patents covering the NI products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the NI Patent Notice at ni.com/patents.

374715F-01