Because the vacations concern all developers... but not the bugs!
Earlier this week, Microsoft made a point of clarifying its schedule for updates to its Windows 10 and Windows 11 operating systems. Finally, it especially wanted to emphasize that the month of December would not know any "factual" update. You know, these updates that focus neither on bugs nor on security and are rather planned to bring "second zone" features, small things that are not essential to the proper functioning of the OS, but which participate in its specificity.
As Bleeping Computer explains, there will be no such updates for the whole of December, and everything leads us to believe that if such updates arrive in January, it won't be at the beginning of the month. Indeed, Microsoft explains that it has taken the decision "exceptionally" to focus on security updates. The reason for this change of perspective is not to be found in a particular increase in threats, Microsoft made the decision in relation to the calendar: " Due to minimal operations during the vacations and the upcoming Western New Year, there will be no unsecured preview release for December 2022. There will be a monthly security release (known as a "B" release) for December 2022. Normal monthly service for both the B and C releases will resume in January 2023."
However, there is no question of resting completely and security updates are planned as usual... well almost. Indeed, while the last Patch Tuesday seemed to be rolled out as normally as possible, many users started to report "blue screen" problems. To be exact, the incriminated update is the KB5021233 which we advise you not to deploy for the moment. The problem causing the appearance of these Blue Screens Of Death would be related to an incompatibility in the system file hidparse.sys present in two different system folders.
For the bad news, that's about it and, fortunately, the good news are more numerous. First of all, the bug does not affect all users and only some users of Windows 11 versions 22H2/21H2 and Windows 10 version 21H1 are affected. Second good news, if your PC has restarted properly after the update was deployed, you won't encounter the problem: it declares itself immediately. Finally, and this is probably the most important, Microsoft is aware of the problem.
The editor's teams are already working on a fix, which we hope will not take too long. In the meantime, Microsoft is detailing a maneuver that should allow the problem to be remedied. Unfortunately, the said maneuver will not be easy to apply for everyone: it actually requires using the Windows Recovery Environment (WinRE) and following the different steps detailed by Microsoft on its learn.microsoft.com website.
