Resolving STEP 7 "Missing Software Packages..." Error on Legacy SIMATIC Systems

The "Missing Software Packages..." dialog appears when SIMATIC Manager (STEP 7 V5.x) detects that an optional package referenced in a project file (.s7p) is not installed on the engineering workstation. This document explains the root cause, enumerates the packages most commonly flagged, and provides a recovery procedure that works on legacy Windows installations, including Windows XP SP2/SP3 where newer packages refuse to install.

1. Problem Statement

When an engineer opens a STEP 7 V5.x project (file extension .s7p or .s7l) created on a different workstation, SIMATIC Manager may display a dialog reading:

Missing Software Packages... You cannot use the project fully because the following software packages are missing...

The dialog lists the package name and a recommended action ("Install"). Selecting Install launches the STEP 7 setup, which in turn blocks installation on unsupported operating systems. Engineers running Windows XP encounter an installation error before the package is registered, so the project remains partially editable: standard blocks compile, but the program sections dependent on the missing package appear greyed-out or refuse to open.

Common observable symptoms in the field:

• SCL sources display "Source cannot be compiled — required package not installed".
• F-blocks (fail-safe) cannot be edited; the safety program editor fails to open.
• Hardware catalog shows only a subset of modules; new CPU or distributed I/O types are invisible.
• Hardware Configuration (HW Config) fails with "Module type unknown" or "Cannot find GSD file".
• Right-click on station → "Object Properties" of F-CPU gives "F-library not loaded".

Reference: Why does the message "Missing Software Packages..." appear when opening a STEP 7 project?

2. Root Cause Analysis

Each STEP 7 project carries a manifest in its System Data folder that references the optional packages used during compilation. The reference is recorded by name and by version string. If the locally installed package version differs from the project manifest reference, STEP 7 surfaces the "Missing Software Packages" warning.

Three underlying causes are observed in the field:

1. Package not installed — the optional software was never installed on the engineering workstation, or was installed but the registry entry was corrupted by a partial uninstall.
2. Package version mismatch — a newer package was installed that supersedes the older one, but the older one is required because the project references version-specific APIs.
3. Operating system incompatibility — the package installer blocks installation on the host OS (typically Windows XP SP2 or older), so the engineer cannot complete the install wizard even though the package is otherwise available.

3. Affected STEP 7 Versions and Package Map

The package manifest format is consistent across STEP 7 V5.4 through V5.7. The packages most commonly reported missing in legacy projects are listed below with the catalog (article) numbers and the Windows OS support matrix.

4. Windows XP OS Compatibility Constraints

STEP 7 V5.x officially supports Windows XP Professional SP3 (32-bit) as the last-generation host. Windows XP SP2 is supported by a subset of packages, and Windows XP SP1 / Windows 2000 are unsupported. The setup routines of S7-SCL V5.6 and later explicitly check the Windows version and refuse to install if it is not on the supported list.

The check is enforced through the \Setup\SETUP.EXE wrapper which calls GetVersionEx against a hard-coded allow-list. The bypass for Windows XP is therefore impossible without modifying the installer, which is not supported by Siemens and will void the license terms.

Practical workaround matrix:

5. Resolution Path 1 — Locate the Correct Package Build

Use the Siemens Industry Online Support portal to retrieve the exact build referenced by the project manifest. Avoid downloading a newer build than the project requires; this introduces the version-mismatch class of failure on a different workstation.

1. Open SIMATIC Manager and note the package name and version string listed in the "Missing Software Packages" dialog. For example: S7-SCL V5.3 SP6.
2. Open the Siemens Support entry 109748118 for S7-SCL distribution.
3. Navigate to the "Entry list" tab and filter by Product family = STEP 7, Product = S7-SCL.
4. Download the build matching the project manifest exactly. Verify the SHA-256 of the downloaded .exe against the value published on the download page.
5. For S7 F ConfigurationPack, retrieve from entry 15208817 — confirm the SP level matches the STEP 7 base install.
6. For DP/AS-i F-Link Object Manager, retrieve from entry 24724923.

6. Resolution Path 2 — Install with Windows XP Compatibility

If the host is Windows XP and the project references a build newer than the OS supports, three options exist.

Option A — Install the matching older build

Open the Siemens Support entry and select the SP < build > tab. The site maintains an archive of historic service packs for users on legacy OS. For example, S7-SCL V5.3 SP6 is the highest build that installs on Windows XP SP2.

Option B — Use a virtualized engineering workstation

1. Install Windows XP Mode on a Windows 7 Professional host, or use VMware/VirtualBox with a Windows XP SP3 image.
2. Inside the VM, install STEP 7 V5.5 SP4 with all required packages.
3. Map the project archive folder from the host using a shared folder. Open the project from inside the VM.
4. Use the host for browser and Office productivity; use the VM exclusively for STEP 7.

