This file contains important information about LabVIEW 2015 for Windows, including system requirements, installation instructions, known issues, and a partial list of bugs fixed for LabVIEW 2015.
Refer to the National Instruments website for the latest information about LabVIEW 2015.
Refer to the labview\readme directory for readme files about LabVIEW add-ons, such as modules and toolkits.
|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 8.1/8/7/Vista (32-bit and 64-bit) |
Windows XP SP3 (32-bit)
Windows Server 2012 R2 (64-bit)
Windows Server 2008 R2 (64-bit)
Windows Server 2003 R2 (32-bit)
| Windows 8.1/8/7/Vista (32-bit and 64-bit) |
Windows XP SP3 (32-bit)
Windows Server 2012 R2 (64-bit)
Windows Server 2008 R2 (64-bit)
Windows Server 2003 R2 (32-bit)
|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. National Instruments 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.|
|Note The following list describes restrictions for using LabVIEW on Windows: |
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:
Note If you purchased this product with an NI Software Suite or NI Product Bundle, use the installation media that shipped with your purchase to install this product.
Visit ni.com/security to view and subscribe to receive security notifications about National Instruments products. Visit ni.com/critical-updates for information about critical updates from National Instruments.
You can access the software and documentation known issues list online. Refer to the National Instruments website for an up-to-date list of known issues in LabVIEW 2015.
When run on Windows (64-bit), LabVIEW 2015 (64-bit) provides access to more memory than a 32-bit operating system or a 32-bit application can provide. LabVIEW 2015 (64-bit) includes nearly all of the development environment features of LabVIEW 2015 (32-bit).
Refer to the National Instruments website for information about obtaining a copy of LabVIEW 2015 (64-bit).
LabVIEW 2015 (64-bit) supports many hardware devices. Refer to the National Instruments website for information about drivers compatible with LabVIEW 2015 (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 2015 (64-bit).
LabVIEW 2015 (64-bit) supports only the NI Vision Development Module. Refer to the Vision Development Module documentation for more information. No additional modules support LabVIEW 2015 (64-bit).
The following list contains additional changes to LabVIEW that are not included in the LabVIEW Help, the LabVIEW Upgrade Notes, or both:
The following items are the IDs and titles of a subset of issues fixed in LabVIEW 2015. 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.
|52263||Some operations on integer waveforms lose dt value|
|225616||Error 1172 (System.Reflection.AmbiguousMatchException) is returned when using the .NET invoke node to call a .NET method that also contains an additional generic version of the same method.|
|257275||Format Into String does not work with the %d format for numbers larger than I32|
|278730||Web Services ignore the No App switch on RT targets|
|315474||Feedback node with waveform data input, and greater than 2 iterations of delay, outputs an array of waveform|
|333388||Incorrect highlight execution order with LVOOP property node|
|348592||Select node causes buffer copy|
|361311||"Natural log of 1 + x" primitive incorrectly returns NaN for small positive values|
|372784||LabVIEW 2012 and later have added overhead to dynamic dispatch calls when compared to LabVIEW 2011|
|377653||There is inconsistent labeling on 'Constrained Nonlinear Curve Fit.vi' TRLM instance.|
|392232||Autopreallocate Arrays and Strings VI Property Can Crash LabVIEW when not in FPGA Context|
|392446||Installing LabVIEW on a Windows laptop decreases battery life|
|397550||LabVIEW can switch to different Front Panels or Block Diagrams when going between LabVIEW and other programs.|
|400736||Error -4403 returned from Write Palette.vi for Template VIs|
|401689||Constrained Non-Linear Optimization VI has Potential for Infinite Loop|
|408351||The Bookmark Manager window is not closed when 'Esc' key is pressed|
|413786||Help button does not work on Setup page of LabVIEW 64-bit Example Finder|
|413954||Slow VI compilation with complex VI|
|419089||Infinite loop in NI_Gmath.lvib:cno_isisubopt.vi under certain conditions|
|421739||Quick drop ctrl+r needs to wire the To More Specific/Generic side terminal instead of center terminal|
|424089||The advanced analysis Kummer Function returns 'NaN' instead of correct values for certain combinations of input parameters.|
|425562||Scan from String requires a space between modifiers when using SI notation|
|426157||VI invoke node Find CtrlWithKeyFocus don't work with typedefs|
|434426||Reading from same UDP port twice simultaneously crashes LV|
|435756||Web Services reset all resource VIs to their default parameters (GET as Terminal/XML) when multiple files are simultaneously added to project.|
|437915||When converting a Timestamp into a string with the Format into String primitive, certain incorrect format strings will cause the End of file encountered error.|
|438751||Renaming a group in a Mixed Signal Graph crashes LabVIEW once there is a plot containing data|
|441262||Call Library Function Nodes maximum error checking mode incorrectly reports memory corruption with CStrs and PStrs.|
|443165||Modifying the dependencies of a Packed Project Library (PPL) may cause LabVIEW to crash|
|444759||Default probes should fit to probe watch window pane|
|444851||Encapsulated PostScript (EPS) is not supported on Mac 64-bit|
|453489||Minimizing the lvlib group in VI hierarchy messes up the entire VI hierarchy.|
|458700||Equals? Function executes slowly on long strings|
|458724||Uninstalling myRIO Module 2013 causes LabVIEW Getting Started Screen to become unresponsive.|
|462624||Mouse wheel scrolling does not work on the Functions Palette.|
|463275||Using the same Application twice in installer causes unexpected behavior|
|463408||Log scale on a Graph does not use correct minimum with certain data|
|463760||Improved security of an authenticated session when used over an un-encrypted connection like http.|
|466635||Add new "Create Unique File" VI to vi.lib|
|468062||Path to URL.vi does not handle network path|
|468921||Auto-populating folders may not update their contents correctly|
|469070||In some cases, Fract/Exp String To Number VI does not convert the string correctly|
|469178||Sound Examples do not have volume control|
|469269||Error when VIPM quits LV -- svcloc_interface.cpp line 1702|
|471706||Cannot paste into destination name of installer properties in LabVIEW 2013|
|474004||Multiple LabVIEW windows do not group in RHEL.|
|474143||Copy functions returns a permission error (error code 8) occasionally when running in a loop|
|474764||A VI can hang at Occurrences if Allow Debugging is disabled|
|476028||MAX/NIER report: Null pointer dereference in LVBroker.dll!CniLVBroker::HandleVIClose(niLVReq & req, int (void) *)|
|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|
|477112||If you cancel the file dialog, it will never show again in Write to Measurement File Express VI.|
|477280||When using [VersionNumber], Application Builder post-build VIs do not get passed the proper path|
|477352||In the TDMS File Viewer VI, the menu becomes partially hidden after making the plot legend visible|
|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|
|477954||VI Analyzer throws error 1 when analyzing project with a Networked Computer under the Target Folder.|
|478485||Selecting a Polymorphic VI while loading a caller VI causes a crash due to missing polymorphic instances|
|478854||Source Distribution Target Directory not used, VIs placed in startup folder|
|478906||Conditional Double Probe does not handle NaN equality check|
|479161||Error 7 When Building Installer for EXE with Custom Destinations|
|480103||Using VirtualBench API through TestStand and the LVRTE causes crashes on exit|
|480480||Invoke Node shows the English shortname at the first drop in German LabVIEW|
|480921||Unable to delete and re-add a destination folder successfully in build specification of a LabVIEW Installer|
|484575||Issue writing to individual digital waveform channels in TDMS files|
|484662||LabVIEW Runtime installer should allow multiple versions in one distribution|
|484767||Bookmarks changed event does not return the path of the VI(s) in which the bookmarks changed|
|484940||Create Express VI tool throws Error 1099 when template VIs are marked as Source Only|
|485412||Make Ctr-W shortcut wire to inner terminals of tunnels|
|486475||LabVIEW crashes when adding a saved copy of an lvclass member to an lvlib|
|488710||Multicolumn Listbox Key Navigation is not consistent|
|489848||"Remove empty cases" option in case structure disappears when Subdiagram Label is visible.|
|490378||Report Generation Toolkit, headers.vi has a reference leak.|
|490606||Web Service installer fails to install on Win Server 2008 R2|
|491093||Application Web Server fails to run on VxWorks when root directory has too many files|
|491198||Any VI that has a VI Documentation greater than 8000 characters will cause the context help window to truncate the documentation.|
|491539||Unexpected behavior with Resample Waveforms (Single Shot).vi|
|496699||LabVIEW crashes when attempting to reinitialize unused plots in plot legend of waveform graph|
|497131||The WebDAV Put.vi when executed on a cRIO target can lead to a memory leak|
|497256||CoreAnimation thread warning when calling a LabVIEW-built Framework on Mac OS X 10.0|
|497516||Replacing a Waveform control with an Array(Silver) crashes LabVIEW with internal error in datamgr.cpp.|
|497755||Cannot reset the values of Build Specification Version in Set Build Specification Version VI to zero|
|499042||Incorrect Diagram Identifier reported by LV Compare tool when comparing case structures|
|500986||Error 1 generated in property node when remote debugging|
|501004||Performance improvements for 3D Plot VIs|
|501633||Variable Engine does not have a "Run-Time" product for deployment.|
|502081||Ctrl+shift+E (find in project) doesn't work for clone VIs.|
|502105||"New..." dialog only looks for VI templates in the LabVIEW directory, which is not writable on Linux systems|
|503234||The method "Synchronize in all Contexts" causes LabVIEW to crash.|
|505523||Diff and Merge do not work with Enable Hyperlinks|
|508525||Improve "Select a VI" experience with Quick Drop Replace and Insert|
|509097||LabVIEW crashes when sending an empty input array to the Preallocated Read from File VI|
|509204||Format Into String outputs an incorrect string when using Timestamp data and an order modifier|
|510063||LabVIEW does not exit properly after encountering a NIER exception|
|510881||LabVIEW Crash when saving Library containing Shared Variables with Class Object in Typedef.|
|510908||Application Builder slows when builds involve PPLs with controls in them|
|511588||Currently selected item in the Connector Pane selection menu is not outlined|
|511708||LabVIEW crashes when use "save method" to save the UDF VI if the MathScript RT Module and Control Design and Simulation Module are both installed.|
|511770||The Waveform Unbundle/Bundle node pair on InPlace Element Structures cannot be scripted|
|512153||Cursor in LabVIEW can disappear when switching between tools.|
|512294||Crash in search 1D array when run on VI with host interface node|
|512464||After making a change in Format Into String, the containing VI does not recompile automatically.|
|512761||The input XML containing "\n" hangs the LabVIEW storage VIs.|
|513188||Improved Bookmark Manager performance by adding additional caching.|
|513259||Substitute Actor VI does not transfer nested actors|
|513281||Improved error handling in AB_Engine_EXE_Call_Write_Icons.vi|
|513457||"Change to Array" menu option should not appear on tab controls or XControls.|
|513871||MAX/NIER report: Access violation in lvrt.dll!std::_Tree|
|513963||Classes containing NaN values compare incorrectly when using the Equals function|
|514518||LabVIEW 2014 crashes upon close while an RFmx example VI is running continuously from a LabVIEW Project context.|
|515054||Icon transparency of VIs is not maintained when building a Source Distribution|
|515086||Building VIs with certain recursive dependencies can cause a LabVIEW crash|
|515223||Advanced TDMS Write broken wire behavior is incorrect.|
|515763||The To Long Integer conversion bullet can crash when converting a float64 array to an int32 array if the start of the input data (just after the dimsize) is not 16 bytes aligned.|
|515779||Invoke node Append String returns error 1043 while display style set to backslash "\" codes|
|515884||LabVIEW crashes when using the Class Browser to select a class which contains an accessor available via property nodes|
|515920||Memory issues due to timestamp handling in the Data Storage VIs.|
|516057||LabVIEW Application Builder API Build (path).vi returns unclear error 1055 when Build Specification name or target name is incorrect|
|516217||The WebDAV Put.vi when executed on a cRIO target can lead to a memory leak|
|516227||UI Thread LabVIEW code cannot execute while a Time Stamp Control's 'Set Time and Date' window is visible.|
|516506||'Build All' error does not indicate which build specification failed.|
|516674||LabVIEW crashes when dragging a class member VI from the Class Browser onto an Untitled VI of a Library|
|516841||VeriStand crashes after manipulating a System Definition via the System Explorer|
|516905||Cannot get VI Path/Name for Type Definitions, Classes, or Global VIs if dependency is missing|
|517128||Error 1357 when building using two VIs with the same name and only capitalization differences.|
|517307||Mass Compile of VeriStand 2014 LabVIEW examples will crash LabVIEW|
|519216||LabVIEW crash when closing subVI Icon Editor that was opened from VI Hierarchy.|
|519533||IDFinder downloads the wrong version of VIs for Instrument drivers|
|519665||LV crashes when copying user event data while handling high priority user events|
|520343||Runtime popup menus appear on the Project properties dialog|
|521114||Property VIs of classes do not require that inputs/outputs match the class itself|
|521509||LabVIEW security update|
|524370||LabVIEW 2014 crashes on VI load if old error cluster controls are connected to case structures or conditional terminals|
Refer to the LabVIEW Help, accessible by selecting Help»LabVIEW Help from LabVIEW, for information about LabVIEW 2015.
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.
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:
When you install National Instruments software on Microsoft Windows 8.x, 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.
NI Launcher helps you find and launch installed NI products. It provides you with a method of finding NI products similar to the Start menu in previous versions of Microsoft Windows. To use NI Launcher, click the NI Launcher tile in the Apps view. NI Launcher launches the desktop and opens a menu containing a list of NI products. Click any NI product to launch it.
Note NI MAX does not appear as a desktop shortcut when installed on Microsoft Windows 8.x. You can launch NI MAX either from the Apps view or from within NI Launcher.
For convenience, you can pin your most-used NI applications, such as MAX, to either the Start screen or the Taskbar on the desktop, as necessary:
|Current Application||Icon Location||Pin to Action|
|Windows 8.x Desktop||Desktop Taskbar||Right-click application and select Pin to Taskbar|
|Windows 8.x Desktop||Start screen||Right-click application and select Pin to Start|
|Windows 8.x Start screen||Desktop Taskbar||Right-click application and select Pin to taskbar from the menu bar on the bottom of the screen|
If you want to find a particular application or related files, such as documentation files, from the Start screen, you can access all installed files from the Apps view. To get to the Apps view, right-click anywhere on the Start screen and select All apps (Windows 8.0) or click the down arrow on the bottom left of the screen (Windows 8.1).
For more information about NI support for Windows 8.x, visit ni.com/windows8.
LabVIEW will drop support for Microsoft Windows Vista, Windows XP, and Windows Server 2003 as of July 1, 2016. Versions of LabVIEW that ship after July 1, 2016 will not install or run on 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:
© 2004–2015 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.
National Instruments 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.
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.
For patents covering the National Instruments products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.