error code Archives

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

May 1, 2025

Windows 11 April security patch quietly blocks 24H2 update, but are you impacted?

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: 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 30, 2025

Microsoft acknowledges problem with Windows 11 24H2 update

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 25, 2025

Windows “inetpub” security fix can be abused to block future updates

A recent Microsoft security update has created a new 'inetpub' folder in the root of the system drive, linked to a fix for a Windows Process Activation elevation of privilege vulnerability (CVE-2025-21204). This folder has appeared on systems without Internet Information Services (IIS) installed. Microsoft advises users not to delete the folder, as it enhances system protection. However, cybersecurity expert Kevin Beaumont has shown that the 'inetpub' folder can be manipulated by non-administrative users to create a junction that redirects to a Windows file, potentially obstructing future Windows updates and resulting in a 0x800F081F error code. Microsoft has classified this issue as "Medium" severity and has closed the case, indicating it may be addressed in future updates.

Winsage

April 18, 2025

Windows 11 Update Fiasco: Microsoft Confirms Blue Screen Of Death. Here’s What To Do

Reports of the Blue Screen of Death (BSOD) have emerged following updates to Windows 11, with Microsoft confirming the issue in a support document. Users may encounter a blue screen exception with error code 0x18B (SECUREKERNELERROR) after installing the latest updates, specifically linked to the Windows 11 version 2H42 release and affecting updates KB5053598, KB5053656, and KB5055523. Microsoft is working on a fix and has deployed a server-side update to disable changes causing the BSOD. Affected users are advised to check for updates multiple times to receive the server-side patch quickly. Additionally, the April update has caused issues with Windows Hello functionalities, which Microsoft plans to address in a future update scheduled for May 2025.

Winsage

April 18, 2025

Windows 11 24H2 Update Bug Triggers BSOD Error

Microsoft has acknowledged a significant bug in its Windows 11 24H2 updates, causing Blue Screen of Death (BSOD) crashes with the error code “SECUREKERNELERROR” (0x18B). This issue has escalated since the April 2025 Patch Tuesday update, affecting thousands of users globally. The bug leads to system crashes after installing the updates, resulting in persistent crash-restart loops or unbootable systems. Initially reported in March 2025, the problem gained traction following the April update, prompting Microsoft to confirm the bug and investigate its cause. Other issues include failures with Windows Hello and compatibility problems with games and software, particularly on ARM-based devices. To address the crisis, Microsoft has implemented a Known Issue Rollback (KIR) to disable the problematic code, which is being automatically pushed to affected devices, although users may experience a delay of up to 24 hours. Users are advised to keep their devices connected to the internet and restart their PCs multiple times to expedite the fix. For enterprise environments, IT administrators must manually deploy a specific Group Policy update. Microsoft is working on a permanent solution, expected in a future update, while also acknowledging related issues and committing to further fixes in the upcoming May 2025 update.

Winsage

April 17, 2025

It must be a day with a ‘y’ in it – there’s a problematic Windows 11 update causing blue screens

Microsoft is addressing issues stemming from the KB5055523 update for Windows 11, which has caused Blue Screen of Death (BSoD) errors with the 0x18B error code. This update was automatically installed on most devices and is linked to the earlier KB5053656 preview update. Microsoft is implementing a Known Issue Rollback (KIR) to mitigate the problem, although it may take up to 24 hours for the fix to propagate to consumer and non-managed business devices. For enterprise-managed devices, IT administrators must manually resolve the issue by configuring the necessary Group Policy.

Winsage

April 17, 2025

March, April Windows 11 updates cause BSOD pain for users

Microsoft has reported that two recent updates for Windows 11 24H2, specifically the April cumulative update KB5055523 and the March preview update KB5053656, are causing blue screen crashes with the error code 0x18B (SECUREKERNELERROR) after installation and reboot. There is currently no permanent solution, but Microsoft is working on a workaround using a Known Issue Rollback (KIR) that will automatically apply to personal or unmanaged devices through Windows Update. IT departments will need to manually download a Group Policy .msi file to implement the rollback. Affected machines will require a restart to complete the process.

Winsage

April 17, 2025

Microsoft Has a Fix for Windows’ Latest Blue Screen Problem

Unexpected crashes on Windows 11 version 24H2 have been reported, resulting in a secure kernel fatal error with the blue screen exception error code 0x18B. Microsoft has introduced a Known Issue Rollback (KIR) to address this issue by rolling back specific updates. For personal or non-managed computers, the fix will be automatically deployed via Windows Update, and users are advised to restart their PCs. For enterprise devices, IT departments must install the KIR Group Policy, found under Computer Configuration > Administrative Templates, and a restart of affected devices is required. The blue screen bug appeared after a Patch Tuesday update that addressed 134 security vulnerabilities, including a zero-day flaw.