Resolving the STEP 7 "You can only open XXX if the Windows Regional and Language options is set to German" Project Open Error

Engineers and integrators working with legacy Siemens SIMATIC Manager (STEP 7 V5.x) projects occasionally encounter a hard-blocking error when opening a customer project: the SIMATIC Manager refuses to load the project and returns the message "You can only open XXX if the Windows Regional and Language options is set to German." This article documents the field-tested procedure to clear the lock without re-installing Windows, the underlying cause of the lock, the equivalent handling in TIA Portal V20, and the related regional/language issues that can reappear after Windows updates.

1. Problem Description

When the user double-clicks a STEP 7 V5.x .s7p project file or selects File > Open > Open Project from SIMATIC Manager, the application may raise a modal error dialog stating:

"You can only open [ProjectName] if the Windows Regional and Language options is set to German (Germany)."

The dialog blocks project loading entirely. The project tree, hardware configuration (HW Config), and program blocks remain inaccessible until the regional setting is changed.

1.1 Symptoms

• SIMATIC Manager shows the error at project open and aborts the load.
• All other project navigation is disabled until the offending regional setting is corrected.
• Switching the Windows regional format to German (Germany) resolves the open error but breaks downstream applications that depend on non-German codepage behavior (e.g., file explorers, network shares, scripts that use Japanese, Chinese (Simplified PRC), or UTF-8 folder names).
• Switching back to the user's native regional setting causes the STEP 7 project to become inaccessible again.

1.2 Affected Products

2. Root Cause

The lock is implemented by a marker file written by the original integrator inside the project directory:

\<project_root>\GLOBAL\LANGUAGE

The LANGUAGE file carries no file extension and stores a one- or two-letter culture tag (commonly de for German, sometimes de_DE) written by the project engineer who originally created or last modified the project. SIMATIC Manager reads the file at project open and compares the tag against the active Windows regional format. If the codes do not match, the regional-language guard fires and the project refuses to open.

The \GLOBAL\ folder is the project-global data area shared by all S7 programs, sources, and symbol tables inside a STEP 7 V5.x project. Markers placed here are loaded before HW Config, NetPro, and the program editor initialize. This is why no override exists inside the editor—the check happens before any user interaction.

2.1 Why the File Exists

Siemens implemented the marker in older releases to prevent commissioning engineers in non-German regions from inadvertently opening a project whose display elements, comment sets, and S7-GRAPH sequencer strings contain ANSI-1252 / ISO 8859-1 (Latin-1) German characters (ä, ö, ü, ß). Without the guard, those characters render as question marks or boxes on a Japanese, Chinese, or English (US) Windows install, silently corrupting operator screens and printed documentation. The LANGUAGE file is therefore a defensive artifact, not a license key or DRM element.

2.2 Why It Persists Across Machines

The file travels with the project archive (.zip, .s7p bundle, or *.s7l library export). Any engineer who receives the project inherits the regional lock. There is no project-level setting inside SIMATIC Manager to clear it; the file must be removed at the file-system level.

3. Prerequisites

Before executing the resolution, confirm the following:

1. The STEP 7 project folder is fully accessible and writable. The path must not be marked read-only or hosted on a network share that drops NTFS permissions.
2. You have local administrator rights on the engineering station. SIMATIC Manager writes to %TEMP%, %APPDATA%\Siemens\Automation\, and the project root on open.
3. All instances of SIMATIC Manager, S7-PLCSIM, and the S7DOS Helper Service are closed. Verify in Task Manager that S7OMSP64.exe (or the older S7OMSI.exe) is not running.
4. A full backup of the project folder exists. Copy the entire \<project_root> directory to a safe location, including all subfolders and hidden files.
5. The Windows account has the Modify NTFS right on \GLOBAL\. If the project is on a corporate share, request a temporary elevation from IT.

4. Step-by-Step Resolution

Step 1 — Archive the Project

Copy the project root to a timestamped backup folder. Include the \GLOBAL\, \S7PROGS\, \HMI\, and any \Documents subfolder.

xcopy "C:\Siemens\Projects\CustomerX" "D:\Backup\CustomerX_2025-01-15\" /E /H /K /I

Use /H to include hidden and system files, and /K to preserve attributes. Do not skip this step—the LANGUAGE file may be needed if the customer requires the regional lock restored for compliance reasons.

Step 2 — Close All Siemens Applications

Exit SIMATIC Manager, S7-PLCSIM, the S7DOS Helper Service control panel, and any open WinCC flexible / ProTool runtime windows. From a command prompt run as administrator:

taskkill /IM S7OMSP64.exe /F
taskkill /IM S7OMSI.exe /F
taskkill /IM PLCSim.exe /F
taskkill /IM S7tgtopx.exe /F

Step 3 — Locate the GLOBAL Folder

Open Windows File Explorer and navigate to the project root. The GLOBAL folder is always at the top level of a STEP 7 V5.x project:

C:\Siemens\Projects\CustomerX\
├── GLOBAL\
│   ├── LANGUAGE          <-- marker file (no extension)
│   ├── s7global\.sdf
│   └── ...
├── Station1\
├── Station2\
└── CustomerX.s7p

If the LANGUAGE file is missing, the regional guard is already disabled; the project will open without changing Windows settings.

Step 4 — Delete the LANGUAGE File

Select LANGUAGE in \GLOBAL\ and delete it. If Windows hides the file because of its no-extension status, enable View > File name extensions or delete from the command line:

cd /D "C:\Siemens\Projects\CustomerX\GLOBAL"
del LANGUAGE
dir /A

The /A switch on dir confirms the file is gone (it will not appear in the listing).

Step 5 — Restore the Native Regional Setting

