Resolving S7-SCL Editor Not Opening in STEP 7 V5.6

1. Problem Statement

Engineers running STEP 7 V5.6 with the optional S7-SCL package on Windows 10 report a specific failure mode: double-clicking an SCL source or compiled SCL block in the SIMATIC Manager causes the editor window to appear as an item on the Windows taskbar, but the window never receives focus, never draws its content, and never accepts keystrokes. The process (SCL_Editor.exe) is alive in Task Manager, consumes CPU, but the UI is effectively unreachable.

This article documents the root cause, the diagnostic procedure, and the field-proven resolution steps for the S7-SCL editor not opening on STEP 7 V5.6 SPx with Windows 10 1909 (OS build 18363) and later. It also covers the related failure pattern where the editor appears to launch but renders only a blank gray content area, and the migration prerequisites to a TIA Portal project.

2. Affected Versions and Environment

The behavior is reproducible on the following configuration matrix:

Officially, S7-SCL V5.3 SP5 or later is the documented minimum option package version for STEP 7 V5.6 installations that will eventually be migrated to TIA Portal. This requirement is also called out in the Migrating SCL programs (S7-300, S7-400) documentation. A version below the minimum will compound the editor-open problem and will block the migration step described in Section 9.

3. Root Cause Analysis

The failure is a process-launch and window-painting problem, not a STEP 7 project corruption problem. Engineers who attempted Save As > With Reorganization (slow) and opened different projects confirmed the SCL editor remained broken across projects. The root cause is a stale or partially broken S7-SCL editor environment interacting with Windows 10 1909+ display subsystem changes.

3.1 Primary Cause: S7-SCL Editor Profile and COM Registration

The S7-SCL editor is implemented as a separate Win32 application that is launched and owned by SIMATIC Manager via COM. The editor stores user-specific configuration in:

• %APPDATA%\Siemens\Automation\SCL\ (user profile)
• %LOCALAPPDATA%\Siemens\Automation\SCL\ (local cache, last open positions)
• Registry hive: HKCU\Software\Siemens\Automation\SCL
• Registry hive: HKLM\SOFTWARE\Siemens\Automation\S7-SCL (installation)

If the editor process is killed while a window is mid-create (Windows shutdown, BSOD, taskkill), the persisted window state can record coordinates that lie outside the visible monitor area or at a position that Windows 10 1909 treats as "do not show". The next launch positions the window off-screen or with WS_VISIBLE set incorrectly, hence the visible taskbar entry with no client area.

3.2 Secondary Cause: DPI Awareness Mismatch

Windows 10 1909 (build 18363) shipped a refresh of per-monitor DPI scaling. The S7-SCL editor is a System DPI-Aware application that does not declare Per-Monitor V2 DPI awareness. On systems running mixed-DPI multi-monitor setups (laptop + external 4K at 175% / 200% / 225% scaling), the editor window can be created with negative or zero effective extent when the originating display changes between launches.

3.3 Tertiary Cause: Virtual Memory / Pagefile Configuration

Although 18 GB free disk and 32 GB RAM appear sufficient, S7-SCL performs a large contiguous allocation on editor start for the symbol table mirror. If the pagefile is set to System Managed with a small maximum on systems with multiple RAM disks or with VSS snapshots active, the allocation can return an in-process address that the Win32 window manager subsequently refuses to map to a DC. The result is the same: process alive, no visible window.

3.4 Quaternary Cause: Windows Cumulative Update Side Effect

Cumulative updates for Windows 10 1909 - notably those released after KB4580929 - modified user32.dll behavior around ShowWindow() and the new taskbar grouping logic. COM-based child windows of long-running Win32 hosts (which is exactly the SIMATIC Manager > SCL_Editor relationship) can be left in a "pending visibility" state when the taskbar grouping algorithm groups the editor into a non-focusable cluster. A full S7-SCL reinstall repairs the COM registration; the user profile reset repairs the window position.

4. Diagnostic Procedure

Run the following checks in order. Each check is non-destructive.

