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
CISA Adds Actively Exploited Zimbra CVE-2026-73570 to KEV Catalog with Immediate Patching Deadline
CISA has added CVE-2026-73570 affecting Zimbra Collaboration Suite to its Known Exploited Vulnerabilities catalog, ordering urgent remediation due to confirmed active exploitation. The flaw enables unauthenticated remote command execution on servers where the optional zimbra-snmp package is installed and SNMP notifications are enabled. Exploitation occurs via specially crafted SMTP requests that trigger operating system command injection under the privileges of the zimbra user. Zimbra released the fix in version 10.1.20 on July 20, 2026, while CISA placed the vulnerability in the KEV list on August 21 and set an August 24 deadline for federal civilian agencies. Organizations are advised to first verify exposure by checking for zimbra-snmp and SNMP notification settings before applying the update. Post-patch steps include validating the version, controlled service restarts, and hunting for indicators such as unexpected Zimbra restarts, anomalous zimbra user activity, and new files in sensitive directories like /opt/zimbra/jetty/webapps/. The directive highlights the critical nature of pre-authentication flaws in internet-facing mail servers that process untrusted inbound traffic.
CISA Adds Zimbra Collaboration Suite CVE-2026-73570 to KEV Catalog After Confirmed Exploitation
US authorities have issued a warning about active exploitation of a vulnerability in the Zimbra Collaboration Suite. CISA added the OS command injection flaw CVE-2026-73570 to its Known Exploited Vulnerabilities catalog on August 21, 2026, marking the fifth such entry for the year. The issue resides in the SNMP monitoring component and allows unauthenticated attackers to execute arbitrary operating system commands with Zimbra user privileges when SNMP notifications are enabled. MITRE rated the vulnerability 8.9 on CVSS v3.1, classifying it as High severity. Federal agencies must apply mitigations by August 24, while all organizations using the product are urged to prioritize patching to prevent further abuse.
IBM Patches 191 Vulnerabilities in AIX and PowerVM VIOS Including Critical Remote Command Execution Flaws
IBM disclosed a large set of security vulnerabilities affecting its UNIX-based AIX operating system and the PowerVM VIOS virtualization component. The company addressed a total of 191 CVEs through multiple updated releases for both products. Thirty-five of the issues received CVSS base scores of 9.0 or higher, with three OS command injection vulnerabilities rated at 9.9 that allow remote attackers to execute commands with low privileges. IBM provided specific Technology Level and Service Pack updates for AIX 7.3 and 7.2 branches along with corresponding fixes for PowerVM VIOS versions 4.1.x. The advisory covers both IBM-developed code and third-party software components integrated into the platforms. All listed CVEs are now resolved in the recommended maintenance levels released on August 15.
Vulnaware Bridges Vulnerability Scanners and ITSM Systems to Improve Critical Flaw Prioritization
A new open-source tool called Vulnaware has been developed to address the persistent gap between vulnerability discovery and remediation in enterprise environments. The project focuses on intelligent prioritization rather than attempting to fix every reported CVE, recognizing that fewer than 10 percent of published vulnerabilities are ever exploited. It integrates outputs from MaxPatrol VM, Nessus Pro, and Greenbone/OpenVAS, then applies scoring based on CISA KEV catalog presence, public exploit availability from Vulncheck feeds, and trend data. Prioritized issues are automatically converted into tickets in Jira Service Management, GLPI, Znuny, and osTicket, while also delivering alerts via Telegram and email. The approach aligns with the updated CISA BOD 26-04 framework that replaced flat 15- and 25-day deadlines with risk-based timelines of 3, 14, or 60 days. By treating vulnerability remediation as a managed change or service request under ITIL4 principles, Vulnaware ensures that critical issues reach the correct engineering teams with proper SLA tracking.