- Windows 11 24h2 Windows Patch causes odd bugs
- There are several problems with Windows Hello connections
- The update also does not manage to install for some people
The latest Windows Correct 11 24H2 causes problems with the failures to be installed (again) and also Windows Hello is broken in some cases.
Let’s start with the bug in Windows Hello, which is the function that allows secure connections to your PC (via facial recognition using a webcam, or other more methods).
The latest Windows reports that some users have found that the cumulative update for April 2025 (known as KB50555523) affects those who use Windows Hello for facial recognition with a confidentiality shutter on the webcam.
How does a facial connection work even with a confidentiality shutter masking the camera? Well, it works very well because the technology uses an infrared sensor on the camera that can work through a physical component (a plastic cursor that people more concerned about privacy use to exclude any danger than they are spying via webcam).
The problem is that the April update seems to spoil with the infrared sensor, so the connection no longer works unless you open this confidentiality shutter – which is hardly ideal.
Windows found the problem present on an HP spectrum laptop, also highlighting a report by a Windows 11 user which was affected by this bug and said to us: “I reproduced the problem several times, with several clean installations. The webcam we use is the Logitech Brio 4K, with the latest firmware and drivers, which is compatible with Windows Hello. ”
There are also other reports on Reddit, like this: “I just wanted to see if someone else encounters problems with the recognition of Windows Hello Face since the last update (KB5055523). Before, I had the camera cover (brilliance 4K) and it would not work. Now I have to remove the confidentiality coverage to recognize myself.
There are a number of responses from people who echo that they have the same bug affecting their connections. The only solution is apparently to uninstall the April update (which strongly suggests that this is a problem caused by this last Microsoft corrective).
That said, Windows Last offers a possible solution, which is obtained by heading towards device Manager (Just type this in the Windows search area and click on it). There, you must click on the small arrow next to where he says’Cameras“And then you can see two listed cameras – the IR camera (infrared) and the RGB / color (normal) camera. Right click on the latter and deactivate it, but leave the infrared camera. Now, if you will again configure Windows Hello, this can work properly.
Windows Dernit does not guarantee this, however, and says that it will only make the tip for some Windows 11 users. If you desperately have to make a fix, you can give a whirlwind, because you could wait a little bit of Microsoft’s official solution. Remember that you will of course have to reorganize the main camera (RGB) once any corrective has been applied.
Interestingly, in the official notes of the notes for the April update, Microsoft signals a problem with Windows Hello – but not this one. Rather, this is a separate problem, although the one who should not affect those who execute Windows 11 at home.
Microsoft explains: “We are aware of a Windows Hell Hell problem with a problem with devices with specific safety features activated … Users can observe a Windows Hello message saying” Something has happened and your PIN code is not available. Click to restore your PIN code “or” Sorry, something went wrong with the configuration of the face “.” »»
Microsoft provides instructions on what to do if you encounter this particular problem via its putting notes in April (under known problems).
However, this bug affects only those who use the System Guard Secure launch (or dynamic confidence root for measurement), which is only supported on Windows 11 Pro (or Endition Editions). So, as indicated, if you are on Windows 11 Home, you should not meet this hiccup.
Installation blues
Windows last also took a second major problem, namely installation failures (which are not new). These seem to reproduce with the April 2025 update, with error messages devoid of usual sense accompanying a unsuccessful attempt (hexadecimal arrest errors such as “0x80070306”).
The technological site notes that it has verified the update reports which does not settle in this way, or its progress is blocked at 20% or 70% in some cases, never really ending. Windows the last informs us that Microsoft apparently studies these installation failures.
There are other reports of this type of problem on the Answers.com help forum of Microsoft (and certain possible suggestions of solutions of a customer service representative, some of which would have worked for some, but not for others). In the case of the original poster of this thread, the update failed to install and display the “restart restart”, which is a strange touch in the tale.
Overall, there is therefore a certain degree of oddity here, because the failures of Windows Hello are rather strange, just like some of these installation problems. Am I surprised, however? No, because Windows 11 24H2 has produced very offbeat bugs (and an in addition bizarish general) since it was born at the end of last year.
If you are in the mood for certain protruding facts of the most extreme quirks that have been inflicted on us by the 24H2 version, read the rest …
3 of the strangest bugs of Windows 11
1. The exchange of language goes completely from the rails
Some of the most special bugs I have ever seen surfaced in Windows 11, and in particular in the 24 -hour update.
One of my favorites – if this is the right word (it is probably not if you have been affected by this problem) – is the space in preparation somewhere in Windows 11 which caused the display of the operating system as a mixture of two different languages. This happened when some users changed the language of Windows 11 from one choice to another, after a large part of the menus and the text of the operating system remained in the original language. Confusing? No doubt. How did it even happen? I have no idea.
2.
Last month, Microsoft managed a real Doozy by allowing a bug via this abandonment co -pilot. Yes, at a time when the software giant desperately tries to promote its AI assistant and its rally support, the corrective of last month uninstalled the Copilot application for some Windows 11 users. It was very embarrassing for Microsoft, especially since some people estimated that it was the first Windows bug with which they were happy to be struck.
3. See more – or less – File Explorer
A more memorable for me was at the end of last year when Windows 11 24h2 was assaulted by a problem by which a menu in File Explorer (the folders of your office) flew to the top of the screen. Yes, the “see more” menu offering more options to interact with the files exceeding the edge of the screen, so most were not visible – you have seen less, ironically. And that meant that you could not use these undisputed options.
Again, how did Microsoft broke a major part of the Windows 11 interface in such a fundamentally raw manner? 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. (This bug has just been corrected, moreover, and this happened with this last April update).
