STEP 7 V5.4 SP5 'Missing Software Packages' Error on CP343-1 Lean

Problem Overview

When a STEP 7 V5.4 SP5 project that references a SIMATIC S7-300 CP 343-1 Lean communications processor (MLFB 6GK7 343-1CX10-0XE0) is opened on a workstation that lacks the matching Hardware Support Package (HSP), the dialog "Missing software packages / Required software packages are missing" is displayed. The dialog blocks edits in HW Config, prevents NetPro connection edits, and may silently purge the CP entry if the user attempts Save As with Reorganize (slow). Siemens entry 109975824 documents the underlying behaviour: "If you open a project with missing software packages, you will not be able to use the project to its full extent." The error is a project-integrity flag, not a license violation, and is resolved by aligning the workstation's installed HSP set with the package references embedded in the compressed project database (.s7p, .s7l, .s7f).

Root Cause Analysis

STEP 7 V5.x stores hardware object types as references to HSP files located under %ProgramFiles%\Siemens\Automation\HSP and registered against HKLM\SOFTWARE\Siemens\Automation\HSP. When the project was last saved on a workstation that had a specific CP HSP installed, the CP 343-1 Lean object was written with an internal type identifier that the current workstation cannot resolve. Common triggers observed in field service:

1. Project migrated from a STEP 7 V5.5 workstation (CP HSP bundled) to a STEP 7 V5.4 SP5 workstation (CP HSP optional).
2. Project archived from the integrator's PC using WinZip / 7-Zip before Save As with Reorganize, stripping the HSP cache.
3. In-place STEP 7 upgrade chain (V5.4 → V5.4 SP4 → V5.4 SP5 → HFx) without re-installing the matching CP HSP.
4. Windows 10 cumulative update (notably KB 4517389 in 1909 builds) altered .NET runtime behaviour and broke HSP registration during STEP 7 startup.
5. STEP 7 installed to a non-default path or relocated post-install, leaving the HSP index pointing to a non-existent directory.
6. Repair install of STEP 7 SP without re-running the HSP setup, producing partial HSP coverage.

Affected Versions and Compatibility Matrix

Solution Path A - STEP 7 V5.4 Hotfix 5 or V5.5 Upgrade

Siemens released Hotfix 5 (HF5) for STEP 7 V5.4 SP5 specifically to address the missing-package dialog when CP 343-1 Lean, CP 343-1, CP 343-1 Advanced, or CP 342-5 HSPs are referenced. HF5 is distributed through the regional Siemens Industry Online Support office and is not on the public download portal. The alternative path - clean migration to STEP 7 V5.5 - resolves the dialog because the CP HSP is bundled with the V5.5 DVD and is registered automatically during installation.

HF5 Acquisition and Install Procedure

1. Sign in to Siemens Online Support with your Customer Center account.
2. Navigate to STEP 7 V5.4 → Support & Downloads → Hotfixes.
3. If HF5 is not listed, request it via the regional Siemens Industry Online Support hotline. Provide the STEP 7 serial number (Certificate of License) and the installation ID from Start → SIMATIC → Information → Information on installed software.
4. Copy HF5 to a local path with administrator write access. Right-click the .exe → Run as administrator.
5. The installer stops the services S7DOS, S7EHSRV, and CCAgent before applying the patch.
6. Restart the workstation. Verify in HW Config that CP 343-1 Lean appears at SIMATIC 300 → CP 300 → Industrial Ethernet → CP 343-1 Lean.

V5.5 Migration Procedure

1. Archive the V5.4 project (File → Archive) to a network share with a dated filename.
2. Install STEP 7 V5.5 on a separate workstation or partition to validate the upgrade before committing.
3. De-archive in V5.5. HW Config prompts to update module descriptions; accept.
4. Re-compile HW Config (Station → Save and Compile) and review the consistency log.
5. Download the updated hardware configuration to the CPU (Online → Download to Target).

Solution Path B - Save with Reorganization and Reinsert CP

When a workstation upgrade is not feasible, the project can be repaired by reconstructing the CP slot manually. This is the field-proven approach when HF5 cannot be obtained in a timely manner or the workstation is locked to V5.4 SP5.

1. Open the STEP 7 V5.4 SP5 project. Acknowledge the "Missing software packages" dialog.
2. File → Save As. Enable With reorganization (slow). Click OK. The project path is renamed with a numeric suffix.
3. The dialog disappears, but the CP 343-1 Lean slot is now empty or marked Unspecified module.
4. In HW Config, identify the original CP slot (typically slot 4 or 6 of the S7-300 rack). Right-click the slot → Insert Object.
5. Browse the catalog: SIMATIC 300 → CP 300 → Industrial Ethernet → CP 343-1 Lean → 6GK7 343-1CX10-0XE0. Select firmware V2.x or V3.x to match the physical module.
6. Insert the CP. When HW Config offers to copy properties from an identical module, select the slot the CP previously occupied.
7. Open NetPro. S7 connections previously bound to the original CP appear with a ? marker. Right-click → Insert New Connection and re-create the S7 connection. Connection IDs, partner IDs, and TSAPs can be transferred from a project archive (File → Retrieve).
8. Station → Save and Compile. Review the consistency log for unresolved connections.

Restoring CP Properties from Project Archive

If you have an archived copy of the project prior to corruption, retrieve it to a temporary directory. Open the archive's HW Config and capture the following for exact re-entry:

• CP order number (MLFB): 6GK7 343-1CX10-0XE0
• Firmware version: V2.0, V2.1, or V3.0 (must match physical module label)
• IP address, subnet mask, default router
• MAC address (factory assigned; do not overwrite)
• S7 connection partner and TSAPs
• Configured port: RJ45 Port 1 (10/100 Mbit/s, auto-negotiation)
• Connection resource count: max 16 S7 connections per CP

Mismatched firmware pointers between project and physical module trigger a "Module does not match configuration" fault during download.

STEP 7 Installation Repair Considerations

When HF5 and project repair do not resolve the issue, the underlying STEP 7 installation may be corrupted. Microsoft documentation describes scenarios in which MSI/MSP installers leave orphaned registry entries after Windows updates, particularly on Windows 10 builds that changed component servicing.

Repair Upgrade Path

1. Obtain the original Windows 10 ISO matching the installed build via the Media Creation Tool.
2. Mount the ISO and run Setup.exe from within the running OS (do not boot from USB - that performs a clean install).
3. Select Keep personal files and apps. This performs a repair upgrade that replaces system files without touching user data or applications.
4. After reboot, re-apply Windows updates one by one to isolate the offending update (a frequent offender on Siemens workstations is KB 4517389).
5. Re-install STEP 7 V5.4 SP5 and HF5 with administrator privileges.
6. Re-register HSPs manually if HW Config still rejects them: from an elevated CMD run regsvr32 "%ProgramFiles%\Siemens\Automation\HSP\hsp.dll".

HSP Re-registration Reference

Step-by-Step Recovery Procedure

1. Confirm CP type and order number. Cross-check the physical module label against the HW Config catalog: 6GK7 343-1CX10-0XE0 = CP 343-1 Lean, Ethernet, S7 communication only, no IT / PROFINET gateway.
2. Capture the project state. File → Archive to a network share. Name the archive with date and CP version for traceability.
3. Identify installed HSPs. Start → SIMATIC → Information on installed software. Confirm that "CP 343-1 Lean" appears with a release date matching the STEP 7 version.
4. Obtain HF5 or upgrade. Request HF5 from Siemens regional support, or migrate the engineering workstation to STEP 7 V5.5.
5. Apply HF5 or run V5.5 setup. Restart, then verify the CP appears in the HW Config catalog.
6. Re-open the project. The "Missing software packages" dialog must not appear.
7. Re-validate NetPro. Right-click the CP → Object Properties → confirm IP, subnet, and S7 connection table match the as-built network.
8. Compile and check consistency. Station → Check consistency. Resolve undefined partners or duplicate connection IDs.
9. Download to target CPU. Online → Download to Target → To Target System. Enable Module reset only if the CPU is in STOP and no process-critical retain data must be preserved.
10. Verify online. Open Online → Module Information on the CP and confirm the diagnostic buffer contains no fault entries since the download.

Verification and Commissioning Checks

Troubleshooting Matrix

Preventive Measures

• Maintain a master STEP 7 installation image (Acronis / Veeam) for engineering workstations. Restore the image rather than repairing corrupted HSPs.
• Document the exact STEP 7 version, SP, HF, and HSP list in each project header comment. Siemens provides a template in the project properties dialog.
• Use SIMATIC Logon / Version Control (e.g., SVN) to lock project files against inadvertent Save As Reorganize operations.
• Schedule a workstation image refresh every 12 months; STEP 7 V5.x is no longer in active development and security patches frequently break HSP registration.
• Always request an archive of the source project from integrators with a sidecar text file listing all installed HSPs and their release dates.
• Disable Windows automatic restart after updates on engineering workstations; manual update scheduling avoids mid-edit disruptions.
• Block Windows feature upgrades via Group Policy until validated in a VM image.

Related Issues and Edge Cases

• CP 343-1 vs CP 343-1 Lean confusion. The Lean variant (6GK7 343-1CX10-0XE0) supports S7 communication and UDP / TCP broadcast only. It does not include the IT functions (HTTP, FTP, SNMP, e-mail) of the standard CP 343-1 (6GK7 343-1EX11-0XE0). Selecting the wrong HSP causes the module to be insertable but its firmware tab greyed out.
• PROFINET IO controller migration. If the CP was used as a PROFINET IO controller, only CP 343-1 Advanced (6GK7 343-1GX21-0XE0) supports this. The Lean variant cannot act as a PROFINET IO controller; attempting to enable PN-IO on the Lean produces a "Function not supported" dialog.
• Multi-project with several CPs. When multiple CP types (343-1 Lean, 343-1, 343-1 Advanced) coexist in a project, all HSPs must be installed or the "Missing software packages" dialog persists even after partial HSP installation.
• Virtualization pitfalls. Running STEP 7 V5.4 inside a Windows 10 VM with dynamic memory allocation can trigger HSP detection failures during STEP 7 startup. Lock VM memory and disable dynamic allocation in VMware Workstation / Hyper-V settings.
• Locale mismatch. Projects created on a German-locale workstation and opened on an English-locale workstation occasionally report missing package names with different translations. The underlying binary object is identical; the dialog is a presentation artifact.
• Connection resource exhaustion. The Lean variant supports a maximum of 16 S7 connections. Projects approaching this limit from earlier CP firmware versions may fail consistency checks after CP reinsertion if connection IDs were not preserved.

FAQ