Fix TIA Portal V18 Set PG/PC Interface Missing in Windows Control Panel
After installing TIA Portal V18 (or V18 Update x) on a Windows 10/11 engineering workstation, the legacy Set PG/PC Interface applet sometimes fails to register as a Control Panel item. The executable still exists under Siemens Automation in the Start menu, but the only network adapter it lists is a generic picture with <none> next to it, and no interface can be selected, added, or assigned to an online access point. This article documents the root cause, the recommended Siemens-supplied fix (PC_Identifier), and the surrounding configuration steps needed to get a CP (PROFINET/Industrial Ethernet) interface online again.
Online: Connection failed errors.1. Problem Summary
| Attribute | Observed Value |
|---|---|
| Software | STEP 7 / TIA Portal V18 (Basic, Professional, PLCSIM optional) |
| Operating System | Windows 10 (21H2, 22H2) and Windows 11 (21H2, 22H2, 23H2) |
| Symptom 1 |
Set PG/PC Interface icon absent from Control Panel > All Control Panel Items
|
| Symptom 2 | Shortcut exists under Start > All Apps > Siemens Automation > Set PG/PC Interface
|
| Symptom 3 | Opened dialog lists a single network card with <none> and a yellow indicator |
| Symptom 4 | No TCP/IP, PROFINET, or soft-PLC interface available for selection |
| Symptom 5 | TIA Portal Online > Accessible nodes returns no devices |
2. Root Cause Analysis
The Set PG/PC Interface tool is a Win32 Control Panel applet (CPL) registered during TIA Portal / STEP 7 setup. It depends on two registry-controlled artifacts:
-
Registrable CPL file —
Siemens.TIA.PGPCInterfaceCPL.cplor the legacys7epaepaaxx.cpl, registered underHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Control Panel\CPLs. -
PC station configuration data — the
PC_Identifierregistry hive that maps installed Siemens PC modules (e.g. CP 1616, CP 1626, CP 1628, Softnet, S7DOS) to logical PC interface names such asS7ONLINEandIE PG/PC interface.
If the PC_Identifier hive is missing, corrupted, or was never created (typical on a clean Windows 11 image where the installer ran with a stripped-down user profile, or after a partial uninstall/reinstall), the applet starts but has no PC station data to populate. The visual placeholder card with <none> is the result.
%LOCALAPPDATA% redirection introduced in Windows 10 1903 and tightened in Windows 11 can cause the TIA installer to write the CPL under the invoking user but not the PC_Identifier hive under HKLM\SOFTWARE\Siemens\Automation. Re-installing TIA does not always re-create the missing hive.3. Affected Versions and Environment
| Component | Versions / Models Confirmed Affected |
|---|---|
| TIA Portal | V18, V18 Update 1 through Update 5 |
| STEP 7 (legacy coexistence) | V5.6 SP2 / V5.7 when used alongside V18 |
| SIMATIC PC modules | CP 1612, CP 1616, CP 1623, CP 1626, CP 1628, Softnet-S7 Lean/Standard, S7-1613/1623 Softnet |
| CPU families (online target) | S7-1200 (V4.x), S7-1500 (V2.x/3.x), ET 200SP/MP, SINAMICS S120/G120 |
| OS builds | Windows 10 21H2, 22H2; Windows 11 21H2, 22H2, 23H2, 24H2 |
| Hypervisor (if virtualised) | VMWare Workstation 17.x, Hyper-V Gen2 with synthetic NIC passthrough |
4. Solution Overview — Install PC_Identifier
Siemens ships a stand-alone repair tool called PC_Identifier that re-creates the missing PC station registry hive and re-registers the Set PG/PC Interface CPL. This is the manufacturer-recommended fix and is documented in Siemens Support Entry 109812676 — "PC Identifier: Information on the function and installation of the PC Identifier".
5. Step-by-Step Procedure
5.1 Prerequisites
- Local administrator rights on the workstation.
- All running TIA Portal instances closed (
Siemens.Automation.Portal.exeandS7EPAEX.EXEnot running). - Approximately 50 MB of free disk space for the unpacked installer.
- Working internet access to support.industry.siemens.com for the initial download.
5.2 Download PC_Identifier
- Open a browser and navigate to https://support.industry.siemens.com/cs/ww/en/view/109812676.
- Locate the Downloads table at the bottom of the entry.
- Download the file
PC_Identifier_Vx_x_x.exe(latest revision is recommended; it is backwards compatible with TIA V14 and newer). - Verify the SHA-256 checksum published on the Siemens entry against the downloaded file using
Get-FileHash -Algorithm SHA256in PowerShell.
5.3 Install PC_Identifier
- Right-click the downloaded
.exeand choose Run as administrator. - Accept the licence agreement.
- Leave the default install path
C:\Program Files\Siemens\Automation\PC_Identifierunchanged. - Click Install. The tool creates the registry keys under
HKLM\SOFTWARE\Siemens\Automation\PC_Identifier. - Click Finish and reboot the workstation. The reboot is required because the TCP/IP service trigger and Winsock catalog are touched.
5.4 Verify the Set PG/PC Interface CPL
- Open
Control Panel > All Control Panel Items. The Set PG/PC Interface icon should now be present. - If still missing, manually launch the applet from
C:\Program Files\Siemens\Automation\SetPgPcInterface\SetPgPcInterface.cpl(file name varies by version). - Confirm the Interface Parameter Assignment Used field shows at least one entry (e.g.
Intel(R) Ethernet Connection I219-LM <TCP/IP>) instead of<none>.
6. Configuring the PG/PC Interface Once Restored
After the applet is functional, the access point that TIA Portal uses by default is S7ONLINE. Configure it as follows:
- Open Set PG/PC Interface.
- Under Access Point of the Application, select
S7ONLINE. - Under Interface Parameter Assignment Used, select the physical or virtual PROFINET/Industrial Ethernet adapter that is wired to the target CPU, e.g.:
-
Intel Ethernet I219-LM <TCP/IP>— for onboard NICs. -
CP 1616 NDIS <TCP/IP>— for the CP 1616 PC card. -
Siemens Softnet <TCP/IP>— for the Softnet-S7 software interface.
-
- Click OK and confirm any prompts to take the bus offline momentarily.
Optional entries that are also useful for V18 mixed topologies:
| Access Point | Use Case | Recommended Interface |
|---|---|---|
S7ONLINE |
Default for S7-1200/1500 online, download, HMI tag routing | Realtek/Intel/CP onboard TCP/IP |
IE PG/PC interface |
Legacy STEP 7 V5.x routes & routing tables | CP 1616/1623/1626/1628 |
|
PROFINET IO controller (PC station with CP 1628) | CP 1628 NDIS |
PN/IE |
Symbian for WinCC Unified (PC RT) online access | Any Intel/Realtek onboard |
7. Alternative Solutions if PC_Identifier Does Not Resolve It
Run the following in order if the symptom persists after the reboot.
7.1 Re-register the CPL manually
Open an elevated PowerShell and execute:
regsvr32 "C:\Program Files\Siemens\Automation\SetPgPcInterface\s7epaepaaxx.cpl"
regsvr32 "C:\Program Files\Siemens\Automation\SetPgPcInterface\Siemens.TIA.PGPCInterfaceCPL.cpl"
Then re-check the Control Panel.
7.2 Repair TIA Portal V18
Control Panel > Programs and Features > Siemens TIA Portal V18 > Repair. This forces the installer to re-emit the registry keys. A second reboot is required.
7.3 Clear the cached user profile
If the CPL appears for other users but not the current one, delete the cached state under %LOCALAPPDATA%\Siemens\Automation\PGPCInterface and re-launch.
7.4 Firewall / Winsock corruption
TIA Portal installs a Winsock LSP (WinSock Catalog) entry for S7DOS. If a third-party security suite has stripped it, reset the catalog:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
Reboot after running the commands.
7.5 Clean re-install of the TIA Portal PC station
- Uninstall TIA Portal V18 via the Setup installer (not via Programs and Features — the Setup installer also removes the PC station).
- Delete the residual folders
C:\Program Files\Siemens\AutomationandC:\ProgramData\Siemens\Automation. - Run
CCleaneror the equivalent registry cleaner only as a last resort (manual deletion ofHKLM\SOFTWARE\Siemens\Automationis safer). - Reboot, then re-install TIA Portal V18, then re-install
PC_Identifier.
8. Verification & Field Checks
After the fix is in place, run the following checks to confirm the interface is fully functional before returning the workstation to production.
| Test | Expected Result | Tool / Command |
|---|---|---|
| Set PG/PC Interface visible in Control Panel | Icon appears, double-click launches the dialog | Manual check |
| Network adapter shown in the applet | Real NIC name, MAC address visible, no <none> suffix | Manual check |
| Accessible nodes from TIA Portal | Target CPU appears with IP and MAC | Online → Accessible nodes |
| Ping the CPU | <1 ms on the same subnet, no loss | ping 192.168.0.1 -t |
| Download hardware configuration | Successful, online status turns green | Project tree → PLC → Download to device |
| Run diagnostic buffer read | Live buffer returned, time stamps current | Online & diagnostics → Diagnostic buffer |
| PLCSIM (if used) connectivity | PLCSIM instance shows in Accessible nodes | Online → Accessible nodes → PLCSIM tab |
9. Common Related Error Codes and Messages
| Error / Message | Meaning | Mitigation |
|---|---|---|
| 0x011A — The network name cannot be found (WSA error during online) | S7ONLINE access point bound to wrong NIC | Re-assign S7ONLINE in Set PG/PC Interface |
| 0x80BF — No license for online functions | Online licence on USB stick missing or transferred | Re-seat licence dongle, restart automation licence manager |
| 0x80C8 — Connection to partner could not be established | Sub-net mismatch, firewall blocked TCP/UDP 102, 161/162 (SNMP), 34964 (PN-DCP) | Open ports, set CPU and PC in same subnet |
| 0xFFFD — Online: Interface is not assigned | Root cause of this article — PC_Identifier missing | Install PC_Identifier and reboot |
| “Set PG/PC Interface is not found in Windows Control Panel” | CPL registration missing in registry | Re-register CPL, install PC_Identifier |
| “Accessible nodes returns empty list” | No S7ONLINE assignment, no DCP broadcast, wrong VLAN | Verify access point, NIC link, DCP multicast (UDP 34964) is allowed |
10. Field-Proven Best Practices
- Always run the TIA Portal V18 setup as a local administrator, not as a domain user with temporary elevation, to avoid UAC virtualisation issues on Windows 11.
- Pre-install the .NET Framework and Visual C++ runtimes listed in the TIA Portal V18 readme before launching the Setup, especially on freshly imaged Windows 11 24H2 workstations.
- Capture a baseline of the
HKLM\SOFTWARE\Siemenshive withreg exportonce the system is known-good — invaluable for fast roll-back if a Windows update resets the hive. - For laptops that dock/undock, mark the wired adapter as priority in the Set PG/PC Interface dialog and disable the auto-fallback that TIA does on wireless interfaces.
- Disable PC Sleep and USB selective suspend in the Windows power plan to prevent the CP 1616/1626 from being marked as
<none>on resume from sleep.
11. Frequently Asked Questions
Why does TIA Portal V18's Set PG/PC Interface show only <none> on Windows 11?
The PC station registry hive (PC_Identifier) is missing or corrupted, so the applet cannot enumerate installed Siemens PC modules. Install PC_Identifier from Siemens Support Entry 109812676, reboot, and the network adapters will re-appear with their proper driver names.
Do I have to reinstall TIA Portal V18 to fix the missing Set PG/PC Interface?
No. PC_Identifier is a stand-alone repair tool that re-creates the missing registry keys without touching the TIA Portal installation. It is the manufacturer-recommended first-line fix and is faster than a full repair install.
After installing PC_Identifier, Accessible nodes in TIA Portal is still empty — what next?
Verify the S7ONLINE access point in the Set PG/PC Interface is bound to a working TCP/IP adapter, ping the CPU, allow UDP 34964 (PROFINET DCP) and TCP 102 (ISO-on-TCP) in the Windows firewall, and check that the CPU's PROFINET interface is on the same subnet as the PC.
Will PC_Identifier affect an existing STEP 7 V5.6 / V5.7 installation?
No. PC_Identifier is backwards compatible and only populates the HKLM\SOFTWARE\Siemens\Automation hive. It does not overwrite an existing STEP 7 V5.x PC station configuration. Both TIA Portal V18 and STEP 7 V5.x can coexist afterwards.
Is there a fix that does not require a reboot?
No. The PC_Identifier installer touches the Winsock catalog and the TCP/IP service trigger. A reboot is required for the new PC interface bindings to take effect. Plan the change for a maintenance window.