LabVIEW 2012 Readme for Windows

Version 12.0.0

June 2012

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

Refer to the National Instruments website for the latest information about LabVIEW 2012.

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

System Requirements
Installation Instructions
Known Issues
LabVIEW 2012 (64-bit)
Additions to the LabVIEW Help
Bug Fixes
Automating the Installation of NI Products
Important Information

System Requirements

WindowsRun-Time EngineDevelopment Environment
ProcessorPentium III/Celeron 866 MHz or equivalentPentium 4M or equivalent
Screen Resolution1024 x 768 Pixels1024 x 768 Pixels
Operating SystemWindows 7/Vista (32-bit and 64-bit)
Windows XP SP3 (32-bit)
Windows Server 2003 R2 (32-bit)
Windows Server 2008 R2 (64-bit)
Windows 7/Vista (32-bit and 64-bit)
Windows XP SP3 (32-bit)
Windows Server 2003 R2 (32-bit)
Windows Server 2008 R2 (64-bit)
Disk Space353 MB3.67 GB (includes default drivers from the NI Device Drivers DVD)
Color PaletteN/ALabVIEW and the LabVIEW Help contain 16-bit color graphics. LabVIEW requires a minimum color palette setting of 16-bit color.
Temporary Files DirectoryN/ALabVIEW uses a directory for storing temporary files. National Instruments recommends that you have several megabytes of disk space available for this temporary directory.
Adobe ReaderN/AYou must have Adobe Reader installed to search PDF versions of all LabVIEW manuals.
Note  The following list describes restrictions for using LabVIEW on Windows:
  • LabVIEW does not support Windows 2000/NT/Me/98/95 or Windows XP x64.
  • 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:

  • LabVIEW Installation Guide—Includes information about installing LabVIEW, modules and toolkits, drivers, and hardware.
  • LabVIEW Upgrade Notes—Includes information about protecting existing VIs and projects before you install a new version of LabVIEW, as well as upgrade and compatibility issues and a complete list of new features in LabVIEW 2012.

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

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.

Known Issues

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 2012.

LabVIEW 2012 (64-bit)

When run on Windows (64-bit), LabVIEW 2012 (64-bit) provides access to more memory than a 32-bit operating system or a 32-bit application can provide. LabVIEW 2012 (64-bit) includes nearly all of the development environment features of LabVIEW 2012 (32-bit).

Refer to the National Instruments website for information about obtaining a copy of LabVIEW 2012 (64-bit).

Supported Hardware

