Downloading SIMATIC IPC Drivers: BX-39A, PX-39A, 647E Reference

Overview

This technical reference covers the consolidated SIMATIC IPC, SIMATIC Tablet PC, and SIMATIC Field PG driver package distributed through the Siemens Industry Online Support portal. The consolidated entry replaces earlier fragmented driver postings and bundles certified device drivers for SIMATIC industrial PCs running Microsoft Windows 11 IoT Enterprise LTSC 2024, Windows 10 Enterprise 2015 LTSB, Windows 8.1, and selected Linux distributions. Each release date listed in the entry tracks a new or preliminary driver drop; installing the most recent dated archive supersedes prior releases for the same operating system image.

The driver archive is structured in three logical layers so engineers can navigate quickly:

1. Device-specific drivers at the top of the entry, organized by SIMATIC IPC family.
2. Legacy driver packages for Windows 10 Enterprise 2015 LTSB and Windows 8.1, grouped after the device-specific section.
3. Linux driver packages at the end of the entry, currently covering the IPC520A family.

Driver revisions are cumulative within an OS branch. When upgrading the OS image on a SIMATIC platform, deploy the matching OS-specific package rather than mixing drivers from different OS folders or M-suffixes. The M-suffix (M3, M5, M6) on the archive name denotes the platform generation and must match the BIOS revision family on the target hardware.

The official entry can be accessed at: Drivers for SIMATIC IPC, SIMATIC Tablet PC and SIMATIC Field PG (entry 109783704).

Supported SIMATIC IPC Hardware Families

The consolidated driver entry covers the following SIMATIC families. Confirm your exact model designation (printed on the device label and reported on the BIOS main page) before selecting a driver package. Applying the wrong chipset or storage driver is the leading cause of blue-screen recovery loops on SIMATIC hardware.

SIMATIC Tablet PC and SIMATIC Field PG driver revisions are also tracked in the same entry and are typically bundled in M-series (M3, M5, M6) subfolders. The M6 designation denotes the current mainstream release; check the archive name suffix (for example, _M6_Win11LTSC2024) before applying it to a fleet.

Operating System Support Matrix

The following matrix maps each supported OS branch to the SIMATIC IPC families covered. Always match the OS branch in the driver folder name to the OS installed on the device. Mixing drivers across OS branches (for example, applying Windows 10 LTSC 2019 drivers on a Windows 11 IoT LTSC 2024 image) is a common cause of POST or Device Manager errors because of ACPI and storage stack differences.

Driver Package Layout and Revision Tracking

Each ZIP archive downloaded from the Siemens support entry follows a consistent layout. Unzip into a working directory and inspect before running any setup. Do not execute Setup.exe directly from the ZIP — extract fully first.

\SIMATIC_IPC_Drivers\
|-- \IPC_BX-39A_PX-39A_PRO\       (device-specific)
|     |-- Chipset\
|     |-- Graphics\
|     |-- Audio\
|     |-- Network\
|     |-- Storage_Raid\
|     |-- Touch\
|     |-- Watchdog\
|     '-- Setup.exe / autorun.inf
|-- \IPC_647E_847E\               (device-specific)
|     '-- ...
|-- \IPC_627E_677E\               (device-specific)
|     '-- ...
|-- \Legacy\                      (legacy driver bundles)
|     |-- Win10_2015_LTSB\
|     '-- Win8_1\
|-- \Linux\                       (Linux section at end)
|     |-- IPC520A\
|     '-- README_Linux.txt
'-- \M6_revision_history.txt

Confirm the M-suffix (M3, M5, M6) of the package matches the platform BIOS revision family. The BIOS firmware must be at or above the minimum revision listed in M6_revision_history.txt; out-of-date BIOS can prevent the driver installer from detecting devices on the PCI tree, particularly RAID controllers on 647E/847E/547J units.

Recent revision history tracked in the entry:

• 08/12/2025 – New driver package for IPC 647E/847E and IPC BX-39A/PX-39A (PRO).
• 05/09/2025 – New driver package for IPC 647E/847E and IPC BX-39A/PX-39A (PRO).
• 05/29/2025 – New driver package for IPC 647E/847E.
• 04/03/2025 / 04/14/2025 – Earlier Windows 11 IoT Enterprise LTSC 2024 preliminary packages added for the E-series and J-series families.

Always check the latest revision on the entry page before commissioning. New releases supersede prior ones for the same operating system branch. Subscribe to the entry in the Siemens Industry Online Support portal to receive change notifications.

Identifying the SIMATIC IPC Model and BIOS Revision

Before downloading, confirm the exact model and BIOS revision. Misidentification leads to applying the wrong chipset driver, which can cause a BSOD on first boot or render the RAID volume invisible on rack platforms.

1. Power on the SIMATIC IPC and enter BIOS (typically DEL or F2 at POST).
2. On the BIOS Main page, record the Product Name, System Version, and BIOS Version.
3. Cross-check the Product Name against the family list in the supported models table.
4. On the device chassis, locate the type plate (typically on the rear or side panel) and record the MLFB (order number) printed on it. The MLFB uniquely identifies the configuration and maps to a specific driver package.
5. Save an export of the BIOS settings before any change, so they can be reapplied if a BIOS update resets configuration.

Alternative identification from within Windows (Administrator PowerShell):

wmic csproduct get name, identifyingnumber
wmic bios get smbiosbiosversion, releasedate
Get-WmiObject Win32_ComputerSystem | Select-Object Manufacturer, Model, PCSystemType

From Linux (on supported IPC520A):

sudo dmidecode -t system | grep -E "Product Name|Version|Serial"
sudo dmidecode -t bios   | grep -E "Version|Release Date"
sudo lshw -short

Record both the SIMATIC family and the MLFB. Field experience shows that two units of the same product family can carry different storage controllers if ordered at different times, which dictates different storage driver branches.

Downloading the Driver Package

1. Navigate to the official Siemens Industry Online Support entry: Drivers for SIMATIC IPC, SIMATIC Tablet PC and SIMATIC Field PG (entry 109783704).
2. Apply the Entry type filter "Driver" and the Operating system filter matching the target OS (for example, Windows 11 IoT Enterprise LTSC 2024).
3. Choose the device-specific driver package corresponding to your SIMATIC IPC family.
4. For legacy environments, scroll past the device-specific drivers and download the Windows 10 Enterprise 2015 LTSB or Windows 8.1 driver package from the Legacy section.
5. For Linux support, scroll to the end of the entry and download the Linux driver package (currently includes IPC520A).
6. Verify the ZIP archive against the checksum published on the support page (SHA-256 recommended).

Driver Installation Procedure

Apply drivers in a fixed order to minimize Device Manager errors and POST failures. This order is required for any SIMATIC IPC running Windows 10 or later and is enforced implicitly by the PCI enumeration sequence.

1. Extract the ZIP to C:\Drivers\SIMATIC_IPC\<Family>. Do not run setup from a network share that uses SMB signing bypass.
2. Install the Chipset driver first. Reboot if prompted. The chipset driver exposes the correct ACPI tables and PCI interrupt routing used by all subsequent drivers.
3. Install Storage / Intel RST / RAID drivers. Reboot. This step is critical on 647E/847E/547J platforms; the boot volume is typically presented through Intel RST or an LSI/Avago MegaRAID controller.
4. Install Graphics driver. Reboot. Confirm multi-monitor topology if using PX-39A PRO or MD-57A.
5. Install Audio driver (Realtek HDA on most SIMATIC platforms).
6. Install Network drivers: Intel LAN (I219-V / I210 / I350), optional WLAN/Bluetooth, and PROFINET if equipped.
7. Install Touch / Multi-touch drivers on panel PCs only (PX-39A PRO, 477E PRO, PX-32A, 677E).
8. Install Specialty drivers: SIMATIC watchdog, GPIO, serial port extension, TPM 2.0, and IPMI/BMC where applicable.
9. Disable Windows Update automatic driver installation (Group Policy: Do not include drivers with Windows Updates) to prevent Windows Update from overwriting SIMATIC-certified drivers with generic Microsoft versions.
10. Reboot and verify with Device Manager (devmgmt.msc) that no devices show a yellow exclamation.

