optional update

Winsage
December 2, 2025
Microsoft has acknowledged a glitch with the KB5070311 preview update that causes bright white flashes when launching File Explorer in dark mode on Windows 11. The issue occurs not only when opening File Explorer but also during actions like navigating to Home or Gallery, creating new tabs, toggling the Details pane, and selecting 'More details' while copying files. As a temporary solution, Microsoft recommends disabling dark mode. The KB5070311 update also resolved a bug that caused the explorer.exe process and taskbar to become unresponsive after certain notifications and addressed search failures in File Explorer on some SMB shares. Additionally, Microsoft had previously confirmed a critical bug affecting File Explorer and the Start Menu on Windows 11 24H2 devices with cumulative updates since July 2025.
Winsage
November 17, 2025
Windows 11 has received an update on October 28, 2025, to fix the "Update and shut down" bug that caused computers to restart instead of shutting down after updates. This fix is part of the optional KB5067036 update for Windows 11 25H2 Build 26200.7019 or Windows 11 24H2 Build 26100.7019. Users can manually install the patch through the "Check for updates" option in Windows Update settings, or it will be included in a mandatory update on November 11. The update also improves system stability by addressing various errors, including "Error 0x80070103" during driver installations, "Error 0x800f0983" during Windows Update, and issues with video and game display, large archive extraction, application responsiveness, and File Explorer freezing.
Winsage
November 13, 2025
Microsoft has released the Windows 11 November 2025 Update (Build 26200.7171/26100.7171 or newer), which fixes an issue where the Task Manager did not close properly when the Close (X) button was clicked. This problem, first observed after the October optional update (KB5067036), caused multiple invisible instances of the Task Manager to accumulate, consuming 20-25 MB of RAM and 0 to 1.5% of CPU resources, leading to performance degradation. Microsoft confirmed that the October update inadvertently caused this issue while attempting to fix a grouping problem within the Task Manager. The November update (KB5068861) resolves the bug, restoring the expected functionality of the Task Manager. Users can check for lingering instances by opening the Task Manager and observing if multiple instances appear after closing and reopening it.
Winsage
November 3, 2025
An out-of-band security update, KB5070881, has disrupted the hotpatching feature for some Windows Server 2025 devices. This update was released alongside reports of the CVE-2025-59287 remote code execution vulnerability. The Cybersecurity and Infrastructure Security Agency (CISA) has instructed U.S. government agencies to strengthen their systems against this vulnerability. Microsoft has acknowledged that the OOB update caused some Hotpatch-enrolled Windows Server 2025 systems to lose their enrollment status and has ceased distributing the update to these devices. Those who installed the update will not receive Hotpatch updates in November and December but will get standard monthly security updates. Administrators can install the KB5070893 security update to address the CVE-2025-59287 flaw without disrupting hotpatching. Microsoft has also disabled the display of synchronization error details in its WSUS error reporting system and resolved various issues affecting Windows 11.
Winsage
November 3, 2025
Microsoft has acknowledged an issue affecting Windows 11 users after installing the optional October 2025 update (KB5067036), where the Task Manager does not fully close when the "Close" button is used, resulting in multiple instances of taskmgr.exe running in the background. This can lead to performance degradation, including system stuttering and CPU hangs. A temporary workaround involves manually terminating each Task Manager process or using the Command Prompt with the command: taskkill.exe /im taskmgr.exe /f. The KB5067036 update also introduced enhancements like an updated Start Menu and restored functionality to the Windows 11 Media Creation Tool, while addressing specific update errors.
Winsage
November 2, 2025
Microsoft has introduced a new naming convention for Windows Update titles, moving away from the YYYY-MM format and the term cumulative. The October 2025 optional update is now labeled as “Security Update (KB5034123) (26100.4747)” instead of the previous detailed titles that included the release date and specific Windows version. This change has raised concerns among IT professionals and users, as it complicates the identification of updates and may lead to confusion between different types of updates. IT administrators have expressed frustration over the lack of critical information in the new titles, which they believe hinders troubleshooting and update management. Microsoft has acknowledged the feedback but remains committed to the new naming scheme, while updates accessed through the Microsoft Update Catalog or WSUS will retain their original naming structure.
Search