1. Confirm the S7-SCL process is alive. Open Task Manager > Details. Sort by name and confirm SCL_Editor.exe is present. If it is not, the editor is not actually launching - go to Section 5 Method A.
2. Confirm the window is not off-screen. Right-click the editor's taskbar entry, choose Move, then press an arrow key. If the cursor jumps to a window edge, the window is off-screen. Drag it back. This proves root cause 3.1.
3. Inspect window properties. Run spy++ (Visual Studio) or WinSpector against SCL_Editor.exe. Confirm the window has WS_VISIBLE and a non-zero rcClient rectangle. If rcClient is empty, root cause is the profile or the cumulative update.
4. Check the S7-SCL version. Start > SIMATIC > S7-SCL > S7-SCL (or scl.exe /V from C:\Program Files (x86)\Siemens\Automation\S7-SCL\bin\). Confirm the version matches the STEP 7 base version. Mismatched versions (e.g., STEP 7 V5.6 with S7-SCL V5.3 SP4) must be upgraded.
5. Check the pagefile. wmic pagefile list /format:list. Confirm the pagefile is on a fixed drive and is at least the size recommended by the system (typically 1-4 GB minimum on a 32 GB RAM system). If pagefile is disabled or set to less than 800 MB, root cause 3.3 is likely.
6. Check DPI and scaling. Settings > System > Display. If scaling is set to 125%, 150%, 175%, or 200% on the primary display and a secondary display runs at 100%, root cause 3.2 is likely.

5. Resolution Methods

Apply the methods in order. Stop at the first one that resolves the issue.

5.1 Method A: Reset the S7-SCL User Profile

This is the least invasive fix and addresses the off-screen window state.

1. Close the SIMATIC Manager and confirm no SCL_Editor.exe is running in Task Manager.
2. Open PowerShell and run:
   Remove-Item -Recurse -Force "$env:APPDATA\Siemens\Automation\SCL"
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\Siemens\Automation\SCL"
3. From regedit, navigate to HKCU\Software\Siemens\Automation\SCL, export a backup, then delete the SCL key.
4. Re-launch the SIMATIC Manager, open the project, and double-click an SCL block.

5.2 Method B: Reinstall S7-SCL with Matching Version

Use the installation media that matches your STEP 7 V5.6 disk revision. A clean reinstall repairs the COM class registration and the DCOM launch permissions that the editor depends on.

1. Control Panel > Programs and Features > uninstall S7-SCL V5.6.
2. Browse the STEP 7 V5.6 DVD or mounted ISO to Setup\S7-SCL\.
3. Run Setup.exe and select Install S7-SCL. Choose the same language and the same installation path as STEP 7 (default: C:\Program Files (x86)\Siemens\Automation\).
4. Reboot. The DCOM service must be reset for the new registration to take effect.
5. Open the SIMATIC Manager and verify the SCL editor opens.

5.3 Method C: Configure Virtual Memory

Set the pagefile to a fixed, generous size on the boot drive. This addresses root cause 3.3.

1. Settings > System > About > Advanced system settings > Performance > Settings > Advanced > Virtual memory > Change.
2. Uncheck Automatically manage paging file size for all drives.
3. Select the C: drive and choose Custom size.
4. Set Initial size (MB) = 16384 and Maximum size (MB) = 32768 on a 32 GB RAM system. Scale proportionally on smaller systems: roughly 25-100% of physical RAM.
5. Click Set, OK, and reboot.

5.4 Method D: Override DPI Awareness for SCL_Editor.exe

For mixed-DPI multi-monitor setups (root cause 3.2), force the editor to use System DPI awareness.

1. Locate SCL_Editor.exe, typically at C:\Program Files (x86)\Siemens\Automation\S7-SCL\bin\SCL_Editor.exe.
2. Right-click > Properties > Compatibility > Change high DPI settings.
3. Check Override high DPI scaling behavior. Scaling performed by: and select System.
4. Apply and reboot.

5.5 Method E: Save As with Reorganization

If Method A through D do not apply (e.g., the editor starts in some projects but not others), the project itself may carry a corrupted block container. SIMATIC Manager can rebuild the container with a slow reorganization.

