Opening S7-300 Projects from Windows Explorer: .S7P File Setup

Overview

Siemens S7-300 projects under STEP 7 V5.x are stored on disk as a folder tree, not a single archive. The folder is identified by a small marker file with the .S7P extension that the SIMATIC Manager uses to recognise the directory as a project. By default, double-clicking the folder in Windows Explorer opens it as an ordinary directory listing - the project is not loaded into the Manager. For maintenance technicians who keep dozens of project folders in a central archive, this default behaviour is the single most common cause of "I clicked the folder and got nothing" tickets.

This guide covers four reliable ways to start a STEP 7 V5.x project directly from a file manager, a desktop shortcut, a Microsoft Excel hyperlink, or an automation script:

1. Windows file association for the .S7P extension (the cleanest, fleet-deployable option)
2. Direct command-line invocation of S7tgtopx.exe with the project path (for shortcuts and pinned taskbar entries)
3. Excel hyperlinks built around the file:// URL scheme (for plant-wide project indexes)
4. Batch, PowerShell, and VBA automation (for scheduled tasks, logon scripts, and macro-driven archives)

All four methods rely on the same internal contract: pass the path of the .S7P file as the first argument to S7tgtopx.exe. The Manager opens, reads the marker file, and loads the project database.

S7-300 Project File Anatomy and Storage Layout

A STEP 7 V5.x project lives in its own directory. The default install puts it under C:\Program Files\Siemens\STEP7\S7Proj\, but production projects are usually relocated to a network share. Inside the project root sits the .S7P marker, plus the sub-folders that hold the actual engineering data:

C:\Siemens\Projects\Plant_North\
├── Plant_North.S7P          <-- marker, ~2 KB; identifies folder as a project
├── Global\                  <-- cross-project symbols, sources
│   ├── LanguageDB\
│   ├── Symbols\
│   └── ...
├── S7Prog\                  <-- the S7 program(s) themselves
│   ├── Blocks\
│   ├── Sources\
│   ├── STL\
│   └── ...
├── IM\                      <-- interface / module data for HW Config
├── Symbols\                 <-- project-local symbol table
├── offlines\                <-- snapshot of online view from last session
├── online\                  <-- cached PG-side view of PLC state
├── Logs\                    <-- diagnostic logs (post V5.5)
└── ...

The .S7P file is a binary pointer that names the project and links to the Access-compatible MDB file holding the cross-reference, symbol, and block metadata. If the marker is missing or renamed, the Manager will not see the folder as a project. If the MDB is corrupted, the Manager opens the project but reports Project database inconsistent on first load - the marker is still essential.

Default STEP 7 install layout for the launchers (relevant entries only):

C:\Program Files\Siemens\STEP7\
├── S7BIN\
│   ├── S7tgtopx.exe         <-- SIMATIC Manager (the only one you need)
│   ├── S7WbfX.exe           <-- Hardware Config (HW Config)
│   ├── S7LF4XEX.EXE         <-- LAD / FBD / STL editor
│   ├── S7EPATX.exe          <-- Symbol Editor
│   ├── S7ARCHVX.EXE         <-- Archive / Retrieve tool
│   └── ...
├── S7Proj\
│   ├── ProjectA\
│   │   ├── ProjectA.S7P
│   │   ├── Global\
│   │   ├── S7Prog\
│   │   └── ...
│   └── ProjectB\
│       ├── ProjectB.S7P
│       └── ...
└── ...

The exact S7BIN path varies slightly between STEP 7 V5.4, V5.5, V5.6, and V5.7. The Manager executable name is stable across all of them, which is the only filename you need to reference in the registration steps below.

Prerequisites and Permissions

• STEP 7 V5.x installed (verified on V5.5 SP4, V5.6, and V5.7). TIA Portal uses a different project model (.ap15 / .ap16) and a different launcher; it is not covered here.
• SIMATIC Manager at the default path C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe. If installed elsewhere, substitute the actual path in every command below. The path may be C:\Program Files (x86)\Siemens\STEP7\S7BIN\ on older 32-bit STEP 7 builds.
• Local Administrator rights on the workstation for the initial file association. After the initial registration, the association is stored in the registry and inherited by every user that logs on to the machine.
• Project folders stored on a local drive or a mapped network drive. UNC paths work in shortcuts and hyperlinks but require Modify permission for STEP 7 to update the offline/online view on load.
• For multi-engineer deployments, a documented convention for project folder names and a single source of truth for the path (a network share, a documentation index, or an asset database).

Method 1: Associate the .S7P Extension with SIMATIC Manager

File association is the cleanest and most portable method. Once registered, every .S7P file on the workstation launches the Manager with the parent project loaded - no path, no argument, no extra script.

Step-by-step (Windows 10 / 11, classic shell)

1. Open File Explorer and navigate to any project folder under C:\Program Files\Siemens\STEP7\S7Proj\.
2. Right-click the .S7P file (for example ProjectA.S7P) and select Open with → Choose another app.
3. Click More apps → Look for another app on this PC.
4. Browse to C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe and select it.
5. Enable the checkbox Always use this app to open .S7P files, then click OK.
6. Test by double-clicking any .S7P file. SIMATIC Manager opens with the matching project loaded, bypassing the File → Open dialog.

