Siemens STARTER Installation on Windows 7: Resolving BSOD Errors

David Krause10 min read
SiemensTroubleshootingVFD / Drives
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview: STARTER Commissioning Software and Windows 7

Siemens STARTER (commissioning tool for SINAMICS drives) is the standard engineering environment used to parameterize, diagnose, and commission the SINAMICS G120, G120C, G120D, G120P, G130, G150, S110, S120, S150, and SIMOTION-connected drive families. The tool communicates with drives over PROFIBUS, PROFINET, RS232 (USS), and Ethernet/IP via the SIMATIC NET stack, and is shipped as a stand-alone installer that historically integrates with STEP 7 V5.x or sits beside the TIA Portal in the SINAMICS Startdrive environment.

On legacy laptop fleets running Windows 7, STARTER is still the dominant tool because many service engineers run V5.x to maintain installed bases of SINAMICS G120 and S120 drives that pre-date the TIA Portal migration. The combination of Windows 7 32-bit Home editions and STARTER V4.x / V5.x installers has produced a well-documented pattern of install-time Blue Screen of Death (BSOD) failures, often originating from the auto-installed License Manager service. This reference documents the supported editions, the specific STARTER build that runs on a 32-bit host, and the procedure to recover from the BSOD during the install of the License Manager.

Windows 7 Edition Support Matrix for STARTER

STARTER V5.x and V4.x are 32-bit applications. Siemens explicitly certifies the tool against a narrow subset of Windows 7 SKUs. Selecting an unsupported edition results in install failure, license manager crash, or silent runtime instability when commissioning SINAMICS drives.

Windows 7 Edition STARTER V4.x STARTER V5.1 SP1 HF2 STARTER V5.3 / V5.4
Starter Edition Not supported Not supported Not supported
Home Basic / Home Premium Not supported Not supported (works unofficially) Not supported
Professional 32-bit Supported (V4.2 HF1) Supported via compatibility mode Not supported
Professional 64-bit Supported Supported (recommended) Supported with STEP 7 V5.5.3.7+
Ultimate / Enterprise 32-bit Supported Supported Not supported
Ultimate / Enterprise 64-bit Supported Supported Supported with STEP 7 V5.5.3.7+
Windows 7 Starter and Windows 7 Home editions lack the security identifiers and DCOM services that STARTER's License Manager and SIMATIC NET components require. Installation will either fail at the StarterSetup.exe pre-check or produce a STOP 0x0000007E / 0x00000050 BSOD when the License Manager kernel driver initializes.

STARTER Build Selection: V4.2 HF1 vs V5.1 SP1 HF2 vs V5.3

Three builds of STARTER are typically deployed in the field. Choosing the wrong build against the host operating system is the most common cause of install-time BSOD errors.

Parameter STARTER V4.2 HF1 STARTER V5.1 SP1 HF2 STARTER V5.3 / V5.4 SP3
Siemens KB / Entry ID 26233208 (entry family) 26233208 Entry 109746330
Supported OS Win XP SP3, Win 7 32/64 Win XP SP3, Win 7 32/64 Win 7 64-bit, Win 10 64-bit
STEP 7 prerequisite None (standalone) None (standalone) STEP 7 V5.5.3.7 or higher
License Manager V5.2.x (legacy) V5.3.x (compatible) V5.4.x (64-bit only)
SINAMICS firmware coverage Up to FW V4.4 Up to FW V4.7 FW V4.7 to V5.2 SP3
32-bit install on Win 7 Yes Yes (compatibility mode) No (blocked)
Recommended for fleet of 40 G120/S120 Legacy maintenance only Yes — preferred Requires Win 10 64-bit host

For an engineer commissioned to commission or re-parameterize a fleet of 40 SINAMICS G120 and S120 drives, the deterministic choice is STARTER V5.1 SP1 HF2 on Windows 7 Professional 64-bit. The same build also installs on Windows 7 Professional 32-bit when the setup is launched in Windows XP SP3 compatibility mode, but this configuration is not officially supported and is used as a fallback only.

