Windows industrial PCs in the SBOM: edition, build and patch level instead of CVE lists
In brief · As of November 2026
Panel PCs, industrial PCs and vision computers usually run Windows 10 or 11 IoT Enterprise LTSC, with runtime software such as WinCC, TwinCAT or CODESYS Control Win on top. Unlike with a PLC, the plant builder assembles this software. For Windows itself three details count: edition, build and patch level, the fourth part of the build number (10.0.19044.7807). In its update data Microsoft lists the LTSC editions under their release line, so Windows 10 IoT Enterprise LTSC 2021 appears as “Windows 10 Version 21H2”. For this line Microsoft fixed 2,391 CVEs between November 2025 and October 2026, twelve of which were already being exploited. That cannot be assessed one by one; the reliable statement is the gap between the installed and the current patch level. The data is collected with a read-only script from the registry, locally or from the maintenance PC.
On the industrial PC, the plant builder assembles the software
A PLC comes with its manufacturer's firmware. An industrial PC comes with a Windows image, and everything above it is installed by the plant builder or a supplier: visualization, runtime, drivers, tools. Each of these layers has a version and an advisory source of its own:
- Windows: edition, build and patch level. The source is Microsoft's Security Update Guide with monthly, machine-readable update data.
- Automation software: WinCC Runtime (Siemens ProductCERT), TwinCAT (Beckhoff via CERT@VDE), CODESYS Control Win (CODESYS via CERT@VDE; 17 of the 36 CODESYS advisories name it) and visualizations from other vendors.
- Other programs and runtime environments: .NET, Java, remote maintenance and utility programs. For common programs the NVD has CPE entries; here matching via CPE works.
- Drivers: fieldbus cards, cameras, licence dongles, and drivers that ship with Windows itself, as the example further down shows.
The device level is not enough here. Two identical panel PCs with the same order number can carry completely different software; the plant SBOM therefore needs the software inventory of every PC. More on this source in the article on creating the SBOM in plant engineering.
Microsoft lists LTSC editions under their release line, and the edition decides the end of support
No IoT or LTSC edition appears in Microsoft's monthly update data. They are listed under the release line with the same build number. For matching, the edition therefore has to be mapped to its line first:
| Edition | Build | Line in Microsoft's update data | Security updates until |
|---|---|---|---|
| Windows 10 (IoT) Enterprise LTSB 2016 | 14393 | Windows 10 Version 1607 | 13 Oct 2026, expired |
| Windows 10 (IoT) Enterprise LTSC 2019 | 17763 | Windows 10 Version 1809 | 9 Jan 2029 |
| Windows 10 Enterprise LTSC 2021 | 19044 | Windows 10 Version 21H2 | 12 Jan 2027 |
| Windows 10 IoT Enterprise LTSC 2021 | 19044 | Windows 10 Version 21H2 | 13 Jan 2032 |
| Windows 11 Enterprise LTSC 2024 | 26100 | Windows 11 Version 24H2 | 9 Oct 2029 |
| Windows 11 IoT Enterprise LTSC 2024 | 26100 | Windows 11 Version 24H2 | 10 Oct 2034 |
Easy to overlook is the difference between rows three and four. Windows 10 Enterprise LTSC 2021 and Windows 10 IoT Enterprise LTSC 2021 have the same build and receive the same updates, but the Enterprise edition ends on 12 Jan 2027, the IoT edition five years later. The build does not reveal this; the edition is recorded in the registry (EditionID) and in the licence documentation. The dates come from the Microsoft lifecycle.
LTSB 2016 received its last update on the October 2026 Patch Tuesday. Panel PCs with this edition have been running without security updates since then, even if they otherwise work perfectly.
The patch level is the fourth part of the build number
Two parts of the build number 10.0.19044.7807 count: 19044 is the line, 7807 the patch level, which Microsoft calls the Update Build Revision (UBR). Every cumulative update raises the UBR. In its update data Microsoft names, per CVE and line, the build from which it is fixed and the KB article. A PC is affected if its UBR is lower than that of the fixed build.
On 3 Nov 2026 we downloaded the update documents from November 2025 to October 2026 from Microsoft's CVRF interface and counted them for the line Windows 10 Version 21H2 (x64):
| Measurement (3 Nov 2026) | Result |
|---|---|
| fixed CVEs, November 2025 to October 2026 | 2,391 |
| of which already exploited according to Microsoft | 12 |
| per Patch Tuesday | 24 (February 2026) to 908 (October 2026) |
| current fixed build (Patch Tuesday 13 Oct 2026) | 10.0.19044.7807 (KB5126657) |
| for comparison: Windows 11 24H2 / Windows 10 1809 | 2,717 / 2,403 |
In October 2026 it was 908 CVEs for a single Windows line, in February 24. Anyone assessing every CVE individually against every industrial PC cannot keep up. The reliable statement for the plant is a different one: which patch level is installed, how many months it lags behind the current one and which of the open CVEs are already being exploited. The list of open CVEs follows from that.
An example of an exploited vulnerability is CVE-2025-24990 in the Agere modem driver ltmdm64.sys that ships with Windows. According to Microsoft it can be exploited even if no modem is in use; it is fixed by the cumulative update of October 2025 removing the driver, for Windows 10 21H2 build 10.0.19044.6456 (KB5066791). A panel PC that has not been patched since an acceptance in autumn 2024 carries this vulnerability without any modem hardware installed.
The inventory reads the registry, locally or from the maintenance PC
Everything needed is in the registry and can be read without administrator rights:
- Windows version: under
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersionthe valuesCurrentBuild,UBR,EditionIDandDisplayVersion.ProductNameis not a reliable source; on Windows 11 it still says “Windows 10”. - Installed programs: the uninstall keys under
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstalland their 32-bit counterpart underWOW6432Node, each with name, publisher and version. - Not via the WMI class `Win32_Product`: according to Microsoft, a query triggers a consistency check of all MSI installations, visible in the event log as a reconfiguration per application. On a running operator PC that is not a harmless read access.
Locally, such a script runs on every PC at acceptance and writes a file that goes into the plant SBOM. From the maintenance PC it works via PowerShell remoting (WinRM, port 5985 or 5986). This requires remoting to be enabled on the target PC, the account to be in the “Remote Management Users” group or an administrator, and outside a domain the target PC to be entered as a trusted host on the maintenance PC. On many panel PCs remoting is off by default; then running the script locally at acceptance is the simpler route.
For the plant, edition, build, patch level and the installed automation software count
- Record edition, build and UBR per industrial PC and map the edition to the Microsoft line. The end of support follows from the edition, not from the build.
- Show the gap to the current patch level and the open, already exploited CVEs instead of assessing thousands of CVEs individually.
- Keep automation software with vendor and version as components of their own below the PC and match it against the advisories of its vendors.
- Re-read edition, build, patch level and installed programs at every service visit. Without remote access, the last measured state is the most honest statement.
Werkspilot reads the inventory file and carries Windows with edition, build and patch level, as well as the installed automation software, as components of the PC in the plant.
All 13 manufacturers compared: SBOM by manufacturer →
Guide: the plant SBOM in five steps.
Which sources feed the device list, which version layers count per device and how matching against manufacturer advisories works without CPE, compact as a PDF with a checklist per step.
Werkspilot keeps the devices of delivered plants and reports when a manufacturer advisory hits one of them by order number and firmware. It reads runtime, libraries and Windows versions and carries them per device. The figures in this article are our own measurements from 3 Nov 2026 from Microsoft's update data.
