- Windows 11 24h2’s April patch is causing some strange mistakes
- There are multiple problems with the Windows Hello session late
- The update is also not completely installed for some people.
The last Windows 11 24h2 patch is causing some problems with the failures to install (once again) and also Windows Hello is ending in some cases.
Let’s start with the error in Windows Hello, which is the characteristic that allows safe session on its PC (through facial recognition using a webcam or other methods in addition).
The latest Windows reports that some users have discovered that the accumulated update for April 2025 (known as KB5055523) is affecting those who use Windows Hello for facial recognition with a privacy shutter in the webcam.
How does a facial login work even with a privacy shutter that darkens the camera? Well, it works well because technology takes advantage of an infrared sensor in the camera that can work through a physical shutter (a plastic slider than the most aware people of privacy use to rule out any danger that they leave through the webcam).
The problem is that the April update seems to mess with the infrared sensor, so logging no longer works unless that privacy shutter opens, which is not ideal.
Last Windows found the problem present on an HP Specter laptop, which also highlights a report by a Windows 11 user who has been affected by this error and tells us: “I have reproduced the problem several times, with several clean facilities. The webcam we are using is the Logitech Brio 4K, with the latest firmware and controllers, which is compatible with Windows Hello.”
There are also other reports about Reddit, such as this: “I just wanted to see if someone else is experiencing problems with the recognition of Windows Hello Face since the last update (KB5055523). Before, I had the camera (Brio 4K) cover and it would work well. Now, I have to eliminate the privacy cover to recognize me. It does not seem that I cannot unlock with the infrared chamber now.” “.” “.” “.” “.” “.” “.”
There are a number of responses from people who echo that they have the same error that affects their session. Apparently, the only solution is to uninstall the April update (which strongly suggests that this is a problem caused by this last Microsoft patch).
That said, Windows Last offers a possible solution, which is achieved when heading to Device administrator (Simply write that in the Windows search box and click on it). There, you must click on the small arrow next to where it says’Cameras‘And then you can see two listed cameras: the IR (infrared) camera and the RGB/color (normal) camera. Right click on the latter and disregard it, but left the infrared camera on. Now, if you go and configure Windows Hello again, you can work properly.
However, Windows Last does not guarantee this, and says that this will only do the trick for some Windows 11 users. If you are desperate for a solution, you can take a turn, since you could be waiting for a time for the official Microsoft solution. Do not forget that, of course, you will have to re -enable the main camera (RGB) after any solution is applied.
Interestingly, in the official notes of the patch for the April update, Microsoft marks a problem with Windows Hello, but not this. Rather, this is a separate problem, although it should not affect those who execute Windows 11 at home.
Microsoft explains: “We are aware of a case of Windows HELLO’s edge.
Microsoft provides instructions on what to do if you find this particular problem through its April patch notes (on known issues).
However, this error only affects those who use the safe launch of System Guard (or dynamic confidence root for measurement), which is only admitted in Windows 11 Pro (or business editions). So, as noted, if you are in the house of Windows 11, you should not meet this hiccup.
Installation blues
Windows Last also collected a second important problem, namely installation failures (which are not new). These seem to be happening again with the April 2025 update, with the usual unsect error messages that accompany a failed attempt (hexadecimal stop errors such as ‘0x80070306’).
The technology site indicates that it has verified the reports of the update that is not installed in this way, or its progress is stuck at 20% or 70% in some cases, it was never completed. Last Windows informs us that Microsoft is apparently investigating these installation failures.
There are other reports of this type of problem in the Microsoft Answers.com forum (and some possible solutions of solutions from a customer service representative, some of which have worked for some, but not for others). In the case of the original poster of this thread, the update was not installed repeatedly and showed as ‘pending restart’, which is a strange turn in the story.
In general, then, there is a certain degree of rarity here, since Hello Windows failures are quite strange, as are some of these installation problems. However, does that surprise me? No, because Windows 11 24h2 has produced some errors very out of the wall (and a general strangeness in addition) since it arrived at the end of last year.
If you are in humor for some prominent aspects of the most extreme oddities that have been inflicted on version 24h2, keep reading …
3 of the most strange Windows 11 mistakes
1. Language exchange is completely out of the rails
Some of the most peculiar mistakes I have seen have appeared in Windows 11, and particularly in the 24h2 update.
One of my favorites, if that is the right word (it is probably not if it was affected by this problem), it is the key in the works somewhere in the depths of 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 in Windows 11 from one option to another, after which a good part of the menus and the text of the operating system remained in the original language. Confused? No doubt. How did it even happen? I have no idea.
2. Disconcerting deletion of Copilot
Last month, Microsoft achieved a real dozy by allowing an error through that really abandoned co -pilot. Yes, at a time when the software giant desperately tries to promote its AI and Rally support assistant, last month’s patch uninstalled the Copilot application for some Windows 11 users. That was very shameful for Microsoft, especially because some people felt it was the first Window error with which they were pleased to be beaten.
3. See more, or less, by File Explorer
One really memorable for me was at the end of last year when Windows 11 24h2 was harassed by a problem by which a menu in the file explorer (the folders on his desk) flew from the top of the screen. Yes, the ‘See more’ menu that offers more options to interact with the files passed through the edge of the screen, so most was not visible, he saw less, ironically. And that meant that you could not use those unesisable options.
Again, how did Microsoft break an important part of the Windows 11 interface in such a fundamentally raw? Your assumption is as good as mine, but I suspect that the transition to a new underlying platform for Windows 11 24h2 had something to do with that. (By the way, this error has just been solved, and that happened with this most recent April update).
