Resolving TIA Portal V15.1 'Needs License' Error on Windows 11

1. Problem Description

A clean installation of SIMATIC TIA Portal V15.1 from the original DVD media aborts immediately after the setup launcher starts. The dialog reported by Setup.exe reads: "The program you want to install needs a license". The same dialog is raised when launching the bundled Automation License Manager (ALM) installer (Setup_ALM.exe) from the same media, so no TIA Portal component - STEP 7, WinCC, PLCSIM, Startdrive, Sinutrain, S7-PCT, or ALM itself - can be registered.

The typical scenario is a workstation that previously hosted a TIA Portal V16 trial license which has been removed. The user possesses a valid V15.1 license on a USB dongle (parallel port or USB), but cannot get the ALM service to enumerate it. The host is Windows 11, build 22000 or newer, on x64 hardware with a 32 GB or larger RAM complement.

The fault is reproducible on any attempt to launch Siemens Setup for V15.1, and is independent of the license key type (floating, single, trial, or upgrade license). It is also independent of whether the user is a local administrator, a standard user with UAC elevation, or signed in with a Microsoft account. The setup log generated by the installer contains the same message and provides no remediation hint, because the failure occurs before the licensed feature detection layer is loaded.

2. Affected Software and Environment

The failure pattern has been confirmed on the following combinations:

Windows 11 builds that exhibit the symptom: 21H2 (build 22000), 22H2 (build 22621), 23H2 (build 22631), and 24H2 (build 26100). TIA Portal V15.1 was tested and signed only against Windows 7 SP1 / Windows Server 2008 R2, Windows 8.1 / Server 2012 R2, and Windows 10 (1507 to 1809). The official Siemens Industry Online Support compatibility tool does not list V15.1 for any Windows 11 build.

3. Root Cause Analysis

The dialog is triggered by a chain of three independent failures, each of which can be fixed separately:

1. Expired code signature chain. The V15.1 installers are signed with a Siemens AG code-signing certificate issued in 2017. Windows 11 enforces stricter certificate trust rules, and a signature whose timestamp is older than the current root CA cross-certificate is rejected before the manifest is parsed. The setup launcher therefore exits with the generic "needs a license" message because the actual license module never loaded.
2. Missing or out-of-date Automation License Manager. Even if the TIA Portal setup got past the signature check, the ALM bundled on the V15.1 DVD is V6.0 SP3 (or earlier). The current ALM is V6.0 SP7+ and is the only build that supports the FLEXnet / CodeMeter entitlement layer expected by V15.1 once installed. Without the current ALM, license detection fails regardless of the dongle state.
3. Remnant registry and service state from V16 trial. The Siemens setup removes most program files when the trial is uninstalled but leaves behind the Siemens\AutomationLicenseManager service entry and HKLM\SOFTWARE\Siemens\License subkeys. When V15.1 setup scans for an existing ALM installation, it finds a partial fingerprint of V16 and short-circuits to the "license needed" branch instead of installing fresh.

Any one of those three roots is sufficient to reproduce the dialog. The recommended remediation therefore addresses all three in sequence.

4. Pre-Installation Diagnostic Steps

Before applying a workaround, capture the state of the host so that Siemens Support can triage the issue in case escalation is needed.

1. Collect the setup log. Run the V15.1 setup from an elevated command prompt so the failure path is preserved:
   "D:\Support\Setup\Siemens Setup\Siemens.Setup.Launcher.exe" /log "%USERPROFILE%\Desktop\TIA_V15_1_install.log"
   Search the resulting log for the strings LicenseCheck, ALM_STATUS, and 0x8007xxxx. The hex codes you will most commonly see are 0x80072EE7 (network name no longer available, ALM RPC endpoint) and 0x80070005 (access denied on the ALM service registry key).