Prerequisites Before Installation

  1. Confirm the host SKU. Press Win + Pause or run msinfo32.exe and verify OS Name is Windows 7 Professional, Ultimate, or Enterprise. Windows 7 Home or Starter editions will not support the License Manager service.
  2. Confirm the OS architecture. Run wmic os get osarchitecture in an elevated command prompt. Expect 64-bit; STARTER V5.3 will not install on 32-bit.
  3. Install Microsoft .NET Framework 3.5 SP1 and 4.x. STARTER Setup refuses to proceed if these runtimes are missing; in their absence the License Manager installer raises a CLR 0xE0434352 exception that maps to a Windows STOP 0x0000007E.
  4. Install the SIMATIC NET PC software (V8.x or later) or at minimum the SIMATIC NET communication services if the laptop will talk to SINAMICS drives over PROFINET.
  5. Disable antivirus real-time scanning during the install. Several OEM security suites (Trend Micro OfficeScan, McAfee Endpoint) inject filter drivers that conflict with the License Manager kernel hook and produce STOP 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL).
  6. Ensure the user account is in the local Administrators group and that UAC is set to the lowest notification level for the duration of the install only.
  7. Verify available disk space: minimum 4 GB free on C:\, plus 1 GB for the STARTER project archive folder.

Installation Procedure with Compatibility Mode

For STARTER V5.1 SP1 HF2 on Windows 7 Professional 32-bit, the install must be run with explicit compatibility shims. The Siemens Knowledge Base entry STARTER: Installation on Windows 7 Professional 64 bit (ID 74509988) documents the same procedure that applies to the 32-bit host.

  1. Download the STARTER V5.1 SP1 HF2 archive from the Siemens Industry Online Support portal under entry 26233208. The archive typically contains Starter_Setup.exe, Setup.exe, and the autorun Setup Launcher.exe.
  2. Extract or mount the ISO to a local folder, e.g. D:\STARTER_V51_SP1_HF2\. Do not run the setup from a network share — SMB latency has been observed to corrupt the License Manager install and trigger a BSOD.
  3. Right-click Starter_Setup.exe, select Properties → Compatibility.
  4. Check Run this program in compatibility mode for: and select Windows XP (Service Pack 3).
  5. Check Run this program as an administrator.
  6. Click Change settings for all users to apply the same shim globally so that the launched Setup.exe inherits the context.
  7. Click Apply then OK.
  8. Right-click Starter_Setup.exe and choose Run as administrator.
  9. In the setup wizard, accept the license agreement, choose Install (not Modify), and select the destination folder (default C:\Program Files\Siemens\Automation\S7-START).
  10. When prompted, allow the License Manager install to proceed. This step is the most common BSOD trigger — see the next section if a STOP screen appears.
  11. Reboot when the installer requests it.
  12. Launch STARTER from Start → Siemens Automation → SIMATIC → STARTER and confirm the splash screen reports V5.1 SP1 HF2.

BSOD Root Cause Analysis During License Manager Install

The most frequently reported failure is a STOP screen occurring immediately after the License Manager automatic install completes, before STARTER itself launches. The error has three known root causes in Windows 7 environments.

Root Cause STOP Code Trigger Fix
32-bit License Manager driver on Win 7 64-bit host (or vice-versa) 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) Architecture mismatch between OS and License Manager build Reinstall matching the OS bitness; do not use V5.3 License Manager on Win 7 32-bit
Antivirus filter driver intercepting License Manager IRP 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL) Trend Micro / McAfee / Sophos injecting NDIS hooks Uninstall or disable AV, reboot, rerun setup
Corrupted prior install state in C:\ProgramData\Siemens\Automation\LicenseManager\ 0x00000050 (PAGE_FAULT_IN_NONPAGED_AREA) Interrupted earlier install Delete residual folders, clean registry, reinstall
Missing .NET Framework 3.5 SP1 0x0000007E with module clr.dll CLR runtime not present Install .NET 3.5 SP1 via Programs and Features, then rerun
Capture the minidump from C:\Windows\Minidump\ and submit to Siemens support with the License Manager log located at C:\ProgramData\Siemens\Automation\LicenseManager\Logs\. This evidence is required before Siemens will issue a hotfix.

Step-by-Step Recovery From BSOD During Install

  1. Boot Windows 7 in Safe Mode with Networking by pressing F8 during POST.
  2. Open Device Manager and look under System devices for any yellow-banged Siemens License Manager entry. Right-click and choose Uninstall, deleting the driver software.
  3. Delete residual folders:
    1. C:\Program Files\Siemens\Automation\LicenseManager\
    2. C:\ProgramData\Siemens\Automation\LicenseManager\
    3. C:\Program Files (x86)\Common Files\Siemens\
  4. Open regedit and remove the following keys if present:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Automation\LicenseManager
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\almsrv
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\almsrvhelper
  5. Run msconfig, switch to the Services tab, and uncheck any residual Siemens License Manager Service entry. Apply and reboot into normal mode.
  6. Reinstall STARTER V5.1 SP1 HF2 using the compatibility-mode procedure above.
  7. If the BSOD recurs, capture the dump with WinDbg and confirm the faulting module. Open the dump with !analyze -v and look for the MODULE_NAME line.

Connecting to SINAMICS G120 and S120 After Install

