AntiMalwareAugust 24, 2026🇷🇺Translated from Russian

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

HabrVulnerabilities & Exploits

Fuzzy Logic in Cybersecurity: Reducing Vulnerability Queue by 7.5 Times with CVSS, EPSS and FSTEC Comparison

An information security specialist has developed a fuzzy logic system that prioritizes vulnerabilities far more effectively than traditional scoring methods. The approach uses linguistic variables and membership functions to handle the inherent uncertainty in exploitability and impact assessments. By integrating EPSS probability data with CVSS impact scores and vulnerability age, the model reduces the actionable backlog by a factor of 7.5. The implementation relies on the Mamdani inference algorithm and trapezoidal membership functions to produce smooth, human-interpretable urgency ratings. Detailed coverage checks and rule-base validation ensure no gaps exist in the decision space. Real-world testing on CVE-2025-49113 in Roundcube Webmail demonstrated practical advantages over rigid threshold logic. The method is positioned as a practical enhancement rather than a replacement for existing standards.

AntiMalwareVulnerabilities & Exploits

VLC Media Player Hit by Two Memory Corruption Flaws Exploitable via Malicious PNG and Rogue RealRTSP Server

Two vulnerabilities have been discovered in the VLC media player that allow out-of-bounds memory access. The issues affect versions from 3.0.0 through 3.0.23. CVE-2026-56711, rated 8.6 on CVSS 4.0, stems from an integer overflow when calculating image buffer sizes in PNG files, enabling attackers to trigger writes beyond allocated memory simply by opening a crafted image or loading it from a playlist. CVE-2026-73324, scored 6.9, resides in the RealRTSP module and permits a malicious server to send an oversized response string that causes reads past the end of a buffer due to a missing null terminator. Both flaws are present in official VideoLAN builds, although some distributions may exclude the RealRTSP component. No special configuration or plugins are required to trigger the issues. Until patched releases appear, users are advised to avoid opening images or playlists from untrusted sources and to refrain from connecting to unknown RealRTSP streams.

AntiMalwareVulnerabilities & Exploits

September Windows 11 Security Update KB5124008 Breaks Always On VPN Certificate Authentication

The September security update KB5124008 for Windows 11 has introduced a regression that disables Always On VPN connections using certificate-based authentication. The issue affects devices running Windows 11 versions 24H2 and 25H2 that connect to Remote Routing and Access Service (RRAS) and Network Policy Server (NPS) instances on Windows Server 2019. VPN profiles deployed via Microsoft Intune are impacted, with the failure occurring during the certificate negotiation phase of the IPsec connection. Users confirm the problem is reproducible: the VPN works before the patch, stops after installation, and resumes after patch removal and reboot. Microsoft has not yet acknowledged the regression or released a fix, leaving administrators to pause deployment through WSUS or Intune and open support cases with client and NPS logs. A potential workaround involves switching profiles to EAP-TLS, though its reliability remains unconfirmed.

HabrVulnerabilities & Exploits

API Token Lifecycle: From Issuance to Revocation and Secure Management

The article provides a comprehensive examination of the full API token lifecycle in browser-based applications, emphasizing that signatures alone cannot prevent token theft. It details risks introduced at issuance, storage, transmission, and revocation stages, including improper OAuth grant types and long-lived tokens. Key recommendations include short-lived access tokens, atomic refresh token rotation, and the use of Authorization Code Flow with PKCE for public clients. Storage advice strongly discourages localStorage and sessionStorage in favor of HttpOnly cookies or a Backend-for-Frontend pattern that keeps real tokens on the server. The piece also covers CSRF protections, rate limiting on authorization endpoints, and the advantages of signed client assertions over static secrets. Overall, it stresses that token security depends on the entire lifecycle architecture rather than cryptographic strength alone.