Step-by-step (PowerShell, deployable to many workstations)

For a fleet of engineering PCs, push the association through the registry. The script below uses HKCU to avoid HKLM\Software\Classes ACL issues on locked-down workstations:

# Run elevated once per machine, or deploy via GPO / Intune
$ext    = '.S7P'
$progId = 'STEP7.Project.1'
$app    = 'C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe'

# 1. Create the ProgID
New-Item -Path "HKCU:\Software\Classes\$progId" -Force | Out-Null
Set-ItemProperty -Path "HKCU:\Software\Classes\$progId" -Name '(Default)' -Value 'STEP 7 Project'

# 2. Define the open-command template
New-Item -Path "HKCU:\Software\Classes\$progId\shell\open\command" -Force | Out-Null
Set-ItemProperty -Path "HKCU:\Software\Classes\$progId\shell\open\command" `
                 -Name '(Default)' -Value '"' + $app + '" "%1"'

# 3. Bind the extension to the ProgID
New-Item -Path "HKCU:\Software\Classes\$ext" -Force | Out-Null
Set-ItemProperty -Path "HKCU:\Software\Classes\$ext" -Name '(Default)' -Value $progId

# 4. Verify
cmd /c 'assoc .S7P'
cmd /c 'ftype STEP7.Project.1'

Log off and back on, or run ie4uinit.exe -show, to refresh Explorer's cache. This script is the basis for any Group Policy / Intune deployment of STEP 7 to maintenance terminals. A matching Group Policy Preferences extension association can also be created under User Configuration → Preferences → Control Panel Settings → Folder Options.

Flowchart: What happens when you double-click a .S7P file

Method 2: Direct Command-Line Invocation and Desktop Shortcuts

For shortcuts, pinned taskbar entries, or batch scripts, call the Manager executable directly with the project path as the argument. The same behaviour as a file-association click is produced.

Useful command-line variants

REM Minimal footprint, useful for kiosk / control-room terminals
start "" /min "C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe" "D:\Projects\Line3.S7P" -hide

REM Pin to taskbar: this becomes the 'always open Line3' shortcut
"C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe" "C:\Siemens\Projects\Boiler_01.S7P" -hide

REM UNC path; no mapped drive letter required
"C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe" "\\fileserver\PLC_Projects\Compressor_42\Compressor_42.S7P"

REM Force offline mode for archive-only workstations
"C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe" -offline "\\archive\S7_Archive\Boiler_03.S7P"

Creating a desktop shortcut

1. Right-click on the desktop, New → Shortcut.
2. Enter the location as "C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe" "C:\Siemens\Projects\Plant_North\Plant_North.S7P".
3. Name the shortcut (e.g. Plant North - S7-300) and click Finish.
4. Right-click the shortcut, Properties, set Start in to the project folder so the Manager's File → Save As dialog defaults to the right location on first run.
5. Change the icon to C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe for a consistent look across plants.

Method 3: Excel Hyperlinks for Plant-Wide Project Indexes

Maintenance teams typically maintain a single Excel workbook that maps each plant tag (e.g. PLC-C-102) to the engineering workstation that owns the project. Hyperlinks that call the Manager directly remove the navigation step entirely and let a technician click the row that matches the panel label on the cabinet door.

Why a plain HYPERLINK to an .exe fails

Excel's HYPERLINK(target, friendly_name) interprets target as a URL, not a command line. A link that targets S7tgtopx.exe with an &-separated argument is treated as a malformed URL and the project path is never passed to the Manager. The reliable form is a file:// URL pointing at the .S7P file - the link is then handed to Explorer, which uses the file association from Method 1.

Working cell formula

For UNC paths, omit the drive letter and prefix with file://:

Sample plant index layout

Method 4: Batch, PowerShell, and VBA Automation

One-line batch launcher (drop next to each project)

@echo off
REM OpenProject.cmd - opens the project in the same folder as this script
start "" "C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe" "%~dp0%~n0.S7P"

Save the file as OpenProject.cmd inside the project folder. The %~dp0 expands to the script's directory, %~n0 to its filename without extension, so the script will open OpenProject.S7P if it sits next to it. This works even if the file association is broken.

PowerShell: bulk-open all projects in a directory

# Open every project under D:\Projects in its own Manager window
$manager = 'C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe'
Get-ChildItem -Path 'D:\Projects' -Filter '*.S7P' -Recurse | ForEach-Object {
    Write-Host "Opening $($_.FullName)"
    Start-Process -FilePath $manager -ArgumentList '"' + $_.FullName + '"' -PassThru |
        Select-Object Id, ProcessName, StartTime
}

VBA helper: hyperlink in Excel that always calls the Manager with the right path

' Place in ThisWorkbook module; assigns the hyperlink after click
Private Sub Workbook_SheetFollowHyperlink(ByVal Sh As Object, ByVal Target As Hyperlink)
    Dim sPath As String
    sPath = Target.SubAddress ' not used
    sPath = Target.Address    ' file:// URL or absolute path
    If LCase$(Right$(sPath, 4)) = ".s7p" Then
        Application.StatusBar = "Launching SIMATIC Manager for " & sPath
        Shell """C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe"" """ & sPath & """", vbNormalFocus
    End If
End Sub

The VBA form above is the only practical way to combine the friendly Excel link experience with a real command-line argument. Use it for regulated environments where the file:// form is blocked by the Office Trust Center.

Startup Parameters, Registry, and Default Behaviour

Siemens documents a set of startup switches in the STEP 7 V5.x online help, chapter Starting STEP 7 with Default Start Parameters. The table below lists the switches most useful for routine project access. Switch behaviour was tightened between V5.4 and V5.6; treat the table as a starting point and confirm against the version actually installed on the engineering station. When in doubt, consult Siemens FAQ 38487159 or the local online help on the station itself.

Registry layout written by the PowerShell script

The same keys can be placed under HKLM\Software\Classes for a machine-wide association, but HKCU is sufficient for a single user and avoids UAC prompts during the registration script.

Default-Start behaviour documented in FAQ 38487159

STEP 7 stores the path of the most recently opened project in HKCU\Software\Siemens\Automation\STEP7\V5.x\LastProject. On the first launch after install, after a service pack update, or after a forced crash recovery, the Manager opens the project from this key and ignores the %1 argument. This is why the first double-click on a freshly associated .S7P file appears to do nothing. Close the Manager, double-click again, and the project loads as expected.

Troubleshooting Matrix

Verification Procedure

1. Open a Command Prompt and run assoc .S7P. Expected output: .S7P=STEP7.Project.1 (or whatever ProgID you defined).
2. Run ftype STEP7.Project.1. Expected output: STEP7.Project.1="C:\Program Files\Siemens\STEP7\S7BIN\S7tgtopx.exe" "%1".
3. Double-click an .S7P file. The Manager opens with the project name in the title bar; the Project tree shows the S7-300 station.
4. From Excel, click the hyperlink. Confirm the same Manager instance opens (or, if none was running, a new one starts with the project loaded).
5. Close the Manager and reopen it manually. The last project should be the one you opened from Explorer, confirming the session persistence documented in FAQ 38487159.
6. From an elevated Command Prompt, run reg query "HKCU\Software\Classes\.S7P" /s to confirm the registration keys survived a reboot.

Operational Notes: Multi-User, Archives, and TIA Migration

Multi-user and network share scenarios

STEP 7 V5.x is fundamentally a single-writer application. The offlines\ and online\ sub-folders plus the project MDB are written every time the Manager loads or saves, and concurrent writes will corrupt the database. For shared engineering work, use a source-control workflow: one engineer checks out the project from a version-control repository (SVN, TFS, or a Siemens-managed MUC), edits locally, then commits. The network share stores the released archives only.

Archived projects (.zip, .arc)

Siemens distributes sample and reference projects as compressed archives. The S7ARCHVX.EXE tool in the S7BIN directory unpacks an .arc or .zip file into a regular project folder. After extraction, associate the new .S7P file as documented in Method 1. If you need to keep the project compressed, store the archive and the OpenProject.cmd from Method 4 next to it, with the batch file pointing to the extracted path - the command line accepts the path of an extracted .S7P directly.

64-bit and WOW64 considerations

STEP 7 V5.x is a 32-bit application. On 64-bit Windows the executable runs under WOW64, but file associations are still stored per-user; HKCU registration (as in the script above) avoids the HKLM\Software\Classes WOW64 virtualization issues that bite some installations. Do not redirect the Program Files install path to Program Files (x86) manually - let the installer decide based on the STEP 7 build.

Citrix and Remote Desktop Services

On a Citrix or RDS server, register the .S7P association once at the machine level (HKLM) or via Group Policy so that every user session inherits it. Avoid per-user registration - new sessions will not have the association until the user's first run of the PowerShell script, which leads to inconsistent behaviour between long-lived and short-lived sessions.

Migrating to TIA Portal

When a plant begins its TIA Portal migration, the file-association pattern is reused but the file extension and launcher change:

Re-bind the new extensions to the TIA Portal launcher; the Excel index and the desktop shortcut pattern apply unchanged.

Security, audit, and GxP

• Treat the file association as a configuration item in any GAMP-validated environment. Document the registry keys, the launcher path, and the exact project folder layout.
• For 21 CFR Part 11 deployments, route every project open through an audit-able launcher that records the user, timestamp, and project path to a write-once log. The VBA helper in Method 4 is the right place to add this logging; the Shell call can be wrapped in a function that appends to a CSV before the launch.
• Restrict write access to the network share at the ACL level. STEP 7 will not warn before writing to offlines\ on load; a user with only Read permission will see Access denied on first click.
• Add the S7BIN path and the S7Proj path to your antivirus exclusion list. The MDB and the offline cache trigger false positives in some scanners and slow project open by an order of magnitude.

FAQ