S7-PLCSIM Advanced V2.0 SP1 Installation: WinPcap 4.1.3 Fix

David Krause14 min read
SiemensTIA PortalTutorial / How-to
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

S7-PLCSIM Advanced V2.0 SP1 Installation: Resolving the WinPcap 4.1.3 Prerequisite

1. Overview of S7-PLCSIM Advanced V2.0 SP1

SIMATIC S7-PLCSIM Advanced is Siemens' software-based virtual controller that simulates S7-1500 and ET 200SP CPUs on a PC. Version 2.0 SP1 was released effective October 26, 2018, and remains a reference build for many engineers still running TIA Portal V15.1 environments.

Unlike the older S7-PLCSIM (which integrated directly into the TIA Portal project tree), PLCSIM Advanced runs as a standalone Windows service and exposes the simulated controller through TCP/UDP on a configurable network interface. This service-oriented architecture is exactly what introduces WinPcap 4.1.3 as a hard prerequisite: the simulator needs raw socket access to a virtual or physical Ethernet adapter to broadcast PROFINET, S7 communication, and OPC UA traffic so that the TIA Portal HMI/PLC connection, the PLCSIM Advanced API, and third-party SCADA clients can discover the simulated CPU.

Official Siemens trial download portal entries confirm the release and scope:

V2.0 SP1 ships as a self-extracting archive. Many first-time installers fail at the WinPcap prerequisite stage because the WinPcap 4.1.3 .exe is not exposed on the Siemens download portal itself – it is bundled in the Support sub-folder of the unpacked installer tree, which is normally only reached when installing from the shipped DVD image.

Important: If you attempt a direct install from the Siemens download portal entry without first extracting the archive contents to disk, the WinPcap prerequisite check will block the installation with no obvious path to the missing dependency.

2. System Requirements and Prerequisites

Before installing S7-PLCSIM Advanced V2.0 SP1, verify the workstation meets the following prerequisite matrix. Any deviation outside these bounds typically results in cryptic DLL load failures during the S7-PLCSIM Advanced service start, not in the setup itself.

PLCSIM Advanced V2.0 SP1 prerequisite matrix
Component Minimum Recommended Notes
Operating system Windows 10 Pro/Enterprise 64-bit (1809 or later) Windows 10 20H2+ or Windows 11 Pro 32-bit OS not supported
CPU Quad-core x64, 2.0 GHz 6-core / 12-thread x64, 3.0+ GHz Hyper-V must remain enabled
RAM 8 GB 16 GB or more Each instance consumes ~512 MB–2 GB
Disk 5 GB free SSD with 20+ GB free Temp folders grow during simulation
TIA Portal V15.1 Update 2 or higher V15.1 + latest HSP Source projects compiled against V15.1
.NET .NET Framework 4.7.2 .NET Framework 4.8 Required by TIA Portal host
Packet driver WinPcap 4.1.3 (32-bit and 64-bit) WinPcap 4.1.3 from Siemens archive Hard prerequisite for V2.0
Network adapter Ethernet, TCP/IPv4 enabled Dedicated adapter for simulation Disabling adapter breaks PLCSIM
Hyper-V Enabled (Windows feature) Enabled with virtual switch Required for PLCSIM Advanced VM

2.1 Required Software Stack (In Install Order)

  1. Windows 10/11 64-bit with the latest cumulative update.
  2. Microsoft .NET Framework 4.7.2 or higher.
  3. WinPcap 4.1.3 (both x86 and x64) — the focus of this article.
  4. TIA Portal V15.1 (or matching version) plus the required Hardware Support Packages (HSPs) for the simulated CPU family.
  5. SIMATIC S7-PLCSIM Advanced V2.0 SP1 (trial or licensed).
  6. Optional: S7-PLCSIM Advanced Controller (subscription/license key).

3. The WinPcap 4.1.3 Prerequisite Problem

The PLCSIM Advanced setup binary is built around an InstallShield bootstrapper. When launched, the setup performs a dependency scan and demands two payload components:

  1. WinPcap 4.1.3 (x86) — WinPcap_4_1_3.exe
  2. WinPcap 4.1.3 (x64) — WinPcap_4_1_3_x64.exe

On the original Siemens DVD release, these payloads sit inside D:\Support\WinPcap\ next to the main setup. The setup looks for them under a relative Support directory of the active extraction root, then on the system %TEMP% staging area, and finally aborts if neither exists.

