Windows 11 May Silently Remove Discrete GPU Drivers Due to Eco Mode on Gaming Laptops
Windows 11 has introduced an unexpected behavior that can delete drivers for discrete graphics cards on gaming laptops when the device remains powered off for an extended period in Eco Mode.
The issue was first reported by the owner of an Asus ROG Zephyrus G14 equipped with a mobile GeForce RTX 5070 Ti. In this power-saving mode the discrete GPU is physically disconnected from the PCIe bus. After several weeks of operation, Windows concluded that the hardware had disappeared permanently and initiated cleanup.
Analysis of the setupapi.dev.log showed that the system component pnpclean.dll removed the video card after only 15 days of absence and then deleted the now supposedly unnecessary Nvidia driver package. Although the standard timeout is 30 days, certain devices can trigger earlier removal.
Upon returning to Standard Mode the GPU appeared in Device Manager as a Microsoft Basic Display Adapter with error code 10. The Nvidia application reported driver incompatibility, and the only reliable fix proved to be a complete driver reinstallation.
While the problem has been confirmed primarily on Asus ROG laptops, it may affect other models that fully disconnect discrete graphics. One owner of an older G14 with AMD Radeon graphics reported identical behavior. The developer of the G-Helper utility has already added a warning to the application.
The simplest preventive measure is to switch to Standard Mode every couple of weeks to reset the timer. Automatic cleanup can also be disabled with the following PowerShell command run as administrator:
Set-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches\Device Driver Packages' -Name Autorun -Value 0
Disabling the feature stops Windows from automatically removing old drivers and unused devices. No official confirmation has been received from Microsoft so far.
Related articles
Browser Built on Mistakes: How Real-World Attacks Shaped Modern Browser Defenses
Browser security features such as process isolation, sandboxing, and restrictions on code execution were not designed in isolation but evolved directly in response to concrete attacks over more than a decade. Early threats like malicious Flash advertisements in 2015 demonstrated how a single compromised banner could compromise an entire system, prompting the industry to phase out plugins entirely. Later discoveries, including the Spectre vulnerability, forced browsers to implement stricter site isolation and timing-attack mitigations that remain in place today. Session hijacking and malicious browser extensions further drove the adoption of stronger cookie protections and permission models. BI.ZONE analysts trace this history through specific incidents to show why current architectures prioritize separation of sites into distinct processes. The resulting design reduces the blast radius of any single exploit and continues to adapt as new attack classes emerge.
cKEV Index Launches to Prioritize Vulnerabilities as AI Accelerates Exploit Development
CyberOK has introduced the open cKEV Index, a catalog of high-priority vulnerabilities ranked by the Urgent Patch Score (UPS) methodology. The index incorporates timelines of events such as exploit publication, proof-of-concept releases, and confirmed attacks to help organizations prioritize patching under resource constraints. It addresses the growing gap between rapid AI-assisted vulnerability discovery and slower remediation processes at both vendors and customers. Examples from Anthropic reports highlight how threat actors used AI agents for reconnaissance, code analysis, and exploit development against Android apps and web applications. Microsoft and Oracle have publicly linked increased vulnerability findings and larger patch releases to AI tooling. The UPS framework defines progressive phases from Radar to Emergency/IR, allowing teams to act on strong signals without waiting for full confirmation. An open version of the catalog is now available with detailed event histories for Urgent Patch and Emergency stages.
Apache HTTP Server 2.4.69 Patches 20 Vulnerabilities Including CVSS 9.8 Issues
The Apache HTTP Server development team released version 2.4.69 on October 1, 2026, addressing a total of 20 vulnerabilities. While the Apache Security Team assessed most issues as moderate or low in impact, several vulnerabilities received CVSS base scores as high as 9.8. The update includes fixes for stack-based buffer overflows, use-after-free conditions, and out-of-bounds writes affecting multiple modules. No vulnerabilities were rated Critical or Important by the developers, with five classified as Moderate and fifteen as Low. Specific fixes cover the mod_vhost_alias, mod_http2, mod_dav, and mod_dav_fs modules, along with Windows-specific path handling problems.
BrokenPipe PoC Exploits Steam Client Service for Silent SYSTEM Privilege Escalation on Windows
A new proof-of-concept named BrokenPipe demonstrates how a standard Windows user can escalate privileges to NT AUTHORITY\SYSTEM through the Steam Client Service without requiring administrator credentials or triggering a UAC prompt. The vulnerability stems from insufficient signature validation in VDF installation scripts processed by steamservice.exe, allowing an attacker to control the execution path of a malicious script. The issue affects Steam version 10.96.30.42 on both Windows 10 and Windows 11, though no public CVE has been assigned yet. Valve was notified of the flaw in March, several months prior to public disclosure. The attack is strictly local and requires initial code execution under a standard user account, making it relevant for shared or corporate environments. Security teams are advised to inventory Steam installations, apply application allowlisting, and monitor for anomalous SYSTEM-level processes linked to the service while awaiting an official patch.