Once STARTER V5.1 SP1 HF2 launches cleanly, commission the G120 / S120 fleet using the standard online workflow:

  1. Set the PG/PC interface. Open Start → SIMATIC → SIMATIC NET → Configuration Console → PG/PC Interface. For PROFINET, choose S7ONLINE → TCP/IP → <your NIC>.
  2. In STARTER, click Accessible nodes in the toolbar. The SINAMICS G120 (Control Unit CU240E-2, CU250S-2) or S120 (CU310-2, CU320-2) should appear with its IP address and PROFIBUS / PROFINET name.
  3. For S120, load the topology by selecting the drive and choosing Online → Load to PG. STARTER will retrieve the DO list (e.g. SERVO_01, SERVO_02, SERVO_03) plus the active topology and parameter set.
  4. For G120, choose Online → Load to PG to retrieve the parameter set (P parameters, e.g. P0108 = commissioning interface, P0010 = 30 for factory reset, P0010 = 1 for quick commissioning).
  5. Save the project to a versioned folder, e.g. D:\Sinamics_Projects\Fleet_G120_2024_Q3\. Use the Archive function to package the project for travel between plants.
If STARTER cannot see the drive over PROFINET, confirm that the DCP discovery is not blocked by a managed switch. Many Cisco and HPE switches disable LLDP/DCP by default on edge ports. Enable LLDP transmit and CDP aware on the port, or temporarily attach the PG directly to the drive's service port (X127 on G120, X120 on S120 CU310-2).

Verification Checklist

  • STARTER Help → About reports V5.1 SP1 HF2 (V05.01.01.02) or later.
  • License Manager service almsrv.exe is present in services.msc and shows Started with Automatic startup type.
  • Accessible nodes returns the expected number of CU240E-2 / CU250S-2 / CU310-2 / CU320-2 units.
  • An online parameter read of r0002 (drive status word) on G120 or r899 on S120 returns a current value, confirming the USS/PROFINET channel is healthy.
  • A full Upload from PG / Download to target round trip on at least one drive completes without F0135 or F0802 fault codes.
  • The STARTER project archive opens cleanly on a second engineering station (validates project integrity).

Notes on Migrating Away from Windows 7

Siemens has officially sunset Windows 7 support in STARTER V5.4 SP3 and later. For new SINAMICS S120 firmware (V5.2 SP3 and above) and for SINAMICS G120 with FW V4.7 SP10, Siemens recommends migrating to Windows 10 64-bit or Windows 11 with TIA Portal V17 and SINAMICS Startdrive V17. The legacy STARTER V5.x path remains viable for maintenance contracts on installed bases but should not be used to commission new S120 units with safety-integrated functions (SIF) via PROFIsafe, as those require the newer Startdrive environment.

Frequently Asked Questions

Which STARTER version works on Windows 7 32-bit?

STARTER V5.1 SP1 HF2 installs and runs on Windows 7 Professional 32-bit when Starter_Setup.exe is launched in Windows XP SP3 compatibility mode and as administrator. STARTER V5.3 and V5.4 require Windows 7 64-bit and STEP 7 V5.5.3.7 or higher.

Does STARTER support Windows 7 Home or Starter editions?

No. Siemens certifies STARTER V4.x and V5.x against Windows 7 Professional, Ultimate, and Enterprise only. Windows 7 Starter and Home editions lack the DCOM and security services the License Manager requires, and the setup either refuses to continue or produces a STOP 0x0000007E BSOD during install.

What causes the BSOD immediately after the License Manager auto-installs?

The most common triggers are an architecture mismatch between the OS bitness and the License Manager build (STOP 0x7E), an antivirus filter driver intercepting the License Manager IRP (STOP 0xD1), or a corrupted prior install state in C:\ProgramData\Siemens\Automation\LicenseManager\ (STOP 0x50). Clean the residual folders and registry, disable antivirus, then reinstall using compatibility mode.

Can STARTER V5.1 SP1 HF2 parameterize a fleet of 40 SINAMICS G120 and S120 drives?

Yes. STARTER V5.1 SP1 HF2 supports SINAMICS G120 Control Units CU240E-2, CU250S-2, and S120 Control Units CU310-2 and CU320-2 with firmware up to V4.7. Use the Accessible nodes function to discover all drives over PROFINET or PROFIBUS, then archive the project per plant to maintain a versioned parameter history.

Where is the official Siemens KB article for STARTER installation on Windows 7?

Siemens Knowledge Base entry ID 74509988 — STARTER: Installation on Windows 7 Professional 64 bit documents the compatibility-mode procedure. The STARTER V5.1 SP1 HF2 download is published under entry 26233208.

Back to blog