When you download the trial from the Siemens Support portal, the download itself is just the bootstrapper .exe. Running it without first pre-extracting means Windows stages the payload to %TEMP%\{GUID} and the setup silently cleans it up at the end. Most installers encounter the sequence below:

  • Setup launches → checks %TEMP% → checks Support\ relative path → not found → aborts with "WinPcap 4.1.3 could not be found".
  • Installer searches the web for WinPcap → finds winpcap.org, which still hosts the WinPcap 4.1.3 binaries, but the project has been deprecated since 2018 and hosts a known DLL search-order hijacking advisory.
  • Engineers attempt to install from winpcap.org → concern grows about loading an unsigned driver on a workstation that also connects to plant networks.
Security context: WinPcap 4.1.3 was published by Caceo / Riverbed Technology and is signed, but its installer writes packet.dll and wpcap.dll to C:\Windows\System32. Because the directory is writable for SYSTEM processes, any pre-existing DLL in the search path (e.g., a Plant-Floor drop folder reachable via PATH) can shadow the signed binaries — the classic winsrv-2018-0086 class issue. Mitigations include keeping WinPcap installation local, restricting write access to %PATH% directories, and patching to Npcap (the maintained successor) where PLCSIM Advanced versions permit.

3.1 WinPcap Versions vs. PLCSIM Advanced Compatibility

PLCSIM Advanced version Required packet driver Behavior with alternatives
V2.0 (initial) WinPcap 4.1.3 only Npcap breaks — installer enforces WinPcap
V2.0 SP1 WinPcap 4.1.3 Npcap with WinPcap-compat API: "unverified"
V3.0 / V4.x Npcap 1.x (recommended) or WinPcap 4.1.3 Setup ships Npcap installer; WinPcap supported

4. Pre-Installation Extraction Procedure (The Solution)

The reliable, field-tested workflow to satisfy the WinPcap prerequisite without fetching it from a third-party site is to extract the full installer payload to a known folder, then run the bundled Support components manually before invoking the main setup. This is the same procedure shipped with the DVD media and recommended in Siemens' official FAQ.

4.1 Step-by-Step Extraction Procedure

  1. Download S7-PLCSIM_Advanced_V2_0_SP1.exe from the Siemens Support portal entry (Entry ID 109758848).
  2. Create an empty working folder with no spaces in the path, e.g.:
    C:\Install\PLCSIM_V20SP1\
  3. Do not run the downloaded .exe yet. Move it into the working folder.
  4. Open a command prompt as Administrator:
C:\> cd C:\Install\PLCSIM_V20SP1
C:\Install\PLCSIM_V20SP1> S7-PLCSIM_Advanced_V2_0_SP1.exe -extract

The -extract switch (InstallShield) unpacks every payload file, including the Support sub-folder, and exits without installing anything. You can also right-click → Extract… if a self-extraction dialog appears, but the command-line form is the most reliable on Windows 10 / 11.

  1. Open the working folder in Windows Explorer. You should see the following layout:
    C:\Install\PLCSIM_V20SP1\
      ├── setup.exe
      ├── setup.ini
      ├── Autorun.inf
      ├── ...
      └── Support\
            ├── WinPcap_4_1_3.exe        (32-bit)
            └── WinPcap_4_1_3_x64.exe    (64-bit)
  2. Press ⊞ Win + R, type %temp%, and press Enter. Delete any ~setup / InstallShield staging folders from prior aborted attempts. This avoids the setup picking up a stale Support directory from a previous extraction.
  3. Right-click Support\WinPcap_4_1_3.exe → Run as administrator. Repeat for Support\WinPcap_4_1_3_x64.exe if your OS is 64-bit (it normally is, since PLCSIM Advanced V2.0 is 64-bit only).
  4. Accept the WinPcap license, leave the default install path (C:\Program Files (x86)\WinPcap), and complete both installers.
  5. Verify WinPcap service registration:
    C:\> sc qc npf
    [SC] QueryServiceConfig SUCCESS
    
    SERVICE_NAME: npf
            TYPE               : 1  KERNEL_DRIVER
            START_TYPE         : 2  AUTO_START
            ERROR_CONTROL      : 1  NORMAL
            BINARY_PATH_NAME   : system32\DRIVERS\npf.sys
            LOAD_ORDER_GROUP   :
            TAG                : 0
            DISPLAY_NAME       : NetGroup Packet Filter Driver
            DEPENDENCIES       :
            SERVICE_START_NAME :
    If the npf Kernel Driver shows START_TYPE: 2 AUTO_START, WinPcap is correctly installed.
