Group Policy 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 6, 2025

Announcing Windows 11 Insider Preview Build 26120.3950 (Beta Channel)

Windows 11 Insider Preview Build 26120.3950 (KB5055653) has been released to the Beta Channel for Windows 11, version 24H2. Insiders on version 23H2 can opt to upgrade to version 24H2 with this build. Key changes include the introduction of energy saver management in Microsoft Intune, allowing IT administrators to manage energy settings on Windows 11 PCs. Other updates involve UI experiments in Recall, taskbar enhancements, and graphics improvements for HDR capabilities. Fixes include resolving keyboard focus issues in the taskbar, startup sound playback issues, and scaling problems after sleep/resume. Known issues involve bugs with Xbox Controllers and live captions crashing. Insiders are reminded to keep their devices updated for optimal performance and access to features.

Winsage

May 6, 2025

Announcing Windows 11 Insider Preview Build 26200.5581 (Dev Channel)

Windows 11 Insider Preview Build 26200.5581 (KB5055651) has been released to the Dev Channel, introducing new features, improvements, and fixes. Key updates include: - Energy Saver in Microsoft Intune: IT administrators can manage energy saver settings on Windows 11 PCs through group policies and MDM configurations, optimizing battery usage by limiting background activities and reducing screen brightness. - Taskbar Improvements: The needy state pill for apps has been redesigned, and administrators can allow users to unpin specific pinned apps. - Graphics Enhancements: Improved management of HDR capabilities, including refined wording for HDR settings and independent toggling of Dolby Vision mode. - Fixes: Resolved issues with taskbar keyboard focus, startup sound playback, scaling after sleep, and cumulative update errors. - Known Issues: Users may experience discrepancies in build version display after PC resets and issues with Xbox Controllers causing bugchecks. - Recall (Preview): Users can opt to remove Recall at any time, and intelligent text actions are now moderated locally. - Windows Search: For optimal performance, devices should be connected to power during initial search indexing. - Task Manager: Users may see the System Idle Process showing as 0 after the addition of a new CPU Utility column. Windows Insiders in the Dev Channel receive updates based on Windows 11, version 24H2, with features rolled out gradually.

Winsage

April 30, 2025

Windows 7 took forever to load if you had a solid background. Now we know why

Windows 7, launched in 2009, experienced a boot delay of 30 seconds for users who set a single-color image as their desktop background. This issue stemmed from a programming oversight where the system waited for a confirmation message that never arrived because a single-color background does not qualify as a bitmap. The delay could also occur if the “Hide desktop icons” group policy was enabled, complicating the loading process. Microsoft took several months to identify and fix the problem, releasing an update in November 2009 to resolve the issue.

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.

Winsage

April 16, 2025

Microsoft warns of blue screen crashes caused by April updates

Microsoft has warned customers about potential system failures due to a blue screen error (secure kernel fatal error) following the installation of Windows updates since March, specifically the KB5055523 April cumulative update and the KB5053656 March preview update, affecting Windows 11, version 24H2. Users may experience crashes and a blue screen exception with the code 0x18B. Microsoft is working on a solution and has implemented a Known Issue Rollback (KIR) to reverse the problematic updates, which will automatically reach affected devices within 24 hours. Affected users are advised to restart their devices. For enterprise-managed devices, administrators must install the KIR Group Policy specific to their Windows version to resolve the issue, requiring a device restart. Further assistance is available on the Microsoft support website. Additionally, Microsoft has released emergency updates for local audit logon policies in Active Directory Group Policy and alerted administrators about potential inaccessibility of Windows Server 2025 domain controllers post-restart.

Winsage

April 14, 2025

Windows Server 2025 Restart Bug Breaks Connection with Active Directory Domain Controller

Microsoft has warned IT administrators about a significant issue affecting Windows Server 2025 domain controllers, which may struggle to manage network traffic after a system restart. This problem arises because the domain controllers revert to the standard firewall profile instead of the required domain firewall profile, leading to potential inaccessibility on the domain network, application failures, and open ports that could pose security risks. The issue specifically affects Windows Server 2025 systems with the Active Directory Domain Services role, while client systems and earlier server versions remain unaffected. To address this, Microsoft recommends a temporary workaround: manually restarting the network adapter using PowerShell with the command Restart-NetAdapter * after each reboot. Administrators are advised to create a scheduled task for automation, monitor domain controllers for disruptions, and minimize unnecessary restarts. Microsoft is working on a permanent fix, with an update expected in the future.