1. Open the project in the SIMATIC Manager.
2. File > Save As.
3. Choose a new project name and check With reorganization (slow).
4. Open the new project and double-click an SCL block. The editor will create a fresh SCL container and re-read the persisted window state from the user profile, which - if Method A was also applied - is now empty.

5.6 Method F: Repair the DCOM Launch Permissions

For cases where the editor is launched as a DCOM server by the SIMATIC Manager.

1. dcomcnfg > Component Services > Computers > My Computer > DCOM Config.
2. Locate SCL_Editor in the list. If it is not present, reinstall S7-SCL (Method B) - the CLSID is registered at install time.
3. Right-click > Properties > Security. Confirm that the Launch and Activation Permissions allow the interactive user and the SYSTEM account.
4. Under Identity, select Launching user (default) or Interactive user.
5. Apply, close dcomcnfg, and reboot.

6. Verification Procedure

After applying a fix, verify the resolution end-to-end:

1. Start the SIMATIC Manager and open the affected project.
2. Navigate to the S7 program > Sources.
3. Double-click an SCL source. The SCL_Editor must open with the source code visible within 2-3 seconds.
4. Edit a line, save (Ctrl+S), and compile (Ctrl+B). Compilation must complete without a "SCL compiler not found" error.
5. Close the editor. The SCL block icon in the SIMATIC Manager must update to a timestamp consistent with the save.
6. Repeat the test on a second block to confirm the fix is not a one-off.
7. Reboot the workstation and repeat steps 2-4 to confirm persistence across restarts.

7. Prevention and Best Practices

To keep the S7-SCL editor stable on Windows 10 1909+ and Windows 11 systems:

• Pin the S7-SCL version to the matching STEP 7 base version. Document the build number in the engineering workstation asset record.
• Disable Windows fast startup (Control Panel > Power Options > Choose what the power buttons do > uncheck Turn on fast startup). Fast startup contributes to the corrupted window-position profile in root cause 3.1.
• Run the SIMATIC Manager and SCL_Editor on a single, primary monitor. Avoid docking station / undocking cycles while a project is open.
• Exclude the S7 install directory and the user profile from antivirus real-time scanning. Trend Micro, Kaspersky, and Windows Defender have all been observed to interfere with the DCOM launch handshake for the SCL_Editor.
• Schedule Windows cumulative updates for off-hours. After each Patch Tuesday, run the diagnostic procedure in Section 4 before resuming active development.
• Maintain a workstation image that includes STEP 7 V5.6 + S7-SCL V5.6 + the latest hotfix. Restore from image rather than attempting an in-place repair when an editor instability appears.

8. Troubleshooting Matrix

9. Migration Path to TIA Portal

Once the S7-SCL editor is stable, plan the migration to a TIA Portal project. The official prerequisite is the S7-SCL option package at version V5.3 SP5 or later installed on the source device. SCL blocks at this version or higher can be migrated; blocks at earlier versions will require manual rewrites. The procedure is documented in the Migrating SCL programs (S7-300, S7-400) page of the TIA Portal V20 documentation set.

10. Field-Proven Notes and Caveats

• Engineers who performed a full STEP 7 V5.6 reinstall (not just S7-SCL) reported the most durable fix. The SIMATIC Manager registry keys, the DCOM class registrations, and the S7-SCL editor registration are linked. A partial repair can leave the editor visible in the SIMATIC Manager menu but unable to launch.
• Reorganizations with Save As > With reorganization (slow) do not repair the editor itself. They only rebuild the S7 program container. Always combine with a user-profile reset (Method A) when the editor is the issue.
• Microsoft .NET Framework 4.8 (shipped with Windows 10 1909) is required by some Siemens hotfix installers. Confirm .NET 4.8 is enabled in Turn Windows features on or off before reinstalling.
• On Windows 11 22H2, the same symptoms have been reported and the same methods apply. Method D (DPI override) is required on Windows 11 because Windows 11 defaults to per-monitor V2 DPI for all new applications and pushes that scaling down to legacy Win32 hosts.
• If the engineering workstation is a VM (Hyper-V, VMware, VirtualBox), confirm that the guest additions / VMware Tools are current. A stale display driver inside the guest can manifest the same off-screen window symptom.

FAQ