Resolving SIMATIC PC Station Config Load Error on Windows 10

Problem Overview

Engineers maintaining SIMATIC PC Stations frequently encounter a hard configuration load failure when the host operating system is migrated from Windows 7 to Windows 10. The Station Configuration Editor (SCE) — invoked from the Windows Start menu or from the SIMATIC Net Configuration Console — attempts to load the PC station configuration, terminates the operation with an error dialog, and then opens with an empty project tree. Once the error is acknowledged, every action button in the SCE (Add, Import, Station Diagnostics, Download Station, Save and Compile) is greyed out. No module can be inserted, the configuration cannot be downloaded, and the OPC server or S7 connection behind the PC station cannot be started.

This is a regression that does not exist in the original Windows 7 image. It typically appears the moment the user upgrades the OS in place, even when the matching SIMATIC Net DVD (for example, SIMATIC Net V13 SP2) is installed immediately after the upgrade. Reinstalling SIMATIC Net on the upgraded image usually does not clear the fault because the licensing subsystem, the SCE runtime database, and the PG/PC interface bindings are already in a corrupted state. The cleanest recovery path is a fresh Windows 10 image, a fresh SIMATIC Net installation, and a Windows 10-compatible Automation License Manager (ALM).

Root Cause Analysis

Three layers of state contribute to the failure, and any one of them can be enough to lock out the SCE:

1. In-place OS upgrade corruption. An in-place upgrade from Windows 7 to Windows 10 replaces the kernel, the WinHTTP service, the network stack bindings, the Windows service accounts, and the COM security descriptors. SIMATIC Net 8.1 was compiled against the Windows 7 SDK and the older NDIS 6.x binding model. Some of its services — notably S7DOS, DPM, and the OPC server instances — fail to register correctly under Windows 10, leaving the SCE with no valid interface handle to read or write the station database.
2. SIMATIC Net / NCM version mismatch. The legacy Configuration Manager is NCM S7 (NCM 5.5 SP2 / SP4), while SIMATIC Net V13 ships with NCM S7 V13 (the TIA Portal-based manager) and the SIMATIC Net Configuration Console. The mixed presence of NCM 5.5 SP2 binaries and SIMATIC Net V13 runtime on the same machine leaves the SCE in a state where it can read the registry entries written by NCM 5.5 but cannot decode the project XML written by the V13 Configuration Console.
3. Automation License Manager (ALM) incompatibility. The ALM shipped with the SIMATIC Net 8.1 / NCM 5.5 SP2 DVD predates Windows 10 and uses an older Wibu-Systems runtime. When Windows 10 starts, the ALM service either refuses to start or starts but cannot enumerate the local license stick / license file. Without a working ALM, SIMATIC Net treats every licensed component as "missing license" and the SCE silently disables the configuration surface.

Combined, these three issues produce the symptom: the SCE launches, the load routine hits a WCF / DCOM boundary, fails to read the project, and the user interface drops into a fully disabled state.

SIMATIC Net and Windows Compatibility Matrix

Use this matrix to confirm that the installed SIMATIC Net version is actually supported on the target Windows release before touching the registry. Versions not listed as "supported" either fail to install cleanly or install but do not load the PC station configuration.

Cross-reference this table with the actual DVD or download that is mounted in the engineering workstation. If the installed version is on the "Not supported" row for the target Windows release, a clean install of the supported line is mandatory — no in-place patch will rescue the station.

Required Software Components

Before starting the recovery, gather the following on a writable USB drive or network share. Each item is a separate install image; do not run them in parallel.

• Windows 10 installation media, build 1607 or newer. Industrial users typically deploy Windows 10 LTSC 2019 (build 17763) or Windows 10 LTSC 2021 (build 19044) for long-term stability with TIA Portal V16 and later.
• SIMATIC Net DVD matching the planned TIA Portal line. For a TIA V13 SP2 environment, use SIMATIC Net V13 SP2. For TIA V16 / V17, use SIMATIC Net V16 or V17.
• STEP 7 V13 SP2 (or matching TIA Portal version) for the engineering station. The PC station configuration is generated from STEP 7 / TIA Portal and downloaded into the SCE; the SCE alone cannot author a configuration from scratch.
• Automation License Manager (ALM) for Windows 10. The currently supported build is published under Siemens Support entry 109751634; the legacy Windows 7 ALM is published under 114358. Use the Windows 10 build (ALM V6.0.x or newer) — the older 5.x build is the one that fails to start on Windows 10.
• License key (License Key Disk or license file) for SIMATIC Net and the PC station. Without a valid license, the SCE will still load, but OPC Scout and S7DOS will refuse to start.

