Resolving TIA Portal V14 Crash with S7DosWrapper.dll Error

1. Problem Overview

Engineers launching Siemens TIA Portal V14 SP1 Update 2 (STEP 7 V14 / WinCC V14) on a 64-bit Windows engineering workstation report an immediate application termination. The portal starts, attempts to open or create a project, and crashes with an unhandled System.IO.FileLoadException. The exception names the assembly Siemens.Automation.OnlineAccess.S7DosWrapper.dll and returns the native error code 0x8007045A (ERROR_DLL_INIT_FAILED).

Because the failure occurs before any project tree is rendered, no user data is lost, but the portal becomes unusable for new or existing work. The crash reproduces consistently on cold start, which makes it critical to resolve before commissioning windows or planned engineering work.

The identical symptom class has been confirmed on:

• STEP 7 Professional V14 SP1 Update 2 (build identifier 14.0.1.2)
• STEP 7 Basic V14 SP1 Update 2
• WinCC Comfort/Advanced/Professional V14 SP1 Update 2 (when launched via the TIA Portal shell)
• PLCSIM V14 SP1 Update 2 (when invoked from inside the TIA shell)

Operating environments most frequently affected:

• Windows 7 SP1 x64 (with KB3033929 SHA-2 support)
• Windows 10 1607 / 1703 / 1709 x64 (builds prior to 1809)
• Windows 10 1809 / 1903 / 1909 with legacy .NET Framework 4.7.2

2. Exact Exception String

The exception raised inside Siemens.Automation.Portal.exe is:

System.IO.FileLoadException: Could not load file or assembly
'Siemens.Automation.OnlineAccess.S7DosWrapper.dll' or one of its
dependencies. A dynamic link library (DLL) initialization routine
failed. (Exception from HRESULT: 0x8007045A)

Decoded values:

3. Root Cause Analysis

The native code in S7DosWrapper.dll performs privileged operations against the S7DOS device interface and the S7ONLINE service. On Windows versions that enforce strict User Account Control (UAC) integrity levels, an interactive user running the portal at Medium IL cannot register, attach, or communicate with the S7ONLINE helper service. The wrapper's DllMain therefore returns FALSE on its PROCESS_ATTACH call, and the .NET runtime surfaces this as the FileLoadException shown above.

Other root-cause vectors that produce the same HRESULT but require different fixes:

4. Pre-Flight Diagnostics

Before applying the compatibility fix, capture three data points so the root cause is confirmed, not assumed:

1. Confirm the S7DOS service is present and stopped/startable:
   

   sc query S7DOS
   sc qc S7DOS

   Expected: STATE: 1 STOPPED or 4 RUNNING. If 1060 (ERROR_SERVICE_NOT_FOUND), the OnlineAccess component was not registered.
2. List the wrapper DLL and check its digital signature:
   

   dir /a "C:\Program Files\Siemens\Automation\Portal V14\Public\Common\OnlineAccess\Siemens.Automation.OnlineAccess.S7DosWrapper.dll"
   signtool verify /pa "C:\Program Files\Siemens\Automation\Portal V14\Public\Common\OnlineAccess\Siemens.Automation.OnlineAccess.S7DosWrapper.dll"

   A valid Siemens AG signature is required; missing signature indicates tampering or partial file copy.
3. Reproduce the crash with Procmon (Sysinternals) filtering on Siemens.Automation.OnlineAccess.S7DosWrapper.dll:
   

   Filter: Path contains S7DosWrapper
   Operations: CreateFile, LoadImage, QueryOpen
   Result is NOT FOUND or ACCESS DENIED

   A NAME NOT FOUND means the file is missing (reinstall). An ACCESS DENIED confirms the UAC path described in Section 3.

5. Primary Fix: Compatibility "Run as Administrator" for the TIA Portal Executable

This is the procedure that resolved the reported case and is the first action Siemens Support recommends for the 0x8007045A signature.

5.1 Prerequisites

• User account is a member of the local Administrators group, or has been granted the Log on as service and Debug programs user rights.
• The S7DOS service is installed and its registry hive under HKLM\SOFTWARE\Siemens\S7DOS is intact.
• All TIA Portal instances are closed before editing the executable properties.

5.2 Step-by-Step

1. Open Windows Explorer and navigate to:
   %ProgramFiles%\Siemens\Automation\Portal V14 (or the install path you selected, default on x64: C:\Program Files\Siemens\Automation\Portal V14).
2. Right-click Siemens.Automation.Portal.exe → Properties.
3. Switch to the Compatibility tab.
4. Under Settings, enable "Run this program as an administrator".
   
   Note: Do not enable "Run this program in compatibility mode for:" unless the underlying Windows version is explicitly listed in the Siemens compatibility matrix. Forcing Windows XP/7 compatibility will introduce secondary faults in the .NET 4.7 runtime.
5. (Optional) Click Change settings for all users and re-enable the same box at the system level so every login is covered.
6. Click Apply → OK.
7. Launch TIA Portal V14 by double-clicking the Start Menu entry, the desktop shortcut, or the executable itself.

