Microsoft clarifies it is not actually ending support for many Windows 10 PCs

Microsoft has clarified that it is not ending support for Windows 10 on every system out there. The company has acknowledged the bug and has shared a fix.

The Windows 10 wallpaper with red filter

Support for Windows 10 ended last month on October 14, 2025, with the final Patch Tuesday update released under KB5066791. While this means that the OS will no longer be receiving security updates, Microsoft has assured that Defender will continue to provide some level of protection.

As such, Windows 10 systems that have run the entire course of available cumulative updates now display a "Your version of Windows has reached the end of support" message on the Windows Update settings page.

Microsoft however has confirmed that users are also seeing this message on certain still-supported versions and editions of Windows 10. The tech giant has clarified that this is a false notification that is incorrectly being displayed on the following Windows 10 versions:

Windows 10, version 22H2 Pro, Education or Enterprise editions that are correctly enrolled in the Extended Security Updates (ESU) program and configured with an ESU product key
Windows 10 Enterprise LTSC 2021
Windows 10 IoT Enterprise LTSC 2021

As such, Microsoft has also provided a fix for the issue via a cloud configuration update it has pushed out. However it adds that to receive the update, a system must be connected to the internet, have downloads via the OneSettings CSP (Configuration Service Provider) policy enabled, allow firewall access, and not block dynamic updates.

The company is working on a permanent fix at the moment. In the meantime, a special group policy has also been published for installing and configuring a known issue rollback (KIR) that IT admins can deploy on affected systems that you can download at the link below:

Download for Windows 10, version 21H2 and 22H2 — KB5066791 251020_20401 Known Issue Rollback

Microsoft notes that admins will need to install and correctly configure the provided Group Policy to resolve the bug. This can be done by setting the "KB5066791 251020_20401 Known Issue Rollback" value to "Disabled". A system reboot after this will be required for the change to take effect.

You can find the issue here on Microsoft's official Windows Health dashboard website.