LabVIEW 64-Bit vs. 32-Bit Applications FAQ
Primary Software: LabVIEW Development Systems>>LabVIEW Full Development System
Primary Software Version: 1.0
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Development Systems>>LabVIEW Professional Development System
What are some of the frequently asked questions regarding LabVIEW 64-bit versus LabVIEW 32-bit?
Q. When did LabVIEW start supporting 64-bit operating systems?
A. LabVIEW 2009 is the first release with a 64-bit version.
Q. What platforms are LabVIEW 2009 (and later) 64-bit available for?
A. As of now, LabVIEW 64-bit is available for Windows only, starting with Windows Vista.
Q. Which LabVIEW modules and toolkits are available for LabVIEW 64-bit?
A. Please see this White Paper: Minimum Version Requirements for more information.
Q. Is LabVIEW 64-bit included on the LabVIEW Platform DVD?
A. The LabVIEW 64-bit versions are not available on the LabVIEW Platform DVD, but can be downloaded via the Drivers and Updates: LabVIEW 64-Bit section of our website.
Note: On ni.com, all customers have access to the latest version of 64-bit LabVIEW. Customers with our Standard Service Program (SSP) have access to previous versions of LabVIEW 64-bit.
Q. If I own a copy of LabVIEW 32-bit, do I need to purchase a separate license for LabVIEW 64-bit?
A. Every customer who purchases LabVIEW 2009 or later has a license for both the 32- and 64-bit versions.
Q. Can I run an executable built with LabVIEW 64-bit on a 32-bit PC?
A. No, you cannot run the LabVIEW 64-bit Development System, Run-Time Engine, or executables on a 32-bit PC.
Q. Can I run an executable built with LabVIEW 32-bit on a 64-bit PC?
A. Windows can run 32-bit executables on a 64-bit PC. Therefore, the LabVIEW 32-bit Development System, Run-Time Engine, and executables can be run on Windows 64-bit.
Q. Can I have both LabVIEW 32-bit and LabVIEW 64-bit installed on the same 64-bit machine?
Q. Can I build a 32-bit version of an executable from the LabVIEW 64-bit application builder?
A. No. Currently, there is not an option to create a 32-bit version of an executable from the LabVIEW 64-bit application builder.
Q. How much memory does LabVIEW have access to?
A. An application can request memory, but it is up to the operating system to accept, or deny, that request based on what is available (either physical or virtual). 32-bit LabVIEW on 32-bit Windows XP, by default, can only use up to 2 GB of address space. There is a 3 GB boot option that can allow applications on 32-bit XP to use up to 3 GB of address space. 32-bit LabVIEW running on 64-bit Vista or 64-bit Windows 7 can use up to 4 GB of address space. In any of these configurations you can still run into large buffers failing to allocate if enough contiguous memory is not available. 64-bit LabVIEW on an 64-bit OS supports as much RAM as the OS supports (theoretically, 16 exabytes). Currently, 64-bit Windows imposes a 16 TB limit.
Q. Can I run a VI written with LabVIEW 32-bit on a 64-bit PC and Vice Versa?
A. Yes, a VI that is written with LabVIEW 32-bit development system can be opened by a LabVIEW 64-bit development system and vice versa because the code is not compiled until the VI is run.
Q. What LabVIEW Add-Ons and Toolkits are supported on Windows 64-bit? What National Instruments Device Drivers are supported on Windows 64-bit?
A. Depending on your Operating System, please see:
Note: Device Drivers must be installed after LabVIEW. If device drivers are already installed, then performing a Repair from the Control Panel of the device driver can allow LabVIEW to recognize the drivers. Drivers are a separate installation from LabVIEW.
White Paper: Using National Instruments Products on 32-bit and 64-bit Windows
KnowledgeBase 2HDEH9DT: How Much Memory can LabVIEW 32-bit or 64-bit Use?
White Paper: National Instruments Product Compatibility for Microsoft Windows 7
White Paper: National Instruments Product Compatibility for Microsoft Windows 8
White Paper: National Instruments Product Compatibility for Microsoft Windows Vista
White Paper: NI LabVIEW Operating System Support
Report Date: 08/07/2009
Last Updated: 09/11/2014
Document ID: 506DUP3S