Driver Verification and Audit

After driver installation, run the following verification steps to confirm a clean install before commissioning the SIMATIC IPC in production.

1. Open Device Manager: devmgmt.msc.
2. Confirm zero devices flagged with a yellow exclamation. Right-click Computer, select Manage → Device Manager → View → Devices by connection to verify the device tree is complete against the platform block diagram.
3. Check that the System devices node lists the SIMATIC watchdog, GPIO, and any IPMI/BMC device present on the platform.

Run a PowerShell audit of installed driver versions, filtering for SIMATIC and Intel components:

Get-WmiObject Win32_PnPSignedDriver |
  Where-Object { $_.DeviceName -match "Siemens|Intel|Realtek" } |
  Select-Object DeviceName, DriverVersion, Manufacturer, IsSigned |
  Format-Table -AutoSize

# Confirm SIMATIC services are registered
Get-Service | Where-Object { $_.Name -match "SIMATIC|simatic" }

# Touch panel calibration tool location (panel PCs)
Test-Path "C:\Program Files\Siemens\TouchCalib\TouchCalib.exe"

Verify the RAID / storage stack on rack platforms (IPC 647E / 847E / 547J):

Get-Disk | Format-Table Number, FriendlyName, OperationalStatus, HealthStatus
Get-PhysicalDisk | Format-Table DeviceId, MediaType, BusType, HealthStatus, OperationalStatus

# Confirm Intel RST is the volume manager
Get-Service | Where-Object { $_.Name -like "*iaStor*" -or $_.Name -like "*Rst*" }

For panel PC multi-touch verification, open the SIMATIC Touch Test utility from the desktop or Start > Siemens Automation > Touch Test. Confirm at least 10 simultaneous touch points register without dropouts, and that palm rejection activates correctly.

For network adapter verification on PROFINET-equipped units:

Get-NetAdapter | Format-Table Name, Status, LinkSpeed, DriverVersion, InterfaceDescription
# Expected: Intel I219-V / I210 on standard SIMATIC platforms

# Validate PROFINET device enumeration (if TIA Portal / SIMATIC NET installed)
Get-PnPDevice | Where-Object { $_.ClassGuid -like "{4d36e972*}" } | Format-Table Status, Class, FriendlyName

Update Strategy and Rollback

SIMATIC IPC driver updates should be staged through dev → pilot → production to control fleet risk. Use the following procedure for each transition.

1. Capture baseline. Before applying a new package, run pnputil /enum-drivers > drivers_before.txt to record the current driver store. Also export the device tree:

pnputil /enum-devices /connected > devices_before.txt
pnputil /enum-drivers > drivers_before.txt
Get-WmiObject Win32_PnPEntity > pnp_full_before.xml

2. Snapshot image. Create a full disk image using the SIMATIC Image & Partition Creator or a vendor-supported backup tool. Confirm the image boots in a hypervisor or spare chassis before proceeding.
3. Apply in dev. Install the new package on one representative unit per SIMATIC family. Run a 72-hour soak test with the application stack, including watchdog timer self-test, RAID rebuild simulation (for rack units), and panel touch calibration (for panel units).
4. Roll back if needed. Use Device Manager → Device → Properties → Driver → Roll Back Driver per device, or restore the full disk image for a clean revert. To remove a driver from the store:

pnputil /delete-driver oem<NNNN>.inf /uninstall /force

