upgrade issue

Winsage
August 19, 2025
Microsoft has resolved a significant bug affecting Windows users since August 12, which hindered the migration from Windows 10 to 11 and caused various issues, including installation errors and data corruption. The upgrade issue was particularly problematic for users transitioning from Windows 10 version 1809 to Windows 11 22H2 and 23H2, as well as for Windows Server upgrades, with many encountering error code 0x8007007F. Microsoft confirmed the fix on August 18, although it was available as early as August 15. The latest versions, Windows 11 version 24H2 and Windows Server 2025, were not affected by these issues. Users are urged to upgrade from Windows 10 before October 14 to avoid losing essential security updates.
Winsage
November 13, 2024
Microsoft released an update (KB5046617) for Windows 11 24H2 and Windows Server 2025 that addresses security concerns and includes quality improvements. The update fixes a Task Manager glitch that incorrectly displayed zero counts for active applications when using the "Group by Type" option. It also resolves access issues related to Dev Drive for Windows Subsystem for Linux and installation delays of up to 40 minutes on certain hardware configurations. Additionally, it addresses failures during installations and extended restart times on Windows Server 2025 systems with 256 or more logical processors. Microsoft has been working on known issues, including a problem with fingerprint sensors and an unexpected upgrade issue affecting Windows Server 2019 and 2022 systems.
Winsage
June 22, 2024
- Windows 11 users have been experiencing issues preventing them from upgrading to the Enterprise subscription since April. - Microsoft has acknowledged the issue and mentioned they are working on a fix, but no exact date for the resolution has been provided. - A recent update, KB5039212, also had issues preventing users from upgrading to Enterprise, with an 'Access denied error (error code 0x80070005)'. - There is currently no workaround for the issue, and users will have to wait for Microsoft to release a fix in an upcoming update.
Search