2. Verify the ALM service state. Open services.msc and look for Automation License Manager Service. If the service is missing, the V15.1 bundled ALM never registered. If it is present but cannot be started, open Event Viewer under Applications and Services Logs > Siemens Automation License Manager.
3. Inspect the residual license registry. Launch regedit and remove the following keys only after the V15.1 setup has been confirmed broken:
   HKLM\SOFTWARE\Siemens\License
HKLM\SOFTWARE\Wow6432Node\Siemens\License
HKLM\SYSTEM\CurrentControlSet\Services\ALM
4. Capture the OS and .NET state. Run msinfo32 /report %USERPROFILE%\Desktop\msinfo.nfo and confirm that at least .NET Framework 4.7.2 is installed. V15.1 will not start on a Windows 11 host that has been stripped of .NET 3.5, which is required by ALM V6.0.

5. Solution Path A: Manual Automation License Manager Install

The fastest fix is to break the chicken-and-egg loop between the TIA Portal installer and the ALM by deploying the current ALM first. The current Automation License Manager package is published on the Siemens Industry Online Support portal as entry ID 109751124. Always download it directly from Siemens rather than from the DVD media.

1. Sign in to the workstation as a local administrator.
2. Download the current Automation License Manager V6.0 SP7+ package from the Siemens Industry Online Support portal (search "Automation License Manager download").
3. Extract the archive to a writable folder such as C:\Temp\ALM\ and right-click Setup.exe > Run as administrator. The standalone installer does not depend on the TIA Portal setup launcher and will not raise the "needs a license" dialog.
4. Once ALM is installed, confirm that the service Automation License Manager Service is set to Automatic and is in the Running state. The executable path is %ProgramFiles%\Siemens\AutomationLicenseManager\almservice.exe.
5. Insert the USB license key, open the ALM UI, and verify the entitlement is listed under Connectable devices. If the dongle is not visible, install the appropriate HASP HL driver (current build is part of the ALM install but can also be re-deployed via %ProgramFiles%\Siemens\AutomationLicenseManager\Drivers\Sentinel HASP\setup.exe).
6. Mount the V15.1 DVD and run Siemens.Setup.Launcher.exe as administrator. The setup will now detect the running ALM service and skip the "needs a license" check, allowing STEP 7, WinCC, and the rest of the V15.1 suite to install.

This path takes 15-30 minutes on a clean Win11 host. It does not require a Windows 10 VM, does not require a new license, and keeps the user's existing V15.1 USB entitlement intact.

6. Solution Path B: Windows 10 Virtual Machine

If the manual ALM approach does not work - typically because the V15.1 setup still fails on a deeper signing or UAC boundary - the safest engineering-grade fix is to host TIA Portal in a Windows 10 VM. This is the configuration most support engineers use internally when reproducing customer issues against retired TIA Portal versions.

1. Enable Hyper-V on the Windows 11 host with DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V, or use VMware Workstation Pro / VirtualBox if Hyper-V is reserved for WSL2 or Credential Guard.
2. Create a Generation 2 VM with the following minimums:
   - 4 vCPU
   - 16 GB RAM (out of 32 GB host RAM)
   - 200 GB dynamic VHDX
   - Windows 10 22H2 (build 19045) Professional or Enterprise
   - Virtual TPM enabled
3. Disable Secure Boot in the VM and disable memory integrity (Core Isolation) on the host. Both features break the HASP HL driver that the license key depends on.
4. Map the USB license key through to the VM with the host's USB controller set to USB 3.0 in the VM settings. Confirm the dongle is visible in the guest Device Manager.
5. Install the current ALM in the guest (same procedure as in Path A) and then install TIA Portal V15.1 from the DVD inside the guest.
6. Snapshot the VM after a successful install. Subsequent upgrades to V16 or V17 can be installed side by side in the same VM by using separate user profiles.

Use the VM exclusively for TIA Portal; keep the Windows 11 host free of any Siemens software to avoid signature conflicts if a future V18 install is required.

7. Solution Path C: License Upgrade via Software Update Service

