PC-DYNA is the original name used to describe LS-DYNA for Microsoft Windows. On this page you will find directions to download, install, and license LS-DYNA for Microsoft Windows. Comparable web pages for installing LS-DYNA do not exist for versions of LS-DYNA before 971 R5.0. If you want to download previous versions, then visit the LSTC FTP site
We recommended that you download the complete installation package for PC-DYNA. This package includes a Graphical User Interface tool for managing various LSTC software components. Releases of full installation packages lag behind new versions of LS-DYNA executables. You may download minor releases of LS-DYNA as they come available, and manually add them to the current Windows installation Programs directory.
NOTE: MPP-DYNA executables are not included with the LS-DYNA manager. These must be obtained separately. MPP-DYNA executables cannot be run directly from the LS-DYNA Manager, but instead must be started using tools supplied by the various MPI Software vendors.
The current 32- and 64-bit Windows full installation packages are| LS-DYNA for 32-bit Microsoft Windows Complete Installation |
LS-DYNA for 64-bit Microsoft Windows Complete Installation |
|---|---|
| ls971_R5.1.1_win32_p-install.exe | ls971_R5.1.1_winx64_p-install.exe |
TO INSTALL LS-DYNA: Download the appropriate full installation package to your machine. Right click on the file in order to run as Administrator. The installer package is a self-contained InstallShield application.
*** NOTE *** We highly recommend that you choose an installation path which contains no spaces in the name.
*** NOTE *** On rare occasion, the installer may hang while unpacking the archive. If this happens, then look for a pop-up window that may be hidden by other windows. If no such pop-up appears, then a reboot will fix the problem.
Once you have installed the complete LS-DYNA program, then you may download the latest versions of SMP LS-DYNA executables for your machine, and add them to your installation. SMP LS-DYNA executables can be started from within the LS-DYNA Manager, provided that the new programs are properly located within the LS-DYNA Manager Installation.
You may also download the latest MPP-DYNA programs. However, it is not necessary to locate MPP-DYNA programs within the LS-DYNA Manager Installation because MPP-DYNA programs cannot be started directly from the LS-DYNA Manager. MPP-DYNA programs require the presence of MPI software, and MPI-enabled software must be started using MPI software vendor-supplied tools.
In order to add new executables to your current DYNA Manager installation, follow the directions below.Locate and open the folder containing the LS-DYNA program files. One way to do this is to first locate the LS-DYNA Manager in the Windows Program menu.
Start->All Programs->LS-DYNA. Right click on LS-DYNA Manager and select the Open File Location from the Windows Menu.
Browse to the Programs folder, leaving this file browser window open so that you can copy files to this location.
NOTE: If the Open file location option does not appear on your system menu, then select the Properties option instead. Then press the Open file location button in the Windows system dialog which appears.
Download one of the zip archives, and open it. Select all of the files in the archive, and copy them into the file browser window opened in step (1).
You may see some warnings about overwriting existing files, especially lstc_client.exe You should only replace the LSTC License Client lstc_client.exe with the newest available version. The newest version of lstc_client.exe supports all previous versions of LS-DYNA.
In order to run the new solver using the DYNA Manager, open the Solver->Select LS-DYNA Solver menu option. You should select the new solver file that you just placed in the Program folder.
| HARDWARE | OS | SNG/DBL | ARCHIVE |
|---|---|---|---|
| INTEL or AMD | Microsoft Windows 32 | single | ls971_s_R6.0.0_win32_p.zip |
| INTEL or AMD | Microsoft Windows 32 | single MADYMO |
ls971_s_R6.0.0_win32_madymo73.zip |
| INTEL or AMD | Microsoft Windows 32 | double | ls971_s_R6.0.0_win32_p.zip |
| INTEL or AMD | Microsoft Windows x64 | single | ls971_s_R6.0.0_winx64_p.zip |
| INTEL or AMD | Microsoft Windows x64 | single MADYMO |
ls971_s_R6.0.0_winx64_madymo73.zip |
| INTEL or AMD | Microsoft Windows x64 | double | ls971_d_R6.0.0_winx64_p.zip |
| HARDWARE | OS | SNG/DBL | ARCHIVE |
|---|---|---|---|
| INTEL or AMD | Microsoft Windows 32 | single | ls971_s_R5.1.1_win32_p.zip |
| INTEL or AMD | Microsoft Windows 32 | single MADYMO |
ls971_s_R5.1.1_win32_madymo73.zip |
| INTEL or AMD | Microsoft Windows 32 | double | ls971_d_R5.1.1_win32_p.zip |
| INTEL or AMD | Microsoft Windows x64 | single | ls971_s_R5.1.1_winx64_p.zip |
| INTEL or AMD | Microsoft Windows x64 | single MADYMO |
ls971_s_R5.1.1_winx64_madymo73.zip |
| INTEL or AMD | Microsoft Windows x64 | double | ls971_d_R5.1.1_winx64_p.zip |
| HARDWARE | OS | SNG/DBL | ARCHIVE |
|---|---|---|---|
| INTEL or AMD | Microsoft Windows 32 | single | ls971_s_R5.1_win32_p.zip |
| INTEL or AMD | Microsoft Windows 32 | double | ls971_d_R5.1_win32_p.zip |
| INTEL or AMD | Microsoft Windows x64 | single | ls971_s_R5.1_winx64_p.zip |
| INTEL or AMD | Microsoft Windows x64 | double | ls971_d_R5.1_winx64_p.zip |
| HARDWARE | OS | SNG/DBL | ARCHIVE |
|---|---|---|---|
| INTEL or AMD | Microsoft Windows 32 | single | ls971_s_R5.0_win32_p.zip |
| INTEL or AMD | Microsoft Windows 32 | double | ls971_d_R5.0_win32_p.zip |
| INTEL or AMD | Microsoft Windows x64 | single | ls971_s_R5.0_winx64_p.zip |
| INTEL or AMD | Microsoft Windows x64 | double | ls971_d_R5.0_winx64_p.zip |
| HARDWARE | OS | MPI | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| INTEL/AMD | Win32 | MPICH 1.2.5 | single | mpp971_s_R6.0.0_Intelsse_win32_mpich125.zip |
| INTEL/AMD | Win32 | MPICH 1.2.5 | double | mpp971_d_R6.0.0_Intelsse_win32_mpich125.zip |
| INTEL/AMD | Win64 | ANL MPI | single | mpp971_s_R6.0.0_winx64_anlmpi.zip |
| INTEL/AMD | Win64 | ANL MPI | double | mpp971_d_R6.0.0_winx64_anlmpi.zip |
| INTEL/AMD | Win64 | HP MPI | single | mpp971_s_R6.0.0_winx64_hpmpi.zip |
| INTEL/AMD | Win64 | HP MPI | double | mpp971_d_R6.0.0_winx64_hpmpi.zip |
| INTEL/AMD | Win64 | INTEL MPI | single | mpp971_s_R6.0.0_winx64_impi.zip |
| INTEL/AMD | Win64 | INTEL MPI | double | mpp971_d_R6.0.0_winx64_impi.zip |
| INTEL/AMD | Win64 | MSMPI | single | mpp971_s_R6.0.0_winx64_msmpi.zip |
| INTEL/AMD | Win64 | MSMPI | double | mpp971_d_R6.0.0_winx64_msmpi.zip |
| INTEL/AMD | Win64 | PLATFORM MPI | single | mpp971_s_R6.0.0_winx64_pmpi.zip |
| INTEL/AMD | Win64 | PLATFORM MPI | double | mpp971_d_R6.0.0_winx64_pmpi.zip |
| HARDWARE | OS | MPI | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| INTEL/AMD | Win32 | MPICH 1.2.5 | single | mpp971_s_R5.1.1_Intelsse_win32_mpich125.zip |
| INTEL/AMD | Win32 | MPICH 1.2.5 | double | mpp971_d_R5.1.1_Intelsse_win32_mpich125.zip |
| INTEL/AMD | Win64 | ANL MPI | single | mpp971_s_R5.1.1_winx64_anlmpi.zip |
| INTEL/AMD | Win64 | ANL MPI | double | mpp971_d_R5.1.1_winx64_anlmpi.zip |
| INTEL/AMD | Win64 | HP MPI | single | mpp971_s_R5.1.1_winx64_hpmpi.zip |
| INTEL/AMD | Win64 | HP MPI | double | mpp971_d_R5.1.1_winx64_hpmpi.zip |
| INTEL/AMD | Win64 | INTEL MPI | single | mpp971_s_R5.1.1_winx64_impi.zip |
| INTEL/AMD | Win64 | INTEL MPI | double | mpp971_d_R5.1.1_winx64_impi.zip |
| INTEL/AMD | Win64 | MSMPI | single | mpp971_s_R5.1.1_winx64_msmpi.zip |
| INTEL/AMD | Win64 | MSMPI | double | mpp971_d_R5.1.1_winx64_msmpi.zip |
| HARDWARE | OS | MPI | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| INTEL/AMD | Win32 | ANL MPI | single | mpp971_s_R5.1_Intelsse_win32_anlmpi2.zip |
| INTEL/AMD | Win32 | ANL MPI | double | mpp971_d_R5.1_Intelsse_win32_anlmpi2.zip |
| INTEL/AMD | Win32 | MPICH 1.2.5 | single | mpp971_s_R5.1_Intelsse_win32_mpich125.zip |
| INTEL/AMD | Win32 | MPICH 1.2.5 | double | mpp971_d_R5.1_Intelsse_win32_mpich125.zip |
| INTEL/AMD | Win64 | ANL MPI | single | mpp971_s_R5.1_winx64_anlmpi.zip |
| INTEL/AMD | Win64 | ANL MPI | double | mpp971_d_R5.1_winx64_anlmpi.zip |
| INTEL/AMD | Win64 | HP MPI | single | mpp971_s_R5.1_winx64_hpmpi.zip |
| INTEL/AMD | Win64 | HP MPI | double | mpp971_d_R5.1_winx64_hpmpi.zip |
| INTEL/AMD | Win64 | INTEL MPI | single | mpp971_s_R5.1_winx64_impi.zip |
| INTEL/AMD | Win64 | INTEL MPI | double | mpp971_d_R5.1_winx64_impi.zip |
| INTEL/AMD | Win64 | MSMPI | single | mpp971_s_R5.1_winx64_msmpi.zip |
| INTEL/AMD | Win64 | MSMPI | double | mpp971_d_R5.1_winx64_msmpi.zip |
| HARDWARE | OS | MPI | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| INTEL/AMD | WIN32 | MPICH 1.2.5 | single | mpp971_s_R5.0_Intelsse_win32_mpich125.zip |
| INTEL/AMD | WIN32 | MPICH 1.2.5 | double | mpp971_d_R5.0_Intelsse_win32_mpich125.zip |
| INTEL/AMD | WIN32 | ANLMPI 2 | single | mpp971_s_R5.0_Intelsse_win32_anlmpi2.zip |
| INTEL/AMD | WIN32 | ANLMPI 2 | double | mpp971_d_R5.0_Intelsse_win32_anlmpi2.zip |
| INTEL/AMD | WIN64 | HPMPI | single | mpp971_s_R5.0_winx64_hpmpi.zip |
| INTEL/AMD | WIN64 | HPMPI | double | mpp971_d_R5.0_winx64_hpmpi.zip |
| INTEL/AMD | WIN64 | INTELMPI | single | mpp971_s_R5.0_winx64_impi.zip |
| INTEL/AMD | WIN64 | INTELMPI | double | mpp971_d_R5.0_winx64_impi.zip |
| INTEL/AMD | WIN64 | ANLMPI | single | mpp971_s_R5.0_winx64_anlmpi.zip |
| INTEL/AMD | WIN64 | ANLMPI | double | mpp971_d_R5.0_winx64_anlmpi.zip |
| INTEL/AMD | WIN64 | MSMPI | single | mpp971_s_R5.0_winx64_msmpi.zip |
| INTEL/AMD | WIN64 | MSMPI | double | mpp971_d_R5.0_winx64_msmpi.zip |
Users have the option of installing a separate LSTC License Manager, or using the LSTC License Manager included with the full installation of LS-DYNA for Microsoft Windows.
If users on other machines will access the network license, then it is probably best to create a separate installation of the LSTC License Manager software; that way the network license is not affected when upgrading LS-DYNA at a later time. If this is an installation for users on one machine only, then it is recommended that one install the license using the LS-DYNA Manager instead.
The choice of license installation affects how one installs an initial license and upgrades that license. The procedure to Upgrade the LSTC License Manager Software is the same, regardless.
If you install a separate LSTC License Manager ...
(These link to another page.)
In order to install a network license using the LS-DYNA Manager program, you must complete a license request form and submit it to LSTC. To do this, open the LS-DYNA Manager program and select License Manager->License Manager Registration. A form will appear which you must complete:
Upon completion, select the Save log file option shown above. Save the file LSTC_SERVER_INFO to a convenient location such as the Desktop, and attach it to an email to "keys@lstc.com". Be sure to include any relevant information concerning your license request such as the number of cores, etc.
LSTC will send the license file "server_data" as an attachment to the return email. Save this attachment to a convenient location such as the Desktop.
In order to install this license, you must restart the LS-DYNA Manager as Administrator. To do this, browse All Programs for the LS-DYNA group. Open the LS-DYNA program group, and right-click on the LS-DYNA Manager program. Select the Run as administrator option from the menu.
Import the new "server_data" license file into the LS-DYNA Manager program. Do this by selecting the menu option License Manager->Import License On Local Machine. Locate and select the "server_data" license file.
The LSTC License Manager service must be installed into the Windows Service Control Manager (SCM). To do this, select the option License Manager->Install LSTC License Manager as Service.
The LSTC License Manager service must be started manually after it is first installed. To do this, select the menu option License Manager->Start LSTC License Manager. Windows will start this service automatically whenever the machine is restarted.
To verify that the server is now running, select the menu option License Manager->View Local Machine LSTC License Manager Status. You should see a pop-up appear indicating that the LSTC License Manager is running. If you do not, then contact LSTC support.
Select the menu option Env Variables->Set LS-DYNA Env Variables. Set the License Type to network. Specify the Network License Manager as the host name or IP address of the machine where the LSTC License Manager is running. If the server is running on the local machine, then specify "localhost".
Do not run the LS-DYNA Manager as Administrator except to install a license. Otherwise you may create files that ordinary users cannot delete or modify.
If you receive an upgraded "server_data" license file from LSTC, then you should save the file to a convenient location where you can browse for it later. The instructions below assume you have previously installed the license server using the LS-DYNA Manager.
In order to upgrade a license, you must restart the LS-DYNA Manager as Administrator. To do this, browse All Programs for the LS-DYNA group. Open the LS-DYNA program group, and right-click on the LS-DYNA Manager program. Select the Run as administrator option from the menu.
Import the new "server_data" license file into the LS-DYNA Manager program. Do this by selecting the menu option License Manager->Import License On Local Machine. Locate and select the "server_data" license file.
* Stop the server:
License Manager->Stop LSTC License Manager
* Restart the server:
License Manager->Start LSTC License Manager
The server will re-read the license file when it is restarted.
To verify that the server is now running, select the menu option License Manager->View Local Machine LSTC License Manager Status. You should see a pop-up appear indicating that the LSTC License Manager is running. If you do not, then contact LSTC support.
Do not run the LS-DYNA Manager as Administrator except to install a license. Otherwise you may create files that ordinary users cannot delete or modify.
All download links in this section point to the "objects" section of the LSTC FTP site. You must obtain the username and password for this section from an LSTC representative. A useful file to consult for information about User-Defined Material Models is the User-Defined Materials FAQ. Each archive referenced below also contains a readme.txt file with more information about compilation and compilers.
To invoke a user-defined material, you must:
Creating a custom executable requires you to obtain the same compilers used by LSTC to build the supplied objects. There are two compilers required for Windows Versions of LS-DYNA: Microsoft Visual C++ and a FORTRAN compiler. The specific versions of these compilers varies depending on the version of objects that you use. LSTC does not support alternative versions of compilers.
WARNING: Install Microsoft Visual C++ before installing the Intel Fortran compiler.
| HARDWARE | OS | MPI/SMP | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| Intel/AMD | Win32 | SMP | single | ls971_s_R6.0.0_win32_p_lib.zip |
| Intel/AMD | Win32 | SMP | double | ls971_d_R6.0.0_win32_p_lib.zip |
| Intel/AMD | Win64 | SMP | single | ls971_s_R6.0.0_winx64_p_lib.zip |
| Intel/AMD | Win64 | SMP | double | ls971_d_R6.0.0_winx64_p_lib.zip |
| Intel/AMD | Win64 | ANL MPI | single | mpp971_s_R6.0.0_anlmpi_lib.zip |
| Intel/AMD | Win64 | ANL MPI | single | mpp971_d_R6.0.0_anlmpi_lib.zip |
| Intel/AMD | Win64 | HP MPI | single | mpp971_s_R6.0.0_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | HP MPI | double | mpp971_d_R6.0.0_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | single | mpp971_s_R6.0.0_msmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | double | mpp971_d_R6.0.0_msmpi_lib.zip |
| Intel/AMD | Win64 | PLATFORM MPI | single | mpp971_s_R6.0.0_winx64_pmpi_lib.zip |
| Intel/AMD | Win64 | PLATFORM MPI | double | mpp971_d_R6.0.0_winx64_pmpi_lib.zip |
| HARDWARE | OS | MPI/SMP | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| Intel/AMD | Win32 | SMP | single | ls971_s_R5.1.1_win32_p_lib.zip |
| Intel/AMD | Win32 | SMP | double | ls971_d_R5.1.1_win32_p_lib.zip |
| Intel/AMD | Win32 | MPICH 1.2.5 | single | mpp971_s_R5.1.1_win32_anlmpi1_lib.zip |
| Intel/AMD | Win32 | MPICH 1.2.5 | double | mpp971_d_R5.1.1_win32_anlmpi1_lib.zip |
| Intel/AMD | Win64 | SMP | single | ls971_s_R5.1.1_winx64_p_lib.zip |
| Intel/AMD | Win64 | SMP | double | ls971_d_R5.1.1_winx64_p_lib.zip |
| Intel/AMD | Win64 | HP MPI | single | mpp971_s_R5.1.1_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | HP MPI | double | mpp971_d_R5.1.1_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | single | mpp971_s_R5.1.1_winx64_msmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | double | mpp971_d_R5.1.1_winx64_msmpi_lib.zip |
| HARDWARE | OS | MPI/SMP | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| Intel/AMD | Win32 | SMP | single | ls971_s_R5.1_win32_p_lib.zip |
| Intel/AMD | Win32 | SMP | double | ls971_d_R5.1_win32_p_lib.zip |
| Intel/AMD | Win32 | MPICH 1.2.5 | single | mpp971_s_R5.1_win32_anlmpi1_lib.zip |
| Intel/AMD | Win32 | MPICH 1.2.5 | double | mpp971_d_R5.1_win32_anlmpi1_lib.zip |
| Intel/AMD | Win64 | SMP | single | ls971_s_R5.1_winx64_p_lib.zip |
| Intel/AMD | Win64 | SMP | double | ls971_d_R5.1_winx64_p_lib.zip |
| Intel/AMD | Win64 | ANL MPI | single | mpp971_s_R5.1_winx64_anlmpi_lib.zip |
| Intel/AMD | Win64 | ANL MPI | double | mpp971_d_R5.1_winx64_anlmpi_lib.zip |
| Intel/AMD | Win64 | HP MPI | single | mpp971_s_R5.1_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | HP MPI | double | mpp971_d_R5.1_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | single | mpp971_s_R5.1_winx64_msmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | double | mpp971_d_R5.1_winx64_msmpi_lib.zip |
| HARDWARE | OS | MPI/SMP | SNG/DBL | ARCHIVE |
|---|---|---|---|---|
| Intel/AMD | Win32 | SMP | single | ls971_s_R5.0_win32_p_lib.zip |
| Intel/AMD | Win32 | SMP | double | ls971_d_R5.0_win32_p_lib.zip |
| Intel/AMD | Win32 | MPICH 1.2.5 | single | mpp971_s_R5.0_Intelsse_win32_mpich125_lib.zip |
| Intel/AMD | Win32 | MPICH 1.2.5 | double | mpp971_d_R5.0_Intelsse_win32_mpich125_lib.zip |
| Intel/AMD | Win64 | SMP | single | ls971_s_R5.0_winx64_p_lib.zip |
| Intel/AMD | Win64 | SMP | double | ls971_d_R5.0_winx64_p_lib.zip |
| Intel/AMD | Win64 | ANL MPI | single | mpp971_s_R5.0_winx64_anlmpi_lib.zip |
| Intel/AMD | Win64 | ANL MPI | double | mpp971_d_R5.0_winx64_anlmpi_lib.zip |
| Intel/AMD | Win64 | HP MPI | single | mpp971_s_R5.0_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | HP MPI | double | mpp971_d_R5.0_winx64_hpmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | single | mpp971_s_R5.0_winx64_msmpi_lib.zip |
| Intel/AMD | Win64 | MSMPI | double | mpp971_d_R5.0_winx64_msmpi_lib.zip |