Search the Community

While Patch Tuesdays bring important security updates for the Windows OS, they can often introduce major bugs. The one this month on Windows 10, KB5058379, that introduced a BitLocker recovery reboot bug, has now been resolved with KB5061768 OOB update. Alongside that, Microsoft also resolved a Windows 11 24H2 upgrade bug related to VBS with a Recovery update KB5059442. Speaking of Windows 11, users are reporting installation failures with the Windows 11 May 2025 Patch Tuesday update KB5058411 as well. Affected users say that these are failing with various error codes like 0x800f0991, 0x800f0991, 0x800f0838, 0x800736b3, and 0x800f081f. User Shukang Liang on the Microsoft support forums writes: "Problem with windows update KB5058411 Installation fails and error code 0x800f0991 comes up." The query has been upvoted by 33 other users at the time of writing. Another user PaulK671 notes 0x800736b3 and 0x800f081f errors as they write: The thread has been upvoted by 19 people at the time of writing. Meanwhile, user Jenny-XS says they came across the 0x800f081f error code when trying to install the May '25 Patch Tuesday. Microsoft recently published a support article with a long list of Windows 11 and 10 hex error codes that lead to installation failures. Unfortunately, though, none of the codes reported by users match with the ones Microsoft has provided workarounds for. Thus, it looks like Microsoft will have to update its list sooner rather than later as clearly many hex error codes are still pending and are due for addition to its support documentation. Interestingly, one of the commenters on the 0x800f0991 error thread, ScotBirch, added that they were able to resolve the issue using the "Fix problems using Windows Update" option. Microsoft had detailed what that is and how it works back in December 2024. You can read the linked article to find out more and see if perhaps it fixes your issues too. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Microsoft released Patch Tuesday updates for Windows 10 and Windows 11 for May 2025 this week under KB5058379/ KB5058392 / KB5058383/ KB5058387 and KB5058411/ KB5058405, respectively. Alongside those, the company also released new Dynamic updates for Windows 11 24H2 and Windows 10. The updates apply to Windows Server 2025 as well. Dynamic updates bring improvements to the Windows Recovery in the form of Windows Recovery Environment (WinRE) updates, also called Safe OS updates, as well as to the Setup binaries in the form of Setup updates. First up, we have the dynamic updates for Windows 11 24H2 and Windows Server 2025, and this is one of the rare times where an actual release note has been listed instead of the generic one. Microsoft says that the latest WinRE Safe OS update fixes a VBS (Virtualization-based Security) or Memory Integrity-related bug that prevented Windows 11 24H2 upgrades. VBS is meant to ensure Code Integrity on Windows systems. It writes: Up next, we have the sole dynamic update for Windows 10 in the form of a Safe OS WinRE update. Microsoft notes: For those who may not be aware, these Dynamic Update packages are meant to be applied to existing Windows images prior to their deployment. These packages include fixes to Setup.exe binaries, SafeOS updates for Windows Recovery Environment, and more. Dynamic Updates also help preserve Language Pack (LP) and Features on Demand (FODs) content during the upgrade process. VBScript, for example, is currently an FOD on Windows 11 24H2. If you are having issues installing the update, Microsoft has shared a detailed guide on how to troubleshoot update-related problems. You can find it in full in its dedicated article here. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Last month, Microsoft finally removed a six-month-old Windows 11 24H2 upgrade block related to desktop wallpaper apps. The block was made under safeguard ID 52754008. That hold was placed right when Windows 11 24H2 was released to the public in early October 2024. A month later today, the company has removed another one of those compatibility blocks. This one was placed as a result of a browser-related issue under safeguard hold ID 49562592. Microsoft has said that the bug was resolved in a recent update to the Safe Exam Browser app. The tech giant notes that the app's update version 3.8 or later fixes the problem. This is a welcome thing considering Windows 11 version 24H2 just entered its final rollout phase, according to Microsoft itself. Microsoft writes: Upon checking the release notes for the Safe Exam Browser (SEB), we did not see any fixes in particular related to the Windows 11 2024 update. However, it does mention a change related to Windows support: You can find the Windows 11 24H2 SEB issue entry here on Microsoft's official Windows Health dashboard website. If you still find that your update is blocked, it may be one of the newer safeguard holds, like the one related to a system driver. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