If the engineering requirement allows it, the cleanest long-term resolution is to retire the V15.1 license in favour of a current TIA Portal version covered by an active Software Update Service (SUS) contract. The SUS program is Siemens' subscription model that entitles the customer to all updates between the version of the license at subscription start and the latest released version.

1. Log in to the Siemens Industry Online Support portal and open My Products > License Management. Verify the SUS status of the existing V15.1 license.
2. Submit a "License upgrade to current version" request. With an active SUS contract, Siemens will issue an upgrade license that is valid for the current top-of-tree TIA Portal and is backward compatible to TIA Portal V13 SP1 / V14 / V15 / V15.1 on the supported OS list. Without SUS, the upgrade is still possible but is treated as a new purchase.
3. Receive the new license in the form of a Certificate of License (CoL) and a license key file, or as an upgrade to an existing USB key.
4. Install the current TIA Portal on Windows 11 directly. V16 is recommended for stable general-purpose work; V17 is required for OPC UA features, security updates, and S7-1500 CPUs with firmware V2.9 or higher.
5. Return the V15.1 dongle to Siemens or repurpose it as a backup.

Upgrading is usually less expensive than a second engineering-week of install troubleshooting, and it removes the Win11 compatibility problem at the source.

8. Solution Path D: Escalation to Siemens Support

If Paths A through C are blocked (for example, the customer is contractually required to use V15.1, no SUS contract exists, and Hyper-V is reserved for a domain controller), the issue must be escalated to Siemens. A formal Support Request will produce either a signed hotfix installer or an official statement that V15.1 is not supported on Windows 11.

1. Open the Siemens Industry Online Support portal and select Support Request > Create new request.
2. Choose the product path Automation > Industrial Automation Systems > SIMATIC TIA Portal and the version V15.1.
3. Attach the diagnostic artifacts collected in Section 4: the TIA_V15_1_install.log, the msinfo32 report, a screenshot of the dialog, and the export of HKLM\SOFTWARE\Siemens\License taken from a reg export command.
4. In the description, state the exact Windows 11 build, the previous V16 trial that was uninstalled, and the fact that the manual ALM install was attempted. Siemens will return a workaround document for V15 on Windows 11 or will recommend a target version.

Expect 3-10 business days for a first response on a TIA Portal installation issue. Critical production escalations can be flagged with the Production down priority, which is the only SLA-bound category for non-contract customers.

9. Verification Procedure

After applying any of the four solution paths, run the following checks in order. Each must pass before the install is considered complete.

1. Service check. In services.msc, Automation License Manager Service is Running and its startup type is Automatic. The service account is LocalSystem with the Allow service to interact with desktop flag enabled.
2. License enumeration. Open the ALM UI, choose Connect to local server, and confirm the V15.1 license is listed with a green status. If the status is yellow, re-seat the USB dongle and click Refresh.
3. TIA Portal start. Launch TIA Portal V15.1 and verify the splash screen transitions to the Portal view without a license warning. Create a new project, add an S7-1500 device, and confirm the project can be saved.
4. Compile and download. Add a simple STL or LAD block to the project, compile (no errors expected), and download to a physical S7-1500 CPU on a test bench. A successful download proves the full ALM-to-Portal-to-PLC handshake is functional.
5. Log review. Re-open the TIA Portal log under %ProgramData%\Siemens\Automation\Log\ and confirm there are no EALM_0004, EALM_0007, or 0x80070005 entries since the install.

10. TIA Portal Version Compatibility Matrix

The following reference matrix is condensed from the official TIA Portal version overview and should be used when selecting the target version for a Windows 11 host.

For each newer version, the Automation License Manager is delivered as part of the main installation media and is signed to Windows 11 requirements, so the "needs a license" dialog does not occur. Note that the bundled ALM in V16 has the same Win11 signature problem as V15.1 on a fresh install; the manual ALM install trick is also the recommended workaround when installing V16 from DVD onto a clean Win11 host.

11. Frequently Asked Questions