Administrative privilege required: WinPcap installs the npf.sys kernel driver and registers a service. If you are not on an account with admin rights, the installer will fail silently on the service creation step and the PLCSIM Advanced setup will then report a corrupted WinPcap install.

4.2 Alternative: Extract From %TEMP% After An Aborted Setup

If you have already launched the bootstrapper once and it self-extracted into %TEMP% before aborting, the Support\ folder is still available there for the duration of the session. The sequence is:

  1. Launch S7-PLCSIM_Advanced_V2_0_SP1.exe with no arguments.
  2. The setup begins extracting content to a GUID-named folder under %TEMP%. While the installer is running (or right after it self-extracts), press ⊞ Win + R → %temp%.
  3. Open the most recent folder whose name starts with {xxxxxx} and ends with S7-PLCSIM Advanced V2.0.
  4. Inside, navigate to Support\. The two WinPcap installers will be present.
  5. Run them as administrator, then cancel the setup wizard.

This is the path most field engineers end up using because the manual states "Support folder on DVD" without explaining the procedure for online downloads.

5. Installation Steps

With WinPcap satisfied, complete the PLCSIM Advanced install using the same extracted folder.

  1. In C:\Install\PLCSIM_V20SP1\, right-click setup.exe → Run as administrator.
  2. Select language (English / German / French / Italian / Spanish / Japanese / Chinese).
  3. Accept the Siemens EULA and the WinPcap / Npcap driver EULA.
  4. Choose installation type:
    • Typical: installs PLCSIM Advanced service, API DLLs, and example projects.
    • Custom: allows excluding the documentation CHM, web-help, and the WinPcap pre-check (do not exclude WinPcap on a clean machine).
  5. Set target directory. The default is C:\Program Files\Siemens\Automation\PLCSIM Advanced\. Avoid paths with spaces if you plan to call the API from PowerShell — the COM wrapper can mishandle path quoting.
  6. If a trial license is being used, the dialog prompts for the TIA User Software Download Contract information used to generate the trial key. The key is delivered by email within minutes.
  7. Allow the InstallShield wizard to complete.
  8. Restart the workstation. The PLCSIM Advanced service (S7-PLCSIM Advanced) depends on Hyper-V and the WinPcap npf driver; both must be initialized at boot.

5.1 Post-Install File System Layout

C:\Program Files\Siemens\Automation\PLCSIM Advanced\
  ├── bin\
  │   ├── PLCSIMAdvancedService.exe
  │   └── S7-PLCSIM-Advanced-x64.dll
  ├── Api\
  │   ├── PLCSIMAdvancedApi.dll           (.NET wrapper)
  │   └── PLCSIMAdvancedApi.tlb            (COM type library)
  ├── Config\
  │   └── PLCSIMAdvanced.xml
  ├── Examples\
  │   └── *.ap* (TIA Portal example projects)
  └── Help\
      └── PLCSIM_Advanced.chm

6. WinPcap Security Considerations and Alternatives

Engineers rightly hesitate to install kernel-level packet capture drivers from a third-party site. Below is a decision tree used in plant environments.

6.1 Decision Matrix

Option Source Signed Maintained PLCSIM Adv V2.0 SP1 support Plant-floor suitability
WinPcap 4.1.3 from Siemens archive Bundled in installer Support folder Yes (Caceo / Riverbed) No (deprecated 2018) Supported Acceptable for engineering VLAN
WinPcap 4.1.3 from winpcap.org Third-party mirror Yes No Supported Caution — same DLL-hijack risk
Npcap (Nmap Project) nmap.org/npcap Yes (Nmap LLC) Active V3.0+: officially supported Preferred when licensing allows
Wireshark "Npcap with WinPcap-compat" Bundled with Wireshark installer Yes Active V3.0+: verified with Wireshark 3.x Preferred on engineer workstations