This week, Microsoft has been making some major announcements related to Windows drivers for hardware. First, the company is moving on from Device metadata and the Windows Metadata and Internet Services (WMIS) as it is deprecating the feature, and alongside that, an update to driver signing has also been announced. You can find the details in our dedicated article here. Alongside those, Microsoft has also announced new HLK and VHLK May 2025 releases. These are being referred to as refreshed versions and replaces the RTM version released in May 2024. It writes: For those not familiar, HLK or Hardware Lab Kit essentially helps hardware vendors ensure compatibility and fulfill the driver certification process. Thus, errata, in the context of HLK, refers to bugs or issues that may cause the certification test to "fail" on perfectly compatible hardware or drivers. VHLK is a similar thing, except it is designed with virtual environments, VHDs, and VMS in mind. The Windows HLK (and VHLK) comes under the gambit of the WHCP, or Windows Hardware Compatibility Program. It is a test framework designed to aid hardware vendors and Microsoft partners in testing and ensuring the proper compatibility of hardware and drivers on Windows 11 and 10, among others, such that they can receive the WHQL or Windows Hardware Quality Labs certification. The HLK driver brings several new tests for Bluetooth LE Audio and support for Generation 2 VMs in the case of the VHLK. You can find the full details here on the official Microsoft Tech Community blog post. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Alongside new test capabilities for Windows 11 24H2 and Server 2025, Microsoft shared news about two other significant changes regarding Windows hardware driver development earlier today. First, the company has announced the deprecation of Windows Device metadata and the Windows Metadata and Internet Services (WMIS). In a new blog post, Microsoft has explained: For those wondering what it is, device metadata, as the name suggests, is the collection of additional, user-facing information that an original equipment manufacturer (OEM) provides about a hardware device. The feature was introduced with Windows 7 and can include stuff like icons, logos, descriptive texts, among other things, that help the Windows UI display details about such devices in places like Task Manager or Device Manager. The metadata is presented via an XML file. Going forward, Microsoft recommends using the INF instead, which are setup information files for driver packages. You can find the details here on the official Tech Community blog post. Alongside the upcoming death of Device metadata and the Windows Metadata and Internet Services (WMIS), Microsoft has also announced changes for pre-production driver signing. Microsoft says that the current driver signing CA (certificate authority) or PCA 2010 is set to expire next month in June 2025. Microsoft has explained the timeline of events: You can find the details here on the official Microsoft Tech Community blog post. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

The first hotpatch for Windows 11 is coming next week alongside Patch Tuesday and such, Microsoft has announced that it has released resources for it such that IT admins and system admins have an easier time working out how the new type of update deployment will work. For those not familiar, hotpatching is meant to keep devices secure without causing downtime or interruptions. That is because these security updates install automatically and take effect without needing a device restart. Hotpatch works as an extension of Windows Update and requires Autopatch to create and deploy these updates to devices enrolled in the Autopatch quality update policy. To help, Microsoft has shared technical documentation, the hotpatch calendar, and many more items for use by administrators. Microsoft writes: You can find the post here on Microsoft's Windows Health dashboard website message center. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Microsoft, this past week, announced that Windows 11 24H2 is now ready to roll out to everyone and that it can be downloaded by all. This is despite widespread performance complaints, potential data loss worries, and bugs. Earlier today, we reported on a script enforcement bug on Windows' latest feature update that has been broken for months. Thankfully, Microsoft finally has a fix. Speaking of fixes, the company has now issued a Group Policy to address another major bug related to Windows 11 24H2 upgrade. While Microsoft does place safeguard holds from time to time to prevent feature updates (the most recent one was placed last month), this was a bug that prevented 22H2 and 23H2 systems from installing 24H2 as it would end up with a 0x80240069 error code. The problem happened on WSUS (Windows Server Update Services) managed PCs. The Group Policy that has been released is essentially a known issue rollback (KIR) as Microsoft says it is still investigating the root of the bug. The company writes: You can find the issue entry here on Microsoft's official Windows Health Dashboard website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Microsoft, today, has released the newest build to the Windows 11 24H2 Dev channel for Insiders. The new build, 26200.5581, under KB5055651, brings HDR improvements, energy saver feature to Intune, Windows Update service related improvements, and more. The full changelog is given below: You can find the blog post here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Microsoft, today, has released the newest build to the Windows 11 24H2 Beta channel for Insiders. The new build, 26120.3950, under KB5055653, brings HDR improvements, energy saver feature to Intune, Windows Update service related improvements, and more. The full changelog is given below: You can find the blog post here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Windows 11's latest feature update, version 24H2, is far from flawless, with major upgrade-related bugs, widespread performance complaints, and potential data loss worries. However, Microsoft has decided that it is now ready to roll it out to everyone. The company has announced that Windows 11 24H2 (2024 update) release schedule has "reached the last phase of the gradual rollout." The company has explained how users can avail the update via the Windows Update service in the Settings app. It writes: For devices on Windows 11 versions 23H2 and 22H2, Microsoft has recommended that they upgrade to Windows 11 24H2 in order to "try the latest Windows innovations". Thus if you wish to have the latest Windows 11 features, you can update to 24H2. Microsoft writes: Finally, the company has added that systems with safeguard holds and compatibility blocks in place won't be offered the newest feature update until the hold is lifted. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of April): 1,811 RIP Matrix | Farewell my friend