Open Settings > Time & Language > Region > Regional format and set the value to the engineer's native format (for example, English (United States), Japanese (Japan), or Chinese (Simplified, China)). On Windows 10/11 the change is immediate; on older Windows 7 / Server 2008 R2 engineering stations, a sign-out is required.

Step 6 — Open the Project in SIMATIC Manager

Launch SIMATIC Manager, choose File > Open > Open Project, and navigate to the .s7p file. The regional guard will not fire because the marker file is gone.

5. TIA Portal V20 Multilingual Handling

On S7-1500 CPUs programmed with TIA Portal V20, the regional lock is not implemented as a hidden file. Instead, TIA Portal exposes the project language set, the CPU display language, and the Web server language as first-class configuration objects. The official TIA Portal V20 Multilingual (S7-1500) documentation lists three independent language pools:

The S7-1500 supports up to three simultaneous display languages selected from the project pool at compile time. The user does not need to change the Windows regional format to view any of them, and the project will not refuse to open on an English (US), Japanese, or Chinese engineering station.

5.1 Recommended Project-Language Layout for an Asian Site

This configuration eliminates the need to ever modify the Windows regional format to read project contents, and it removes the risk of breaking network-share paths that contain Japanese or Chinese characters.

6. Verification

After deleting the LANGUAGE file, perform the following checks:

1. Project Open Test: Launch SIMATIC Manager with the Windows regional format set to the native (non-German) value. Open the project. The regional error must not appear.
2. Hardware Config Test: Open HW Config on at least one station. Verify that the rack configuration loads without warning dialogs and that German characters in device names render correctly (or are absent because they were never used).
3. Symbol Table Test: Open the global symbol table (S7 Program > Symbols). Verify that comments and operator texts display with the original German umlauts. If characters appear as boxes or question marks, the project source itself was authored on a non-Latin codepage and the deletion of the marker is not sufficient—re-author the comments in TIA Portal instead.
4. Cross-Application Test: With SIMATIC Manager still open, browse to a network share that contains Japanese or Chinese folder names. Explorer must display the names without error. This confirms that the Windows regional format has not been forcibly changed to German.
5. Compile / Consistency Check: Run Station > Check Consistency on every S7 program inside the project. The check should pass with zero errors. If it reports missing PO files or symbol conflicts, restore the LANGUAGE file from backup and escalate to Siemens Technical Support.

7. Troubleshooting Matrix

8. Related Siemens Regional / Language Settings

Engineers frequently confuse the STEP 7 LANGUAGE marker with several other regional controls. The table clarifies the differences.

9. Best Practices and Preventive Measures

• Document the marker: When delivering a STEP 7 V5.x project to a customer, include a README that lists the contents of \GLOBAL\ and explains the role of LANGUAGE. The customer can then decide whether to keep the lock or remove it for their own engineers.
• Migrate to TIA Portal: TIA Portal V20 stores all text in Unicode, eliminating the marker mechanism entirely. New projects should always be created in TIA Portal; the V5.x import tool (Project > Migrate project) converts symbols, comments, and HW Config while stripping the legacy marker.
• Standardize on English (USA) source comments: Multilingual projects that use English as the source language are immune to the German-only restriction. Add the German (Germany) translation in TIA Portal's translation editor for OEM documentation if required.
• Avoid mixing regional formats on a single engineering station: If you must open both German-only and Asian-locale projects, use separate Windows user profiles and switch between them with Sign out. The Windows regional format is per-user, so this is the cleanest separation.
• Archive projects with the marker file: If the OEM requires the regional lock for contractual reasons, re-create the marker after working on the project by writing a single-byte text file named LANGUAGE into \GLOBAL\ with the contents de followed by a CR/LF.
• Check for nested markers: A single project can contain multiple LANGUAGE files if sub-projects were merged. Always run dir /S /A LANGUAGE from the project root before declaring the issue resolved.

10. Re-creating the LANGUAGE File (If Required)

If the customer mandates that the regional lock be reinstated after engineering work is complete:

cd /D "C:\Siemens\Projects\CustomerX\GLOBAL"
echo de> LANGUAGE
attrib +H LANGUAGE

The attrib +H command sets the hidden attribute, matching the typical file-system appearance when the integrator originally created it. The LANGUAGE file must contain the locale tag (de for German) followed by a line terminator; a zero-byte file is not recognized by SIMATIC Manager and will not re-enable the guard.

11. When to Escalate to Siemens Support

Escalate to Siemens Industry Online Support if any of the following applies after following the procedure above:

• The LANGUAGE file is not present in \GLOBAL\ but the error still fires. This indicates a corrupted s7global\.sdf project database; Siemens can supply a S7recover tool to rebuild it.
• Multiple LANGUAGE files exist in deeply nested sub-folders and SIMATIC Manager still references an older marker. Re-archive the entire project and request a fresh re-package from the OEM.
• The evaluation license was installed under one Windows user and the project is now being opened under another. The Automation License Manager binds to the user SID; sign in as the original user to confirm.
• Windows 11 24H2 introduces new regional-format behavior that prevents SIMATIC Manager V5.7 from launching. Apply the STEP 7 V5.7 SP1 compatibility hotfix referenced in the Siemens SiePortal regional-setting thread.

12. Summary

The "Set Regional to German" error in SIMATIC Manager is triggered by a single hidden marker file in the project's \GLOBAL\ folder. The fix is to back up the project, close all Siemens processes, delete GLOBAL\LANGUAGE, restore the native Windows regional format, and reopen the project. TIA Portal V20 removes the need for this workaround entirely by storing all project text in Unicode and exposing the language set as a first-class configuration object on the S7-1500 CPU. For long-term projects, plan a migration from STEP 7 V5.x to TIA Portal V20 to avoid the regional lock and the related Windows-update reappearance of the German locale.

FAQ