Windows Server Update Services

Winsage
May 15, 2025
Microsoft's May 2025 Patch Tuesday addressed 72 vulnerabilities in Windows Remote Desktop services, including two critical vulnerabilities, CVE-2025-29966 and CVE-2025-29967, which are heap-based buffer overflow issues. These flaws allow unauthorized attackers to execute arbitrary code over a network, posing significant risks. The vulnerabilities have been rated as "Critical" and classified under CWE-122. They affect various versions of Windows operating systems utilizing Remote Desktop services. Although there have been no reported active exploitations, experts warn of the potential dangers, urging users to apply patches immediately. The update also addressed five actively exploited zero-day vulnerabilities in other Windows components. Patches are available through Windows Update, WSUS, and the Microsoft Update Catalog.
Winsage
May 13, 2025
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 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
May 1, 2025
Business and enterprise users are facing challenges upgrading to Windows 11 24H2 due to an issue stemming from an update released on April 8th, which primarily affects machines using Windows Server Update Services (WSUS). Windows 11 Home users are not impacted by this issue. Microsoft is investigating a fix but has not yet provided a solution, leaving users who installed the April 8th update unable to upgrade. The affected versions of Windows 11 include 23H2 and 22H2.
Winsage
May 1, 2025
Microsoft is preparing to release the Windows 11 25H2 update in October, aimed at facilitating the transition to Windows 11 24H2. However, the rollout of Windows 24H2 has faced issues, with many PCs experiencing blocks due to third-party applications and technical problems. The April security patch, released on April 8, has complicated the upgrade process for some users, particularly those with the patch KB5055528 installed, leading to error code 0x80240069. This issue mainly affects IT administrators using Windows Server Update Services (WSUS), while individual users on Windows 11 Home are largely unaffected. Microsoft is investigating the problem and plans to release a fix by the next Patch Tuesday on May 13. Additionally, organizations are advised to explore alternative update management solutions, as WSUS is no longer under active development.
Winsage
April 30, 2025
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 30, 2025
Windows 11 version 24H2 has been facing rollout challenges due to compatibility issues, leading Microsoft to implement a new block identified by protection number 56318982. The removal of such blocks can take time, similar to the previous ID 52754008 case. Current problems with Windows Server Update Services (WSUS) are preventing devices on Windows 11 versions 23H2 and 22H2 from accessing the 24H2 update. Users attempting to download version 24H2 may encounter error code 0x80240069, attributed to the April 2025 security update (KB5055528). This error obstructs the download process, and there is no temporary workaround available from Microsoft at this time. The issue is also affecting the System Center Configuration Manager (SCCM). Error code 0x80240069 is not documented in Microsoft's resources.
Winsage
April 11, 2025
Windows 11 version 24H2 has introduced significant issues, including blue screens of death (BSOD) and device bricking associated with update KB5043145. Users have reported problems such as black screens, corrupted boot sectors, and non-functional system restore points. Businesses are facing complications like failed domain join operations, group policy errors, and stalled WSUS updates. Specific issues include Remote Desktop disconnections after update KB5050094, the removal of the Windows Copilot app in March 2025, blocked BIOS updates for Lenovo ThinkPad users, and gaming performance problems for titles like Star Wars Outlaws and Avatar: Frontiers of Pandora. Microsoft is aware of these issues but is slow to provide solutions. Users are advised to use built-in troubleshooters, roll back problematic updates, pause updates, manually update drivers, and back up their systems before major updates.
Winsage
April 9, 2025
Microsoft will continue to support driver update synchronization for Windows Server Update Services (WSUS) servers, postponing the planned deprecation initially set for April 18 due to customer feedback. Paul Reed, Azure Compliance Senior Program Manager, noted the importance of this feature for organizations, particularly in regulated environments. A revised timeline for the future of WSUS driver synchronization will be developed, and Microsoft is open to ongoing customer feedback.
Winsage
April 8, 2025
April 2025 Patch Tuesday introduced fixes for over 120 vulnerabilities, including a critical zero-day vulnerability (CVE-2025-29824) that is actively exploited. CVE-2025-29824 is a user-after-free vulnerability in the Windows Common Log File System (CLFS), allowing privilege escalation to SYSTEM on compromised Windows machines. Microsoft has patched 32 CLFS vulnerabilities since 2022, with six exploited in the wild. Updates for Windows 10 are not yet available. Other notable vulnerabilities include CVE-2025-26663 and CVE-2025-26670, both unauthenticated user-after-free vulnerabilities in Windows LDAP, and CVE-2025-27480 and CVE-2025-27482 in Windows Remote Desktop Services. None of these vulnerabilities have been patched for Windows 10 systems, but updates are forthcoming. Microsoft reversed its decision to discontinue driver update synchronization to WSUS servers, confirming that WSUS will continue to synchronize driver updates.
Search