Earlier today, we published an article regarding Microsoft's recent removal of the BYPASSNRO script and how it has irked Windows 11 users. The script still allows users to go around the internet and Microsoft Account (MSA) requirements during the Windows 11 OOBE (initial setup). If you are against it, you can let Microsoft know via the official Feedback Hub portal. One of the possible reasons for the Microsoft Account requirement is the default BitLocker encryption changes on the latest Windows 11 feature update, as the recovery key is backed up on the user's MSA. Security from data encryption is something Microsoft also stressed when it discussed the benefits of TPM. For those who are on Windows 11 24H2 or are planning to upgrade soon, keep in mind that Microsoft encrypts your Windows drive with BitLocker or Device Encryption by default. While Microsoft would do so in the past on non-Home editions, the requirement for BitLocker was relaxed for Windows 11 24H2, and now even Home edition systems can be encrypted too. BitLocker has been found to impact drive speed and performance in the past, but there is a far scarier aspect of it, and that is the possibility of data loss. Recently, a Reddit user, MorCJul, shared a bit of a rant about BitLocker Device Encryption and how it has seemingly led to the loss of data for many users. The post was headlined "Microsoft forces security on users, yet BitLocker is now the biggest threat to user data on Windows 11," and it has been overwhelmingly upvoted by users with nearly 550 upvotes at the time of writing. The user says: The Redditor raises a very valid point here, that for most general folks, like the ones who don't read Neowin daily or aren't tech savvy enough or are unaware of all this, can be completely stumped if anything goes wrong with how Microsoft has set up the Windows 11 24H2 BitLocker situation, because they will have no idea that their device was ever encrypted or about keeping the key safe. Hopefully, Microsoft can find a better way to handle this situation so that the general user can be more easily alerted to the dangers of BitLocker. In the meantime, there is an official guide on the topic of backup and recovery of BitLocker keys. Users are advised to bookmark this article as it can come in very handy. We also published a guide on how users can use the Registry to disable BitLocker encryption during the OS setup. You can bookmark this article, too. If you are already on Windows 11 24H2, you can also head over to the Settings app to choose whether or not you want to keep BitLocker enabled (image above). Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Windows 11 version 24H2 is nearly eight months old, and despite that, Microsoft is still blocking the feature update on systems owing to compatibility issues. The latest such incident was announced last month under the safeguard hold ID 56318982. And sometimes it can take a long while before these compatibility blocks are removed, as it happened, for example, in the case of ID 52754008. However, updates can be blocked as a result of bugs in the Windows Update service itself. As it turns out, Microsoft's Windows Server Update Services (WSUS) is currently bugged out such that it is unable to receive the 24H2 feature update on Windows 11 23H2 and 22H2 devices. When an attempt is made to download version 24H2, the error code "0x80240069" is displayed. Microsoft says that the problem started with the April Patch Tuesday update KB5055528. The company has explained the issue in some detail below: The tech giant has not provided any workaround in this case and has only mentioned that it is " presently investigating and will provide an update when more information is available." You can view the issue here on Microsoft's official Windows health dashboard site. Looking around the internet, it appears that SCCM (System Center Configuration Manager) is also affected by this problem, and it is not exclusive to WSUS. Microsoft has dedicated documentation for Windows Update-related error codes. However, the page does not provide any information about the 0x80240069 error, unfortunately. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Alongside the setup and recovery updates, Microsoft has released a new OOBE (out of box experience) update today for the newest Windows 11 version, 24H2, as well as Windows Server 2025. The update is available under KB5059093 and as is usually the case with such updates, the company has published a general changelog for it without going into any specific details about what it brings. Microsoft writes: These OOBE updates will install automatically during setup if the user has an active internet connection. In a separate document about OOBE, Microsoft explained what these OOBE updates deliver. It also notes that the downloading and installation time of the update depends on the users' hardware and internet connectivity. It writes: You can find the support article for KB5059093 here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Windows 11 version 24H2 insiders in the Beta Channel have got a new build to try this weekend. Build 26120.3941 (KB5055634) is here with some welcome improvements like the ability to turn off profanity filter for voice typing, accessibility improvements, new features for users with styluses, and more. Here is what is rolling out gradually (basically the same changelog as the one that Microsoft shipped today to Dev Channel insiders😞 Fixes for everyone in the Beta Channel include the following: And here is the list of known bugs: You can find the official announcement here. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Nvidia's RTX 5000 series desktop launch has been one of the worst in the company's history, and we are not exaggerating when we say that. That is because the 50-series has been plagued with misleading marketing claims, burnt and melted power connectors, and loads of display issues related to the graphics driver. The company has been continuously fixing such problems, and the latest driver version, 576.02, also resolves a variety of such issues, including ones on Windows 11 24H2 that are related to "general stability, and black screens." However, as Neowin reader LiLmEgZ pointed out in the article comments, users are still encountering plenty of problems despite the driver package being packed with bugfixes. One such problem is related to temperature sensor data reading as the GPU temperature on the Nvidia App gets stuck at certain temperature points. For example, the feedback thread on the GeForce forum that talks about this mentions that the user's Asus ROG Astral RTX 5090 read a constant 25 degree Celsius. It looks like a reboot is necessary to fix the problem. The user goku5993 writes: Other commenters on the thread also encountered the same problem on 5080, 5070, and it is not just isolated to 50-series either as RTX 40-series and RTX 30-series GPU owners are also affected. Another user marioho writes: If you are on Nvidia's 576.02 driver and are having to deal with this problem, the best thing to do would be to roll back to the previous driver version, as users say this fixes the problem. This workaround is reminiscent of what even the game devs had suggested recently due to GeForce driver issues. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Last October, Microsoft blessed us with Windows 11 24H2, bringing various improvements like updates to Copilot, better file management with TAR and 7z archive support, a new Energy Saver mode, and enhanced compatibility for newer PCs. Soon after the update started rolling out, some players of the beloved classic Grand Theft Auto: San Andreas began reporting a bizarre problem: the Skimmer seaplane (shown below) was completely missing from the game world and could not be found anywhere. These reports started circulating among the game's community and eventually landed on the radar of Silent, the developer known for SilentPatch. If you don't know what SilentPatch is, it is a passion project with unofficial fixes to squash bugs and improve how older PC games, especially the Grand Theft Auto titles, run on modern computer systems. Silent (AKA CookiePLMonster) initially figured it might be an issue caused by other mods or perhaps a specific setup, as is common with older games and many user configurations. However, the reports kept coming, and some players insisted the bug happened even on a game installation with no other modifications after they updated to Windows 11 24H2. One user posting on GTAForums captured the general confusion: Convinced the issue was real, Silent decided to investigate directly. He set up a test environment with Windows 11 24H2 and a clean installation of GTA San Andreas. Sure enough, loading the game confirmed the Skimmer was gone from its usual spot on the water. The Skimmer is gone from its usual spot Things got even weirder when he tried to force the game to create the plane using an in-game command. Instead of appearing normally, the game glitched and launched the player character an astronomical distance into the sky. A skimmer containing CJ launched 1.087 quadrillion light‑years into the sky. Without SilentPatch installed, this sends the game camera into a visual mess; with SilentPatch installed, the game simply freezes. That chaotic behavior of being launched sky-high strongly hinted at numerical errors, likely involving floating-point values, within the game's logic. When the game froze with SilentPatch installed, Silent could see exactly where it happened in the code: inside a function called CPlane::PreRender, stuck in a loop trying to adjust the plane's rotor blade angle. The value it was using for the blade speed (m_fBladeSpeed) was enormous, around 3.73e+29. This kind of impossibly large number meant tiny adjustments were ineffective, leading to the freeze. This huge speed value was ultimately derived from the plane's altitude, confirming the launch into the sky was the initial symptom of something being fundamentally wrong with the plane's properties. Silent traced the source of this problem back to the code that handles setting up a vehicle's physics the first time it loads. This process calculates things like the vehicle's "bounding box" - an invisible box defining its physical boundaries. A critical part of this setup involves adjusting the bounding box's vertical limit (its Z value) based on the vehicle's suspension. He discovered that for the Skimmer, this calculation was using incorrect numbers, resulting in a corrupted Z value for the bounding box, specifically something like -4.30747210e+33. This impossible value was what caused the game to think the plane was at an extreme height, triggering the sky-launch and the subsequent numerical errors. The deeper Silent went, the more he realized the core issue was tied to how the Skimmer is defined in one of the game's configuration files, vehicles.ide. The Skimmer's entry in this file was shorter than other planes, missing a couple of key numbers needed for its setup - specifically, the size of its wheels. This was likely a leftover from Grand Theft Auto: Vice City, where the Skimmer was classified as a boat and did not need these 'wheel' parameters. When Rockstar changed it to a plane in San Andreas, they forgot to update its line in vehicles.ide to include these now-required values. The game's function for loading vehicle data, CFileLoader::LoadVehicleObject, uses sscanf to read the parameters from the vehicles.ide line into local variables. The critical flaw here is that the game's code did not initialize the local variables intended for the wheel size parameters to a default value (like 0.0), nor did it check if sscanf successfully read values for them. This meant that when the game read the Skimmer's line, which was missing those parameters, the local variables on the program's stack intended for the wheel sizes simply held whatever data was already present in those memory locations from previous function calls. This is a big no-no in programming because it relies on pure chance - the contents of uninitialized variables are unpredictable. Now, here is where Windows 11 24H2 enters the picture and exposes this hidden flaw. For nearly twenty years, on many versions of Windows, including Windows 10, a strange bit of luck kept this bug from appearing on PC. The vehicles.ide file is read sequentially. The entry for the 'Topfun' van comes right before the Skimmer's entry. The Top Fun van does have wheel size values defined, and they are both 0.7. By pure coincidence, on older Windows versions, the memory on the stack used to store Topfun's wheel sizes after its entry was processed was not overwritten by other operations before the game's code started reading the Skimmer's entry. So, when the game looked at the uninitialized stack locations for the Skimmer's wheel sizes, it accidentally picked up the stale 0.7 values left behind by Topfun. The calculations would then proceed using 0.7, resulting in a mostly functional, if technically incorrect, setup for the Skimmer. On Windows 10, the stack values didn’t change much between the calls. However, Windows 11 24H2 brought some internal changes. One small change was in how a low-level Windows function (LeaveCriticalSection), part of the C runtime library and involved in tidying up after reading files line by line, used temporary memory on the stack. This function started using slightly more stack space. This minor shift was just enough that when the game finished processing the Topfun line and moved to the Skimmer line, that specific stack location where the 0.7 values used to linger was now overwritten by this internal Windows function call before the Skimmer's variables were accessed. So, on Windows 11 24H2, when the game went to read the Skimmer line and loaded its uninitialized local variables from the stack, that memory spot no longer held the lucky 0.7 from Topfun. It held arbitrary data left by the updated Windows function. This unpredictable data was then used in the calculation for the Skimmer's physical setup, resulting in a wildly incorrect value for its bounding box Z coordinate, causing the plane to essentially disappear or launch the player into space. On Windows 11 24H2, more stack space was modified by a new implementation of Critical Sections. Silent makes it clear that this is not a bug in Windows 11 24H2. The way internal operating system functions use stack memory is not something programs are supposed to rely on; those details can change anytime Microsoft updates things. The real bug has always been in Grand Theft Auto: San Andreas, which was incorrectly depending on a lucky memory layout that persisted for years. Silent will include a proper code fix for this in the next SilentPatch update. For players who want to fix this issue themselves right now, before the next SilentPatch update, it is possible to manually edit the game's vehicles.ide file. Simply open data\vehicles.ide in your San Andreas directory with Notepad, find the line starting with "460, skimmer", and replace it with: Save the file, and the Skimmer should reappear. Silent notes that a similar issue occurred with Bully Scholarship Edition breaking on Windows 10 for analogous reasons. Source and image credits: Silent's Blog Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft found even more bugs in the recently released Patch Tuesday updates for Windows 11 version 24H2. This week, the company acknowledged that in certain scenarios, users might find themselves with broken Windows Hello biometric authentication or PIN. Now, another issue has shown up in the official documentation, this time with much more serious symptoms. According to Microsoft, April 2025 security updates for Windows 11 version 24H2 cause blue screens of death when restarting computers. In such scenarios, Windows 11 shows error code 0x18B "SECURE_KERNEL_ERROR." Here is what Microsoft says in the official documentation: Fortunately, users should not worry about this too much. Microsoft applied a temporary workaround using the Known Issue Rollback system, which, when deployed, removes problematic code bits to undo damage on affected systems. For regular users and non-managed environments, there is nothing to do at this point. You can restart your system to speed up the process and let the patch propagate faster (fixes usually take up to 24 hours to reach all target systems). In managed environments, though, IT Admins have to deploy Known Issue Rollback patches with special policies. For this particular case, the necessary policy is available in the official documentation. In addition to problems with Windows Hello cameras (some users report more issues with IR cameras besides what Microsoft confirmed), two other known bugs remain standing in the latest Windows 11 updates. One prevents users from launching Roblox on ARM systems when downloaded from the Microsoft Store, and another causes problems with installing security updates with certain versions of Citrix software. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft, last month, removed an upgrade block for Windows 11 version 24H2 that had been placed at the launch of the feature update back in September 2024. The tech giant is repeating that action again this month too, as earlier today, Microsoft removed yet another upgrade block related to compatibility problems with wallpaper customization apps like Wallpaper Engine. Microsoft says that it is slowly beginning to remove this safeguard hold as app updates are beginning to incorporate the necessary fixes, although the company still does not recommend trying a forced update to 24H2 if you are on an older Windows 11 version. It writes: IT admins and system admins can find information related to this problem using the safeguard ID 52754008. You can view the issue here on Microsoft's official Windows health dashboard website. Neowin noticed that the Wallpaper Engine team released an update, version 2.6, to fix Windows 11 24H2-related problems back in February. The patch notes say: You can find the full patch notes for Wallpaper Engine here. If you still can't update, perhaps it is one of the newer compatibility blocks that Microsoft recently placed. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft, today, has released the newest build to the Windows 11 24H2 Beta channel for Insiders. The new build, 26120.3863, under KB5055613, has an improved Search but it is only for Copilot+ PCs. The build also makes the Widgets better, improves desktop icons, and fixes several bugs. The full changelog is given below: You can view the blog post here on Microsoft's official website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft released Patch Tuesday updates for the month of April 2025 earlier today. On Windows 10, they were published under KB5055518, KB5055519, and KB5055521. On Windows 11, they were published under KB5055523 and KB5055528. On the Windows 10 side, Microsoft has confirmed that there are no known issues for the latest supported version of Windows, which is a rarity. Meanwhile, over on the latest Windows 11 side, the tech giant states that it has fixed a Kerberos authentication bug. The bug would not allow passwords to change correctly, leading to authentication failures as they are perceived as "stale, disabled, or deleted." In normal situations, these passwords are set to automatically rotate at an interval (30 days is the default). Due to this issue, Machine accounts in Credential Guard were also disabled as the feature is dependent on Kerberos authentication working optimally. For those wondering, when using this feature, machine account credentials are moved from the registry to the Defender Credential Guard for safety. Microsoft explains: The company says the issue has now been resolved: You can view the issue here on Microsoft's official Windows health dashboard website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft recently published a blog post about devices running Windows 10 that won't be offered Windows 11 as they don't meet the latter's system requirements. The company has urged that such users let go of their old Windows 10 PC and get a new one with Windows 11. However, the experience on Windows 11 may not be flawless, especially on the latest OS feature update, version 24H2. Last month, the company lifted an upgrade block related to gaming with safeguard hold ID 52796746. Today, however, the company has issued a new block on some new devices as it has been found that the sprotect SYS driver is having compatibility problems on Windows 11 24H2, leading to system freezing and blue screening or black screening errors. Below, Microsoft explains the issue and has also provided the safeguard hold ID for system admins: As always, Microsoft has recommended not to force an update to Windows 11 24H2 in case you can't do it. The company says it is working with SenseShield to fix it. You can find the issue here on Microsoft's Windows health dashboard website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft, today, has released the newest build to the Windows 11 24H2 Beta channel for Insiders. The new build, 26120.3671, under KB5055622, is bringing several improvements and new features. The company is further improving its recently released Quick Machine Recovery feature, adding Taskbar icon scaling, and more. There are several bug fixes too. The full changelog is given below: You can view the official blog post here on Microsoft's website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of March): 1,357 RIP Matrix | Farewell my friend