Step-by-Step Recovery Procedure

The procedure assumes an engineering workstation that has been corrupted by an in-place Windows 10 upgrade. Work on a maintenance window — the install will reboot the PC multiple times.

1. Capture the existing PC station configuration

Before re-imaging, copy the SCE project file and the XDB export to a safe location. On a healthy Win7 machine, the project is stored under:

and the XDB / XML exports under:

If the corrupted Win10 image still allows file-level read access, copy these files. If the corruption is in the SCE, you may have to re-author the configuration in TIA Portal from the original project archive.

2. Re-image the workstation with Windows 10

Boot from the Windows 10 USB media and perform a clean install. Format the system partition; do not attempt a "repair install". Once the OS is up:

1. Apply all cumulative updates until Windows Update reports "You are up to date".
2. Disable driver signature enforcement temporarily if a third-party PROFINET / Industrial Ethernet card is in use, then install the vendor-signed driver.
3. Confirm the network interface that will carry the PROFINET / S7 traffic shows up in Device Manager → Network Adapters and that ping 127.0.0.1 and ping <CPU-IP> respond.
4. Set the interface to a static IP inside the plant subnet, for example 192.168.0.50 / 255.255.255.0, with no default gateway if the PC station is on a closed automation LAN.

3. Install a Windows 10-compatible ALM first

Order matters. The ALM must be installed before SIMATIC Net, because the SIMATIC Net installer queries the ALM service to verify licenses during setup.

1. Download the current ALM from Siemens Support entry 109751634.
2. Run Setup.exe as Administrator.
3. Accept the default installation path (C:\Program Files\Siemens\Automation License Manager).
4. Reboot. Verify that the service ALM License Service is Running in services.msc and that the ALM GUI launches without the "ALM 1.x has been replaced" warning.

If the legacy ALM 5.x is the only one that was carried over from the Win7 image, the service will refuse to start on Windows 10 and the SIMATIC Net installer will silently log "No ALM found". This is the most common cause of the "SCE buttons disabled" symptom.

4. Install SIMATIC Net V13 SP2 (or matching version)

Mount the SIMATIC Net DVD. During the install wizard:

1. Select PC Station as the install profile. The default profile already includes S7DOS, DPM, OPC server, and the SIMATIC Net Configuration Console.
2. Accept the default installation path. Do not change C:\Program Files\Siemens to a different drive letter — the SCE registry keys are hard-coded to that path.
3. On the Communication Settings page, set the access points that the PC station will use. For a typical S7-300 / S7-400 / S7-1500 link, the default S7ONLINE access point is correct. For an OPC Scout link, leave CP_HMI_1 as the default.
4. Choose Install as Windows Service for every component — never Manual for the production station.
5. Reboot when prompted.

5. Install STEP 7 / TIA Portal and re-author the PC station

If you are using TIA Portal V13 SP2 or newer, open the TIA project, navigate to Devices & Networks, and add a PC Station with the same station name as before. Slot the components in the same order:

Compile the PC station and download the configuration to the SCE. The SCE will show the project tree populated and the action buttons enabled.

6. Restore the PG/PC interface settings

Open Control Panel → Set PG/PC Interface and verify the following:

• The Access Point of the Application for S7ONLINE points to the IE General on the correct physical adapter, not to a virtual TAP adapter.
• The Interface Parameter Assignment for the Industrial Ethernet adapter is set to TCP/IP (Auto) for PROFINET IO, or ISO if the legacy S7 protocol is required.
• The PG/PC is the only master on the bus checkbox is not set for production stations — it disables permanent routing and is meant for commissioning laptops only.

Automation License Manager Setup

The ALM is the most common silent failure point on a migrated Windows 10 station. The following procedure verifies a clean ALM install and license registration.