6.2 Hardening the WinPcap Installation

  • Install WinPcap from the Siemens-bundled location only, never from a web search result.
  • Disable the WinPcap remote capture server (rpcapd) — PLCSIM Advanced does not use it. The installer adds rpcapd.exe -b -d registration; verify it is set to disabled:
    C:\> sc qc rpcapd
    [SC] QueryServiceConfig SUCCESS
    
    SERVICE_NAME: rpcapd
            START_TYPE         : 4  DISABLED
  • Restrict C:\Windows\System32 ACLs to SYSTEM/Administrators only. Block write inheritance from Users.
  • If the workstation also runs OPC UA clients, keep PLCSIM Advanced network adapter on a separate, non-routable subnet (e.g., 192.168.0.0/24 with no gateway).
  • On multi-boot or hypervisor workstation, isolate the PLCSIM VLAN behind a virtual switch with DHCP disabled.

6.3 Upgrading to PLCSIM Advanced V3.0 / V4.x For Long-Term Support

Siemens V3.0 onward ships Npcap installer inside its Support folder, removing the WinPcap dependency entirely. If your engineering environment allows migrating to TIA Portal V16+ and PLCSIM Advanced V3.0+, plan the migration. V2.0 SP1 remains the lowest-cost option for legacy V15.1 workstations.

7. TIA Portal Integration Configuration

After PLCSIM Advanced V2.0 SP1 installs, configure TIA Portal to use the external simulator.

  1. Open the TIA Portal project.
  2. Right-click the PLC device (e.g., PLC_1 [CPU 1515-2 PN]) in the project tree.
  3. Select Start simulation (PLCSIM Advanced). If the menu item is greyed out, the PLCSIM Advanced service has not started — check services.msc for S7-PLCSIM Advanced.
  4. In the PLCSIM Advanced Interface Selector dialog, choose the network adapter. The drop-down shows every adapter that WinPcap can attach to. Pick the simulation adapter or a dedicated Ethernet NIC.
  5. Click Start. The PLCSIM Advanced compact view launches, showing the simulated CPU with green LEDs once the connection is established.
  6. If the LEDs stay amber, verify npf is loaded:
    C:\> sc query npf
    The state should be RUNNING.

7.1 Connection Parameters PLCSIM Advanced Exposes

Parameter Default Range / Notes
TCP port (S7 communication) 102 1–65535. Must not collide with another service.
Subnet ID (IP routing) 192.168.0.1/24 Matches the chosen adapter subnet.
API port (REST-like) 49152 Used for instance control.
PROFINET device name plcsim-adv- Must match TIA Portal PROFINET device name.
Maximum instances 1 (trial), 16 (license) Each runs in a Hyper-V container.

7.2 Calling the API from PowerShell

# Add the .NET wrapper shipped with PLCSIM Advanced V2.0 SP1
Add-Type -Path "C:\Program Files\Siemens\Automation\PLCSIM Advanced\Api\PLCSIMAdvancedApi.dll"

# Create a new simulated CPU instance
$instance = New-Object Siemens.Simatic.S7PlcSim.Advanced.ControllerInstance
$instance.Start("S7-PLCSIM", "192.168.0.1", "255.255.255.0")

# Wait for RUN
while ($instance.OperatingState -ne "Run") { Start-Sleep -Milliseconds 200 }
Write-Host "Simulated CPU reached RUN state"

8. Verification and Testing

Once installed, run a four-step verification to confirm the simulator is functionally correct on the workstation.

  1. Service check:
    C:\> sc query "S7-PLCSIM Advanced"
    SERVICE_NAME: S7-PLCSIM Advanced
            STATE              : 4  RUNNING
  2. Driver check:
    C:\> sc query npf
            STATE              : 4  RUNNING
            TYPE               : 1  KERNEL_DRIVER
  3. TIA Portal connectivity: In the TIA project, click Go online. Status should turn Online (RUN) within 10 s. If it remains Online (STOP), the simulated CPU is halted but reachable — use Start CPU on the PLCSIM Advanced compact view.
  4. API round-trip: Open PowerShell as Administrator, run the snippet in section 7.2. The instance should report OperatingState = Run.

8.1 Common HMI Test Cycle

  1. In TIA Portal, launch a WinCC RT Advanced instance targeting the simulated PLC.
  2. Toggle a bit in the simulator (e.g., %I0.0).
  3. Watch the HMI tag update on screen within 200 ms (typical cycle).
  4. Force a PLC stop from the PLCSIM Advanced compact view — the HMI should report connection disrupted within 5 s (default watchdog).

9. Troubleshooting Matrix