LabVIEW 2012 (64-bit) supports many hardware devices. Refer to the National Instruments website for information about drivers compatible with LabVIEW 2012 (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 2012 (64-bit).

Supported Modules

LabVIEW 2012 (64-bit) supports only the NI Vision Development Module. Refer to the Vision Development Module documentation for more information. No additional modules support LabVIEW 2012 (64-bit).

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:

  • Because LabVIEW 2012 may apply different compiler optimizations on different machines, you may need to perform additional steps to guarantee that a built application contains the same binary contents when built on different machines. Refer to the National Instruments website for more information about reproducing builds in LabVIEW 2012.

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed in LabVIEW 2012. 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 the issue has been fixed.

ID Fixed Issue
100634 .NET Calendar Control is not sized properly
124146 Re-initialize to default not working on Picture Control
156274 Changes to Type Def Reference to a Tab Control doesn't update other instances
167056 Wiring cluster of fixed point values to waveform chart causes a broken arrow
182407 Remote Debugging crashes with an application that uses MathScript
185059 Member VIs of a class that is a member of a project library have a red X on them in the palettes
186525 'visarc' file included in source distribution even when excluding vi.lib
187412 Custom RTM will incorrectly link to the source location when built into an executable
190778 Huge array causes long save time and run time on LabVIEW 64-bit
190887 XY Plot Legend Shifts Right On Front Panel When Repeatedly Redrawn
209168 VI Server method "Application:Library.Open" returns wrong library if library is unsaved
214475 Cannot zoom in render window of 3D graph
219940 Cannot use Sort 1D Array with an array of clusters containing LabVIEW Classes
236868 Pane Size Event Does not generate final event as documented
258465 Pre-Build Action VI Not brought to front when Source Distribution is Built from Properties Window
280810 Giving Simulation VI class terminals that are dynamic dispatch results in LabVIEW compiler fault
283709 Logos Sockets should broadcast on all available NICs
285210 Read from Measurement File Express VI can read incorrect data
294478 Applications built from VIs that include Damemoji AKA stressed characters in the file name do not work.
297201 Time Critical priority VI shouldn't compile if it contains a Timed Loop
298656 Import Web Services does not support external type definition (external schema)
299162 Saving for previous with missing DLL crashes LabVIEW
300592 LabVIEW built executable with network streams won't exit process
300864 Unexpected broken wires when graphing coerced CDB arrays
302673 Programmatically changing y-axis parameters on a waveform chart or graph causes the plot to shrink horizontally.
302888 Sine Pattern VI behaves incorrectly for certain inputs
302922 Unexpected inputs can permanently corrupt a 3D graph instance.
310813 EXE/RTEXE and PPL have load time issues when statechart is embedded inside
311293 Not A Reference does not work with FTP References
311294 FTP Close will not unregister a session if server is unresponsive
311617 Undoing block diagram cleanup in VI with Control & Simulation Loop and subsystem crashes LabVIEW
312531 When class specific VIs are used in a project, the VI Metrics Tool does not include them in the VIs it analyzes.
313044 Long Delays when editing VIs with LabVIEW object-oriented programming property nodes
313186 Long lines in 2D Picture are drawn to the wrong end points.
313610 NI LabVIEW Report Generation Toolkit for Microsoft Office 2011: broken Excel Active X methods
315798 TCP Write Stream generates add extra characters to TDMS files during FTP transfer
316099 Project load time can be affected by large .lvlps file
317005 Several Express VIs become broken when placed on Block Diagram after Spectral Measurement VI.
318065 "Find" options within context menu for implicitly linked property/invoke nodes missing when original control is a typedef
318415 Error reading LVM file "Incorrect file type"
321650 LabVIEW crashes when changing event registration refnum constant to control.
323425 Build failures caused by inlined VIs in a PPL
325201 Front Panel Indicators to Fail to Update Correctly When EXE is Loaded in Bad State
327431 Import WebService Tool doesn't work for HTTPS protocol
327926 Calling Variable Property Node in a Loop leaks memory
329925 Continuous Sound example unresponsive after pause execution
331216 Rare Crash on VI Compile
332247 To Long Integer produces incorrect result for a SGL input of 2^31
333279 Calling the System Exec VI after calling the Pipe VI in LabVIEW for Linux will Hang LabVIEW.
333651 Converting a PSP variable to a variant, then a string and back, causes the conversion back to PSP variable to fail
335523 Creating a reference for a control that is a typedef is not retaining the typedef properties of the refnum type
338840 Shortcut Menu Activation Interferes with Independent Autoscale Y Settings in Waveform Chart or Graph with Multiple Plots
344940 Copying data in custom probe can crash LabVIEW
346352 "Explore" button on Application Builder build progress dialog doesn't close the dialog
346819 Incorrect result when calling a non-reentrant VI by a pre-allocated VI
347785 General Linear Fit (Bi-Square) VI does not return weight out

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, refer to the following KnowledgeBase articles:

Important Information


© 2004–2012 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:

  • Notices are located in the <National Instruments>\_Legal Information and <National Instruments> directories.
  • EULAs are located in the <National Instruments>\Shared\MDF\Legal\license directory.
  • Review <National Instruments>\_Legal Information.txt for information on including legal information in installers built with NI products.


LabVIEW, National Instruments, NI,, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at for other 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