Windows 10 systems

Winsage
June 30, 2026
Recent reports indicate that AMD's driver is disabling Smart Access Memory (SAM) on Windows 10 systems, resulting in reduced gaming performance. Users have experienced issues such as game crashes and improper recognition of Radeon graphics cards. Many have uninstalled the AMD driver using Display Driver Uninstaller (DDU) and performed a clean installation, but SAM remains disabled in the Adrenalin software despite BIOS settings being unchanged. Notifications from Windows 10 suggest a conflict between the AMD driver and the operating system. AMD is investigating the issue and has released a preview driver version 26.6.3 to address compatibility problems for RX 7000 series GPUs. Temporary workarounds have been suggested by users, including checking monitor refresh rates and rebooting systems.
Winsage
June 26, 2026
AMD unveiled its Adrenalin Edition 26.6.2 WHQL Drivers, featuring day-one support for games like Assassin's Creed Black Flag Resynced and DOOM: The Dark Ages | Revelations, and introducing FSR Upscaling 4.1 for RDNA 3 GPUs. Users on Windows 10, particularly with Radeon RX 7000 and RX 9000 series GPUs, reported installation issues, especially those under the Extended Security Updates program. AMD released a hotfix, Adrenalin Edition 26.6.3, to address these installation problems, which is available for download on their website.
Winsage
June 24, 2026
Windows 11 version 24H2 will reach the end of servicing on October 13, 2026. Enterprises often face version drift, requiring different upgrade strategies for various Windows 11 builds across endpoints. Upgrade methods include enablement packages, ISO-based feature updates, or direct upgrades from Windows 10. Enablement packages are the quickest and least disruptive option for compatible Windows 11 systems. Qualys TruRisk Eliminate can standardize upgrades and minimize version drift on a large scale. Endpoints should be assessed for readiness, categorized by eligibility and current OS status. Enablement packages are recommended for recent Windows 11 builds due to their minimal download size, faster installation, and reduced operational impact. If enablement packages are unavailable, ISO-based feature updates may be necessary. Direct upgrades from Windows 10 to Windows 11 25H2 can be executed without intermediate transitions. Qualys TruRisk Eliminate provides tools for managing these upgrade processes effectively.
Winsage
June 23, 2026
Many users of Windows 10 are experiencing issues with the AMD Adrenalin Edition 26.6.2 graphics driver, which fails to launch properly and shows a yellow exclamation mark in Device Manager. AMD has acknowledged the problem, attributing it to an incompatibility with Windows 10, and has advised users to revert to the previous driver version, Adrenalin Edition 26.6.1. This earlier version does not support FSR 4.1 for RX 7000 series GPUs. There have also been rare reports of similar errors on RX 9000 series systems. AMD's engineers are investigating the issue and working on a solution.
Winsage
June 11, 2026
Microsoft has resolved an issue affecting certain Windows Server 2025 devices that were booting into BitLocker recovery mode after the April 2026 security update. This issue was linked to specific BitLocker Group Policy configurations and required users to input their BitLocker recovery key upon the first restart after the update. However, this key would only need to be entered once for subsequent restarts, provided the group policy configuration remained unchanged. The problem primarily affected enterprise systems rather than personal devices. The issue arose under specific conditions: BitLocker was enabled on the operating system drive, a particular Group Policy was set, the Secure Boot State PCR7 Binding was "Not Possible," the Windows UEFI CA 2023 certificate was present, and the device was not already using the 2023-signed Windows Boot Manager. Microsoft released fixes in the KB5094125 and KB5093998 updates to address this problem, preventing devices with incompatible group policy configurations from installing the 2023-signed Windows Boot Manager. Event ID 1032 in the System event log indicates the issue when Windows updates are installed. For IT administrators unable to deploy the latest updates, it is recommended to remove the Group Policy configuration before installing updates or to implement a Known Issue Rollback (KIR) on affected devices. Additionally, Microsoft had previously addressed similar BitLocker recovery issues in August 2024 and May 2025.
Winsage
April 16, 2026
A recent Microsoft security update, April 2026 KB5082063, has caused issues for administrators of Windows Server 2025 and Windows 11 systems, with many devices entering BitLocker recovery mode after reboot, requiring a 48-digit recovery key. This issue primarily affects enterprise-managed systems with specific TPM Group Policy settings involving PCR7 validation. Similar problems have been reported with updates KB5083769 and KB5082052 on Windows 11. The issue arises from five conditions: BitLocker must be enabled on the OS drive, the Group Policy must include PCR7, the msinfo32.exe tool must show Secure Boot State PCR7 Binding as “Not Possible,” the Windows UEFI CA 2023 certificate must be in the Secure Boot Signature Database, and the device must not be using the 2023-signed Windows Boot Manager. Microsoft suggests two workarounds: removing the TPM validation Group Policy before the update and re-enabling BitLocker, or applying a Known Issue Rollback (KIR) before installation. Skipping the April updates is not advisable due to the addressing of 167 vulnerabilities, including two zero-days. BitLocker recovery issues following updates have been recurring since 2022, with similar incidents reported in August 2022, August 2024, and May 2025, indicating ongoing challenges with Secure Boot certificates and TPM validation bindings in enterprise environments.
Winsage
April 16, 2026
Microsoft announced that certain Windows Server 2025 devices may experience a BitLocker recovery prompt after installing the April 2026 KB5082063 Windows security update. The recovery mode will be triggered under specific conditions: BitLocker must be enabled on the operating system drive, the Group Policy for TPM validation must be configured with PCR7, the Secure Boot State PCR7 Binding must indicate "Not Possible," the Windows UEFI CA 2023 certificate must be in the Secure Boot Signature Database, and the device must not be using the 2023-signed Windows Boot Manager. Microsoft stated that this issue is unlikely to affect personal devices, as the configurations are mainly found in enterprise-managed systems. They are working on a resolution and recommend administrators remove the Group Policy configuration before deploying the update. If removal is not possible, applying a Known Issue Rollback (KIR) is advised to prevent triggering the recovery prompt. Microsoft has previously addressed similar BitLocker recovery prompt issues in May 2025, August 2024, and August 2022.
Search