Symptom Likely root cause Verification Corrective action
"WinPcap 4.1.3 could not be located" at setup Support folder missing because installer was run, not extracted Check %temp%\{GUID} for prior staged payloads Re-extract with -extract switch, run WinPcap manually
PLCSIM Advanced compact view never finishes "starting" npf driver not loaded sc query npf → not running Re-install WinPcap, restart — check npf starts automatically
"Interface not found" in TIA Portal PLCSIM selector WinPcap bound to no adapters pcap_findalldevs via WinPcap diagnostic Enable DHCP on selected adapter, or assign a static IPv4 address
Hyper-V virtual switch error on instance start Hyper-V not installed, or VBS enabled without Hyper-V systeminfo | find "Hyper-V" Install Hyper-V Windows feature, reboot
WinCC RT cannot reach simulated CPU Subnet mismatch between TIA project and PLCSIM Advanced Compare PROFINET subnet settings Use same subnet / disable WinCC RT firewall exception
"License missing or expired" on compact view Trial key not activated or expired Check Automation License Manager Re-import the .zip license key from Siemens email
Setup aborts with 0x80070005 UAC elevation lost mid-install Event Viewer → Application log Disable UAC prompting for installer only, or run elevated from clean boot
"PLCSIM Advanced API not registered" Custom install excluded API DLL Check C:\Program Files\Siemens\Automation\PLCSIM Advanced\Api Modify installation, select API components
Compile error 0x0001 in TIA after download Project compiled against newer TIA version than PLCSIM Adv supports Check TIA project version vs PLCSIM Advanced V2.0 SP1 release notes Re-compile project against V15.1 or upgrade PLCSIM Advanced
Network adapter dropdown empty WinPcap ran in compat mode but did not rebind netsh interface show interface Reboot after WinPcap install

10. Commissioning Checklist

Use this printable checklist during engineering workstation handover.

  • ☐ Windows 10/11 64-bit with Hyper-V feature installed.
  • ☐ .NET Framework 4.7.2+ installed and patched.
  • ☐ TIA Portal V15.1 Update 2+ installed.
  • ☐ PLCSIM Advanced V2.0 SP1 installer downloaded from Siemens Support portal.
  • ☐ Installer extracted with -extract to a non-spaced path.
  • ☐ WinPcap 4.1.3 (x86 and x64) installed from Support folder.
  • ☐ npf driver set to AUTO_START and running.
  • ☐ PLCSIM Advanced service running.
  • ☐ TIA Portal → Start simulation → instance reachable.
  • ☐ WinCC RT / HMI test cycle green.
  • ☐ WinPcap remote capture disabled (sc qc rpcapd = DISABLED).
  • ☐ Trial license key imported (if applicable).

FAQ

Where is the WinPcap 4.1.3 installer in the Siemens download?

The WinPcap_4_1_3.exe files are bundled inside the Support\ folder of the extracted PLCSIM Advanced V2.0 SP1 installer. Run the downloaded .exe with the -extract switch (e.g., S7-PLCSIM_Advanced_V2_0_SP1.exe -extract) to a folder without spaces, then run both WinPcap installers from Support\ as administrator before launching setup.exe.

Is installing WinPcap from winpcap.org safe on a control-network PC?

The WinPcap 4.1.3 binaries on winpcap.org are signed by Riverbed, but the package is deprecated since 2018 and historically subject to DLL search-order hijacking on C:\Windows\System32. The recommended path is to install WinPcap from the Siemens Support folder instead, disable the unused rpcapd service, and restrict ACLs on System32. For new deployments, migrate to PLCSIM Advanced V3.0+ which uses signed Npcap.

Can I use Npcap instead of WinPcap with PLCSIM Advanced V2.0 SP1?

V2.0 SP1's installer hard-requires WinPcap 4.1.3 and does not register Npcap's WinPcap-compat API. Some users have reported that running Npcap in WinPcap-compat mode allows the TIA Portal connection, but it is not officially qualified by Siemens. For guaranteed support, stick to WinPcap 4.1.3 on V2.0 SP1 and switch to Npcap when migrating to V3.0 or later.

What is the exact PLCSIM Advanced V2.0 SP1 release date?

The Trial download became effective on October 26, 2018, per Siemens Support entry ID 109758848.

How many simulated CPUs can run simultaneously under V2.0 SP1?

A trial license allows one simulated instance. A full license supports up to 16 concurrent instances, each running in its own Hyper-V container with its own IP address on the chosen subnet.

Back to blog