Microsoft, today, has released the newest build to the Windows 11 24H2 Beta channel for Insiders. The new build, 26120.3653, under KB5053658, is bringing several new features. Microsoft is testing a new green screen for unexpected restarts, a new quick machine recovery, and more. The company is also removing the BYPASSNRO script which helps users bypass Windows 11 internet connectivity and Microsoft account sign-in requirements. The full changelog is given below: You can view the official blog post here on Microsoft's website. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of February): 874 RIP Matrix | Farewell my friend

One day after releasing the latest non-security updates for Windows 10 and Windows 11 22H2/23H2, Microsoft is dropping a big update for those on Windows 11 24H2. Today's release, KB5053656 (build number 26100.3624), is here with quite a lot of new features, like the AI-powered Windows Search, gamepad keyboard, live captions for AMD and Intel-powered Copilot+ PCs, and more. Here is what is rolling out gradually (it will take a while for these changes to propagate to all users): These changes are available to all, right here and right now: You can download KB5053656 in Settings > Windows Update or from the Microsoft Update catalog using this link. As usual, non-security updates are optional, so feel free to skip them if you do not need or want anything from their changelogs. After all, it is a preview update of what will soon arrive as a mandatory update, so some rough surfaces might still be there. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of February): 874 RIP Matrix | Farewell my friend

Earlier this month, Microsoft removed a Windows 11 24H2 upgrade block related to gaming. Sadly for those who were affected by a Dirac Audio-related issue, Microsoft today "confirmed" that it has not been able to resolve the bug. The company had opened this issue back in December 2024 when it put the compatibility safeguard hold in place. Microsoft had explained: However, even after all this time, Microsoft has not been able to resolve the issue, as the status of the bug has now been changed to "confirmed" from "mitigated". Thus, users affected by this problem will have to wait longer. It seems the driver that was supposed to fix the issue is not yet out, so perhaps the fault is not entirely Microsoft's either. You can find the issue here on Microsoft's Windows Health Dashboard site. In the rare case that you have still not been offered Windows 11 24H2 without any compatibility block, you can try this Registry/Group Policy hack to update immediately. Source Hope you enjoyed this news post. Thank you for appreciating my time and effort posting news every day for many years. News posts... 2023: 5,800+ | 2024: 5,700+ | 2025 (till end of February): 874 RIP Matrix | Farewell my friend