code issue Archives

Winsage

May 13, 2025

Windows 11 upgrade block lifted after Safe Exam Browser fix

Microsoft has lifted an upgrade block that prevented certain users of the Safe Exam Browser from installing the Windows 11 2024 Update due to compatibility concerns. The block was initially implemented in September to protect users from issues with Safe Exam Browser version 3.7 or earlier. Users are encouraged to upgrade to Safe Exam Browser version 3.8 or later before proceeding with the Windows 11 24H2 update. If users still encounter the safeguard hold after 48 hours of updating, they should contact Safe Exam Browser Support. The Windows 11 24H2 feature update is now available for all compatible PCs, except those under safeguard holds. Microsoft has resolved issues that previously blocked the update for some users and has removed other compatibility holds for specific devices and applications. However, some upgrade blocks remain due to incompatible hardware and software. Windows 11 24H2 began its rollout in May 2024 for enterprise testing, with a broader release in October.

Winsage

May 6, 2025

Microsoft pushes fix for Windows 11 update 0x80240069 errors

Microsoft has resolved an issue that affected the delivery of Windows 11 24H2 feature updates via Windows Server Update Services (WSUS) after the installation of the April 2025 security updates. Users reported upgrade problems, specifically encountering error code 0x80240069 during attempts to update from Windows 11 23H2 or 22H2. The update complications primarily impact enterprise environments using WSUS, while home users are less likely to experience these issues. Microsoft is rolling out a fix through Known Issue Rollback (KIR) for enterprise-managed devices, requiring IT administrators to implement the KIR Group Policy on affected endpoints. Additionally, Microsoft is addressing a separate issue where some PCs were upgraded to Windows 11 despite Intune policies preventing such upgrades.

Winsage

April 30, 2025

Microsoft: Windows 11 24H2 updates fail with 0x80240069 errors

Microsoft has acknowledged a significant issue affecting enterprise users trying to upgrade to Windows 11 24H2 via Windows Server Update Services (WSUS) after installing the April 2025 security updates, specifically the monthly security update KB5055528. Users with Windows 11 23H2 or 22H2 are encountering Windows Update Service errors with the code 0x80240069, preventing the download process for Windows 11 24H2 from initiating or completing. Microsoft confirmed that devices with the April security update might be unable to update via WSUS. WSUS, primarily used in enterprise settings, has been deprecated as of September 2024, but Microsoft will continue to support existing functionalities. Additionally, Microsoft is addressing a "latent code issue" that has caused some devices to upgrade to Windows 11 despite Intune policies against such upgrades.

Winsage

April 25, 2025

Microsoft fixes Server 2025 Remote Desktop freezing issues

Microsoft has resolved a bug in Windows that caused Remote Desktop sessions to freeze, which emerged after an update to Windows 11 24H2 and Server 2025 released in February. The company released a patch (KB5055523) for Server 2025 and advised users to install it for essential improvements, while a previous update had already addressed the freezing issue on Windows 11. Microsoft has faced multiple patch-related challenges this year, including erroneous error messages and issues with USB-connected printers. A recent update also allowed some users to install Windows 11 against corporate policies due to a "latent code issue." User sentiment reflects frustration with Microsoft's reliability and suggests a need for better resource allocation to address internal failures.

Winsage

April 21, 2025

Intune flaw pushed Windows 11 upgrades on blocked devices

Microsoft identified a "code issue" within its Intune device management software as the reason for the unintended rollout of Windows 11 to devices not designated for the upgrade. The flaw triggered upgrades despite existing policies meant to prevent them. Microsoft is working on a fix and has advised organizations to pause Windows updates via Intune to avoid further issues. Devices that received the upgrade erroneously will need manual intervention to revert to their previous version. This incident follows a similar occurrence in November 2024, where customers experienced unexpected upgrades from Windows Server 2022 to Windows Server 2025. Microsoft attributed that incident to third-party products used for managing server updates. Additionally, a month prior, Microsoft retracted a preview update for Windows 11 due to severe issues causing crashes.

Winsage

April 16, 2025

More headaches for IT admins as Windows 11 rolls out to ineligible PCs

Microsoft has encountered issues in its enterprise sector, particularly involving the unintended release of Windows 11 to devices that do not meet eligibility criteria due to a bug in Intune. This problem has persisted since April 12 and is caused by a "latent code issue" that prevents Intune from enforcing rollout block policies. The bug allows Windows 11 to be available to "ineligible" Windows 10 desktop devices that IT administrators had blocked from receiving the update. Microsoft is working on a targeted code fix and has advised IT administrators to pause Windows feature updates and manually revert affected devices to Windows 10. The number of companies impacted is unclear, and there are no automated solutions available for the rollback process.

Winsage

April 16, 2025

Windows 11 upgrades sneak past admin blockades

Microsoft has acknowledged that some users are receiving unsolicited invitations to upgrade to Windows 11, despite configurations in Intune meant to prevent this. The issue is attributed to a "recent service change" that has exposed a latent code problem affecting a subset of users. Affected users are prompted to upgrade regardless of IT restrictions, and those who have upgraded can manually roll back to the previous version. Microsoft has advised administrators to pause Windows Feature Updates temporarily and has announced that a targeted code fix is being deployed to resolve the issue. This incident is reminiscent of a previous Windows Server 2025 error in November 2024, which involved a mistaken release as a security update.