Option C — Migrate to TIA Portal

If the project contains no failsafe logic, migrating to TIA Portal V17 or later preserves SCL, GRAPH, and standard ladder logic. Use the TIA Portal "Migrate project" wizard. F-blocks require manual re-authoring because the safety signature is project-specific.

7. Resolution Path 3 — Restore Missing Hardware Catalog (HW Update)

The HW Update package adds new module descriptions to HW Config. When a project references a CPU/IM/CP type not in the local catalog, HW Config reports "Module type unknown". To restore:

1. Close STEP 7.
2. Run the HW Update setup. The installer defaults to C:\Program Files\Siemens\Automation\S7HWUPDA.
3. After install, open HW Config → Options > Install HW Updates → select Install from Internet or Install from file.
4. Accept the license. Restart SIMATIC Manager.
5. Verify by re-opening the station: the missing module type now resolves.

If the workstation has no internet access, download the HW Update ZIP archive from Siemens Support entry 23836323 and place the .zip files into %ProgramFiles%\Siemens\Automation\S7HWUPDA\S7HWUPDA\Updates. Restart HW Config.

8. Resolution Path 4 — F-ConfigurationPack and Safety Library Recovery

Failsafe blocks require the F-ConfigurationPack and the corresponding F-library (for example F_LIB_V1_3.zip) to be installed. Without these, the safety program editor refuses to open F-blocks. Procedure:

1. Install S7 F ConfigurationPack from Siemens Support entry 15208817.
2. Copy the F-library .zip file referenced in the project into %ProgramFiles%\Siemens\Automation\S7FCT\F-Lib.
3. Open SIMATIC Manager → right-click the F-CPU → Object Properties > Safety.
4. Click Update F-Library. The wizard extracts the correct version into the project's Safety sub-folder.
5. Recompile the safety program. Verify the F-signature appears in the diagnostics buffer without CRC error.

9. Resolution Path 5 — DP/AS-i F-Link Object Manager

The Object Manager registers the F-Link gateway in HW Config. If the gateway icon does not appear under PROFIBUS DP > Gateways, install the Object Manager from Siemens Support entry 24724923. Restart SIMATIC Manager. The F-Link now appears as a selectable DP slave with the correct GSD revision.

10. Step-by-Step Recovery Procedure (Consolidated)

Use this checklist on any engineering workstation reporting the "Missing Software Packages" message.

1. Capture the full list of missing packages from the STEP 7 warning dialog. Screenshot the dialog for the project archive.
2. Determine the host operating system: Start > Run > winver. Confirm Windows version and service pack.
3. Cross-reference each missing package against the OS compatibility table in Section 4.
4. For packages compatible with the host, download the exact build from the Siemens Support portal. Use the entry IDs listed in Section 3.
5. For packages incompatible with the host, select Option B or C from Section 6.
6. Close SIMATIC Manager. Run each installer as Administrator. On Windows 10/11, enable compatibility mode "Windows XP SP3" only if the installer is V5.5 era or older.
7. After install, re-open the project. The "Missing Software Packages" dialog should no longer appear.
8. Verify by compiling all sources (Ctrl+F9 in SCL editor) and re-running HW Config consistency check.
9. Archive the license keys (%ProgramFiles%\Siemens\Automation\License\*.zip) before any OS migration.

11. Verification Checklist

12. Troubleshooting Matrix

13. Field-Proven Caveats and Edge Cases

Coexistence with TIA Portal: TIA Portal V17 and later can coexist with STEP 7 V5.6 on Windows 10 LTSC if the Automation License Manager is shared. Do not install TIA Portal on the same Windows XP image — it requires .NET 4.x which Windows XP cannot host.

Project archive corruption: If the package list in the "Missing Software Packages" dialog appears corrupted (non-ASCII characters, truncated strings), the project archive may be damaged. Run File > Reorganize in SIMATIC Manager to rebuild the internal structure before installing packages.

Multi-user ES: When using STEP 7 V5.6 on a Windows Server 2008 R2 with multiple engineering users, each profile requires its own license binding. Use the Floating License option in the Automation License Manager.

Language locale: The package names displayed in the warning dialog are localized to the Windows display language. Switching the display language after install does not change the package version key — the underlying registry value remains unchanged.

Anti-virus interaction: Some anti-virus suites quarantine Setup.exe from S7-SCL V5.6 because of the legacy installer behavior. Add an exclusion for C:\Program Files\Siemens\Automation before launching the setup.

14. Frequently Asked Questions