- Windows 11 24h2s April -Patch causes some odd bugs
- There are more problems with Windows Hello Logins
- The update is also fully installing for some people
Windows 11 24H2’s latest patch creates some problems with errors in installing (again), and also Windows Hello ends up in some cases.
Let’s start with the error in Windows Hello, which is the feature that allows for secure login to your PC (via face recognition using a webcam or other methods in addition).
Windows latest reports that some users have found that the cumulative update for April 2025 (known as KB5055523) affects those who use Windows Hello for face recognition with a privacy of webcam.
How does a facial login even work with a privacy protection that hides the camera? It works well because the technology utilizes an infrared sensor on the camera that can work through a physically closing (a plastic shooter that several privacy conscious people use to rule out any danger of being spying on through webcam).
The problem is that the April update seems to be messy with the infrared sensor so that login no longer works unless you open this privacy protection – which is hardly ideal.
Windows latest found the problem that was present on an HP Specter -Impairable computer, and also highlights a report from a Windows 11 user that has been affected by this error and tells us, “I have reproduced the problem several times, with several clean installations. The webcam we use is Logitech Brio 4K, with the latest firmware and drivers, which are compatible with Windows Hello.”
There are also other reports on Reddit, such as this: “Would just see if anyone else is experiencing problems with Windows Hello Face recognition since the latest update (KB505523). Before, I had the camera (BRIO 4K) covered and it would work fine. Now I have to remove privacy coverage for it to recognize me. alone. ”
There are a number of answers from people who repeat that they have the same error affecting their login. The only solution is apparently to uninstall the April update (which strongly suggests that this is a problem caused by this latest patch from Microsoft).
That said, Windows offers latest a possible solution that is achieved by going into Device Manager (Just write it in the Windows Search Field and click it). In there, click the little arrow next to where it says’Cameras‘And then you can see two cameras listed – IR (infrared) camera and RGB/color (usually) camera. Right -click the latter and disable it, but leave the infrared camera turned on. Now, if you go and configure Windows Hello Again, it might work properly.
However, Windows latest does not guarantee this and says this will only do the trick for some Windows 11 users. If you are desperate for a solution, you can give this a whirl as you could wait a while for the official solution from Microsoft. Just don’t forget that you will of course have to re -exploit the most important (RGB) camera after any solution is used.
Interestingly, in the official patch notes for the April update, Microsoft marks a problem with Windows Hello – but not this. Rather, this is a separate problem, although one that should not affect those running Windows 11 homes.
Microsoft explains: “We are aware of an edge case of Windows Hello problem that affects devices with specific security features that are activated … Users can observe a Windows Hello message that says ‘something happened and your pin is not available. Click to set your pin again’ or ‘Sorry went wrong with facial setup.’
Microsoft provides instructions on what to do if you encounter this particular problem via its April patch notes (under known editions).
However, this error only affects those using System Guard Secure Launch (or dynamic root of confidence in measurement), which is only supported on Windows 11 Pro (or Enterprise Editions). So, as mentioned, if you’re on Windows 11 at home, don’t run into this hiccup.
Installation Blues
Windows latest also picked up another major problem, namely installation error (which is nothing new). These seem to happen again with the update in April 2025, with the usual meaningless error messages that accompany a failed attempt (hexadecimal stop error such as ‘0x80070306’).
The technical site notes that it has confirmed reports that the update not installed in this way or its progress is stuck at either 20% or 70% in some cases never actually completed. Windows latest informs us that Microsoft is apparently investigating these installation errors.
There are other reports on this kind of problem on Microsoft’s Answers.com Help Forum (and some possible suggestions for solutions from a customer service employee, some of whom have reportedly worked for some, but not for others). In the event of the original poster of this thread, the update was repeatedly failed to install and show as ‘pending reboot’, which is a strange VRI in history.
Overall, there is some degree of wonders going on here, as Windows Hello errors are pretty weird, just like some of these installation failures. However, am I surprised by that? No, because Windows 11 24H2 has produced some very off-the-wall-bugs (and general bizarre — also) since it was only last year.
If you are in the mood for some highlights in the more extreme odds that have been applied to us by version 24h2, read on …
3 of the weirdest Windows 11 -Bugs
1. Language exchange goes completely out of the rails
Some of the most peculiar bugs I have ever seen have appeared in Windows 11, and especially in the 24H2 update.
One of my favorites – if it’s the right word (it’s probably not if you were affected by this problem) – is wrench in the works somewhere deep in Windows 11 that caused the operating system to be shown as a mixture of two different languages. This happened when some users changed the language of Windows 11 from one choice to another, after which a great deal of the operating system’s menus and text remained in the original language. Confusing? No doubt. How did it even happen? I don’t have a clue.
2. Confusing deletion of Copilot
Last month, Microsoft administered a real doozy by allowing a mistake through the actually ditched copilot. Yes, at a time when the software giant is desperately trying to promote his AI assistant and rally support, last month’s patch copilot apparated for some Windows 11 users. It was very embarrassing for Microsoft, especially as some people thought it was the first Windows Bug they were happy to be hit by.
3. See more – or less – of File Explorer
A really memorable to me was late last year when Windows 11 24h2 was occupied by a problem where a menu in File Explorer (the folders on your desk) flew off the top of the screen. Yes, the ‘See More’ menu, which offers more options to interact with files, went past the border on the screen, so most of it wasn’t visible – you saw less of it, ironically. And that meant you couldn’t use these non-visible options.
Again, how did Microsoft broke a large part of Windows 11 interface in such a basic raw way? Your guess is as good as mine, but I suppose the transition to a new underlying platform for Windows 11 24h2 had something to do with it. (This error has only just been corrected, and it happened to this recent April update).