6. Secondary Fix: Repair the TIA Portal V14 Installation

If elevation alone does not eliminate the crash, the wrapper DLL or one of its native dependencies is corrupted or missing. Repair the install before performing a full uninstall/reinstall cycle.

1. Close all Siemens applications and stop the S7DOS service:
   

   net stop "s7dos" /y

2. Open Control Panel → Programs → Programs and Features.
3. Select Siemens TIA Portal V14 SP1 Update 2 (or the highest installed package, e.g. STEP 7 Professional V14 SP1).
4. Click Repair. The setup engine re-deploys the OnlineAccess components, the S7DosWrapper, and re-registers the S7DOS service.
5. Reboot. Verify with:
   

   sc query S7DOS
   where /R "C:\Program Files\Siemens" Siemens.Automation.OnlineAccess.S7DosWrapper.dll

   The second command must return one or more hits.

7. Dependency and Windows Component Checks

7.1 Re-registering the S7DOS Interface

If sc query S7DOS returns service not found, the OnlineAccess driver is missing from the system. Re-register manually:

cd "C:\Program Files\Siemens\Automation\Portal V14\Public\Common\OnlineAccess"
s7dosins.exe -regserver
net start s7dos

8. Advanced Diagnostics with sxstrace and Fusion Logging

When the file is present and UAC is bypassed but the loader still reports 0x8007045A, the failure is almost always a side-by-side (SxS) issue. Capture the trace:

1. Start trace as Administrator:
   

   sxstrace.exe trace -logfile:C:\TEMP\sxs.etl

2. Reproduce the TIA Portal crash.
3. Stop the trace and convert:
   

   sxstrace.exe parse -logfile:C:\TEMP\sxs.etl -outfile:C:\TEMP\sxs.txt

4. Open sxs.txt and search for the wrapper DLL. A typical bad entry reads:
   ERROR: Cannot resolve reference Microsoft.VC90.CRT,processorArchitecture="amd64"

To capture .NET binding failures in parallel, enable Fusion logging:

reg add "HKLM\SOFTWARE\Microsoft\Fusion" /v EnableLog /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Microsoft\Fusion" /v LogPath /t REG_SZ /d "C:\TEMP\FusionLogs" /f

Reproduce the crash, then inspect C:\TEMP\FusionLogs for the bind result against Siemens.Automation.OnlineAccess.S7DosWrapper.dll. Disable logging after the capture to avoid disk bloat:

reg delete "HKLM\SOFTWARE\Microsoft\Fusion" /v EnableLog /f

9. Antimalware and Filesystem Permission Interference

Some AV/EDR products (notably CrowdStrike, SentinelOne, and certain McAfee / Bitdefender builds) inject hooks into LoadLibrary and can return ERROR_DLL_INIT_FAILED when policy denies unsigned children of an unsigned parent. Symptoms include:

• Crash only after the AV agent was last updated.
• Operation: CreateFile → Result: REPARSE in Procmon.
• Event Viewer → Application log entry from the AV source with the path to S7DosWrapper.dll.

Add the following paths to the AV exclusion list, then reboot:

C:\Program Files\Siemens\Automation\Portal V14\
C:\Program Files (x86)\Siemens\Automation\Portal V14\
C:\Program Files\Siemens\S7Dos\
C:\Program Files (x86)\Common Files\Siemens\S7Dos\
%LOCALAPPDATA%\Siemens\
%APPDATA%\Siemens\

10. Verification Checklist

Confirm the fix is complete by running all of the following:

1. Launch TIA Portal V14 from a normal Start Menu click (no right-click → Run as Administrator). The portal shell must appear without crash.
2. Open an existing .ap14 project. No FileLoadException dialog should appear.
3. Create a new project → add an S7-1500 device → press Go online. The S7ONLINE connection dialog must list the configured PG/PC interface.
4. Check the S7DOS service is started by the portal:
   

   sc query S7DOS | findstr STATE

   It should report RUNNING.
5. Open Event Viewer → Windows Logs → Application. No new .NET Runtime Error 1026 entries referencing Siemens.Automation.OnlineAccess.S7DosWrapper should appear for at least 10 minutes of active use.

11. Prevention and Best Practices

• Apply the compatibility flag through the all-users dialog so service accounts and Domain Admin sessions inherit the elevation.
• Add the TIA Portal install root to the Windows Defender Controlled folder access allow list and to any third-party AV exclusion list.
• Block in-place upgrades of Windows 10 (e.g., 1709 → 1809) on engineering workstations without first re-validating the TIA installer. Microsoft .NET servicing updates can break the binding chain.
• Maintain a baseline image with TIA V14 SP1 UPD2 fully installed and the compatibility flag pre-applied; deploy via SCCM/Intune as the standard engineering image.
• Subscribe to the Siemens Industry Online Support KB feed for the Portal V14 product tree to receive hotfix notifications.

12. Related Issues and Error Variants