1. Start the ALM GUI from the Start menu. The main window should show Local License Server and the service status as Running.
2. Click Edit → Connect to License Server. The default URL is http://localhost:4410 for the local instance, or http://<almserver>:4410 for a network license server.
3. Verify that the license for SIMATIC NET PC SW V13 is visible under the Local column. If the license is on a USB stick, the stick must be plugged in and the WibuKey driver installed.
4. If the license is missing, transfer it with Edit → Move License from the backup stick to the local C: drive license pool (C:\ProgramData\Siemens\sinumerik\sws for the older key pool, or C:\ProgramData\Siemens\ALM for ALM V6).
5. Open services.msc and confirm ALM License Service has Startup Type = Automatic and Status = Running. If the service does not start, the WibuKey runtime is the likely culprit and must be reinstalled from the ALM media.

Verifying the Installation

Once the install is complete, run the following checks in order. Any failure here indicates that the SCE will still misbehave on the next restart.

1. SCE loads the configuration. Open Station Configuration Editor from the Start menu. The PC station name should appear in the project tree and the modules listed in the configured slot order. The action buttons must be enabled.
2. Station Diagnostics is green. In the SCE, right-click the station name and choose Station Diagnostics → Online. All modules should report OK and the OPC server instance should be in the Running state.
3. S7 connection test. Open the SCE, select the IE General / CP module, and choose Diagnostics → Connection Test. Ping the configured CPU. A successful round-trip confirms that the S7DOS / DPM layer is alive.
4. OPC Scout test. Start OPC Scout V10 from C:\Program Files\Siemens\Automation\OPC Scout V10\bin\SCOUT.EXE. Add the local OPC DA server. Browse the tag namespace; tags from the configured S7 connection should appear with live quality codes.
5. PG/PC interface round-trip. From a separate engineering station, start TIA Portal and download the PC station configuration to the SCE. The download must complete without the "online interface cannot be reached" message reported in Siemens entry 12033912.
6. Reboot persistence. Reboot the PC station. After the reboot, the S7DOS and DPM services must auto-start, and the SCE must come up with the same configuration loaded. If the SCE reverts to the empty / disabled state, the SCE runtime database is corrupted and must be rebuilt (see Troubleshooting Matrix below).

Troubleshooting Matrix

Use this matrix when the install completes but the symptom returns. The first column is the observable symptom, the second is the most likely cause, the third is the corrective action.

Common Pitfalls and Edge Cases

In-place OS upgrade is not supported. Siemens does not certify any SIMATIC Net version for an in-place upgrade from Windows 7 to Windows 10. The Windows 7 → Windows 10 path always re-imaging must be: backup the project, re-image, install ALM, install SIMATIC Net, install TIA Portal, restore the project, re-download the configuration.

Mixing NCM 5.5 SP2 with SIMATIC Net V13 is the #1 reported failure. NCM 5.5 was the configuration tool for SIMATIC Net V8.x. Once SIMATIC Net V13 is installed, the active configuration tool is the SIMATIC Net Configuration Console (a Microsoft Management Console snap-in), not the legacy NCM. Leaving NCM 5.5 SP2 installed from the Win7 image will cause the SCE to read two competing project databases on startup.

PROFINET vs ISO selection. For a S7-300 / S7-400 CPU, the IE General interface can be bound to ISO (transport protocol, fast, plant-local only) or TCP/IP (RFC1006) (routable, slower). For a S7-1500 CPU, only TCP/IP (RFC1006) is supported. The setting is in the SCE, on the IE General module's Properties → Interface → Protocol tab.

Slot 1 must be the Industrial Ethernet adapter. The SCE enforces a hard rule: the IE General / CP 16xx must occupy slot 1, with the OPC server and S7DOS in slots 2 and 3. If TIA Portal places a user application in slot 1, the download will be accepted by TIA Portal but rejected by the SCE runtime.

Time synchronization. A SIMATIC PC station that hosts a WinCC Runtime or that publishes OPC UA data must have its clock synchronized to the plant time server. Use w32tm /config /manualpeerlist:<ntpserver> /syncfromflags:manual /reliable:YES /update followed by w32tm /resync. A clock skew of more than 5 seconds can cause OPC DA sessions to drop.

Antivirus exclusion list. Windows Defender and most enterprise antivirus products will quarantine S7DOS.exe, OPCEnum.exe, and dpm.exe on first launch. Add C:\Program Files\Siemens and C:\ProgramData\Siemens to the AV exclusion list before the first reboot.

FAQ