5. Promote to pilot. Deploy to a small production subset (typically 3–5 units per family) for one to two weeks. Monitor Windows Event Viewer for hardware errors and SIMATIC service restarts.
6. Promote to fleet. Schedule a maintenance window. Deploy via your standard image management process (SIMATIC Image & Partition Creator, SCCM, Ivanti, or equivalent).

Linux Driver Deployment (IPC520A)

The Linux section at the end of the consolidated entry currently lists the IPC520A. Other SIMATIC families with Linux support are typically delivered through the distribution vendor (mainline kernel) rather than through this Siemens entry. When deploying Linux on IPC520A:

1. Confirm the kernel version against the README_Linux.txt compatibility table shipped with the package. Most IPC520A Linux deployments target a vendor-supported LTS kernel.
2. Install the SIMATIC GPIO and watchdog drivers via DKMS if included:

tar -xf simatic-gpio-1.x.tar.gz
sudo dkms add ./simatic-gpio-1.x
sudo dkms build simatic-gpio/1.x
sudo dkms install simatic-gpio/1.x
sudo modprobe simatic-gpio
sudo modprobe simatic-watchdog

3. Enable the SIMATIC watchdog service to auto-reboot on kernel panic. Set the timeout above the longest expected application restart:

sudo systemctl enable simatic-watchdog.service
sudo systemctl start simatic-watchdog.service
# Set timeout to 120 s for commissioning, reduce to 60 s in production
sudo simatic-watchdog --timeout 120

4. Verify loaded modules and watchdog daemon:

lsmod | grep simatic
dmesg | grep -i simatic | tail -20
systemctl status simatic-watchdog.service

5. Persist RTC handling. The IPC520A exposes a SIMATIC RTC; ensure the module loads at boot and NTP is configured as a fallback:

echo "rtc-simatic" | sudo tee /etc/modules-load.d/simatic.conf
sudo timedatectl set-ntp true

For non-IPC520A families running Linux, source drivers from the distribution's mainline kernel or contact Siemens support through the official Industry Online Support portal. Do not apply IPC520A Linux drivers to other SIMATIC families; the GPIO register maps, watchdog register layout, and interrupt assignments differ between platforms.

Troubleshooting Matrix

Security, Compliance, and OT Considerations

SIMATIC IPC driver packages distributed through the Siemens Industry Online Support entry are digitally signed by Siemens AG. Reject any package whose digital signature is missing, invalid, or whose certificate does not chain to a Siemens Trust Center root. Treat unsigned or mismatched drivers as untrusted in OT networks and do not install them on production hardware.

For OT environments following IEC 62443-2-4 or NIS2, treat driver updates as change-controlled activities:

• Capture the SHA-256 hash of every deployed driver package and retain the ZIP archive for at least one full revision cycle.
• Log the MLFB and BIOS version of every unit receiving the package.
• Restrict local administrator rights on the SIMATIC IPC so end users cannot install unsigned drivers via Windows Update or third-party tools.
• Maintain a sealed-image baseline using SIMATIC Image & Partition Creator; detect and alert on out-of-band driver installs.

Drivers from the legacy Windows 10 Enterprise 2015 LTSB and Windows 8.1 sections should not be deployed on systems receiving security updates beyond their support lifecycle. Microsoft ended mainstream support for Windows 8.1 in January 2018 and for Windows 10 Enterprise 2015 LTSB in October 2020 (extended support ended October 2025). Plan migration to Windows 10 IoT Enterprise LTSC 2019/2021 or Windows 11 IoT Enterprise LTSC 2024 in line with the OS lifecycle policy of your operating site.

When decommissioning a SIMATIC IPC, sanitize the storage stack through a cryptographic erase (for SSDs) or a multi-pass ATA Secure Erase (for HDDs) before redeployment or end-of-life disposal. Do not rely on a quick-format pass for OT hardware that may have processed sensitive process data.