![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 63%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELV%3C/text%3E%3C/svg%3E)
The hangs are consistent with a hardware‑level or driver‑level issue that is being triggered after recent Windows servicing changes, not with the superseding of KB5066130/KB5071959 itself.
From the logs and similar cases in the context, there are two key patterns:
- Hardware/firmware issues surfaced by recent updates
- The WHEA-Logger Event 17 entries indicate corrected PCI Express Root Port errors. These are hardware‑reported errors on the PCIe bus (for example, between the Intel chipset root port and devices such as the NVIDIA GPU or other PCIe devices).
- Similar behavior is documented for TPM hardware: Event ID 17 is logged when the TPM hardware fails to execute a command, and the root cause is a device/firmware issue that Windows surfaces in the logs. The recommended mitigation there is to ensure the latest Windows cumulative updates and firmware/BIOS updates are installed, and then work with the hardware vendor if the issue persists.
- By analogy, the PCIe WHEA-Logger 17 events point to a hardware or firmware problem on the PCIe root port or attached device that is being stressed or exposed after recent updates.
- System instability tied to a scheduled security/boot task and network connectivity
- A closely related Windows 10 freeze scenario in the context shows the system consistently freezing about 5 minutes after startup, but only when connected to the internet. The workaround was to disable a scheduled task
Microsoft\Windows\PI\Secure-Boot-Update. With that task disabled, the freezes stopped. - In that case, uninstalling and reinstalling network drivers did not help; the issue was a Windows task that runs shortly after boot and appears to interact with security/boot components when the system is online.
- A closely related Windows 10 freeze scenario in the context shows the system consistently freezing about 5 minutes after startup, but only when connected to the internet. The workaround was to disable a scheduled task
Given the behavior described:
- Hangs occur within ~10 minutes when the Ethernet cable is connected from boot.
- Hangs are largely avoided when booting offline, waiting ~10 minutes, and then connecting Ethernet.
- WHEA-Logger 17 PCIe root port errors appear around the time of the hangs.
- Servicing logs show KB5071959 being moved from Superseded to Absent by DISM (normal package state transition when superseded by newer updates).
This strongly suggests:
- A Windows component or scheduled task that runs shortly after boot and requires network connectivity is triggering activity that stresses the PCIe path (for example, GPU, chipset, or another PCIe device), causing corrected hardware errors and eventually a hang on this older platform.
- The superseding of KB5071959 is likely just the point at which a newer cumulative update or servicing change was applied, not the direct cause.
Actionable steps based on the context:
- Ensure all current Windows updates and firmware are installed
- For similar hardware‑level issues (TPM Event 14/17), the guidance is to install the latest Servicing Stack Update (SSU) and monthly Cumulative Update, and then update BIOS/firmware from the OEM.
- On this Medion system, install the latest Windows 10 cumulative update available and check Medion’s support site for BIOS and chipset/PCIe/Intel Management Engine firmware updates.
- Check for and temporarily disable the Secure Boot–related scheduled task
- In the similar Windows 10 freeze case, disabling the
Microsoft\Windows\PI\Secure-Boot-Updatescheduled task prevented freezes that only occurred when the system was online shortly after boot. - On this system, inspect Task Scheduler under
Microsoft > Windows > PIforSecure-Boot-Update. If present, temporarily disable it and observe whether the hangs still occur when booting with Ethernet connected. - This is a workaround; if it stabilizes the system, it indicates that a security/boot update task interacting with hardware (possibly PCIe/firmware) is the trigger.
- In the similar Windows 10 freeze case, disabling the
- If the issue persists, treat it as a hardware/platform problem
- As with the TPM Event 14/17 guidance, if up‑to‑date Windows and firmware do not resolve the issue, the next step is to work with the hardware vendor (Medion) to diagnose the PCIe root port and attached devices.
- The repeated WHEA-Logger 17 entries on the same PCIe root port (VendorID 0x8086, DeviceID 0xA115) indicate that this specific chipset root port is reporting errors; the vendor can advise on known issues or firmware fixes for that platform.
These steps align with how similar hardware‑signaled error scenarios (TPM Event 14/17 and Secure-Boot-Update–related freezes) are handled in the provided material: keep Windows and firmware current, mitigate problematic scheduled tasks that run shortly after boot with network connectivity, and escalate to the hardware vendor if the platform continues to report hardware errors.
References:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 2%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELV%3C/text%3E%3C/svg%3E)