- Windows 11 22h2 and 11:2 p.m. were struck by a bug that can leave a PC unable to start
- Microsoft is investigating this recovery error problem in the May update
- It is unlikely that Windows 11 home users will be affected, we say to each other, but that does not mean that they cannot meet this case of presentation
Those who have not yet installed the last cumulative update of Windows 11 in May – by which I mean that the upgrade published the previous week, and not the most recent optional update – should be aware of an unpleasant bug that some users meet.
Microsoft said he was studying if the May update can cause a presentation error, which means that your PC does not start. However, this warning is delivered with a welcome warning that he has probably not affected Windows 11 users. However, this possibility is not excluded, and taking into account the seriousness of the bug, it is worth keeping in mind that if you are about to pull the trigger on this cumulative update.
Bleeping Computer reports that Microsoft has updated his Health Release dashboard with information on the bug, and how the upgrade could fall with a “0xc0000098 recovery error in the message of ACPI.SYS.
It is not a simple error or an installation failure, as it leaves Windows 11 unable to start and requires repair to be executed on the system. And if that repair Will be the success is the assumption of anyone, because sometimes these are the kind of situations that are difficult to recover – and the operating system will not necessarily withdraw from the hole that has been dug.
The good news is that the assigned devices executing Windows 11 10:2 p.m. and 11:2 p.m. – note that 24h2 is not affected here – are few. Mainly, this problem concerns virtual machines, not physical Windows 11 PCs.
Microsoft explains: “Windows home users using home or pro editions are unlikely to deal with this problem, as virtual machines are mainly used in IT environments.”
However, being “improbable” does not equivalent to being impossible, and there must therefore have been Windows 11 PC reports (as opposed to virtual machines) affected by this unfortunate problem.
I found such a recent report on Reddit, although it is not explicitly linked to the last update installed, so take this with a grain of salt. The error message was also slightly different, but in its warning, Microsoft acknowledges that a file name other than Acpi.sys could appear in error.
Analysis: a cautious approach can be wise here
Microsoft would not light up such a survey lightly, so if you have not yet installed May’s update, I think it is worth considering the installation of this upgrade a little longer. Mainly to allow Microsoft to finish his investigation here, after all, you waited a few weeks (for any reason) now, so what is another week, or maybe a little more?
It is possible to break the operating system updates for more than a month, even on Windows 11 Home, although you are forced to apply a given fix after 35 days of postponement.
At this additional time, you can wait until Microsoft ends his deeper dive in what is happening here, and I hope that this will lead to a fixing in the course of implementation soon.
Admittedly, you would probably be very unlucky to meet this recovery error, but even a small chance is off -putting, since it could be a potentially thorny problem to extract you. In the end, the choice belongs to you, and if you have already installed the May update without meeting such an error, I should clearly indicate that you have nothing to fear.
Microsoft has not had a good time in recent times with regard to bugs of a very unpleasant nature, because there was also a real bite in the tail for some users of Windows 10 with the May update.
