- Windows 11 22H2 and 23H2 have been hit by an error that can leave a PC that is unable to start up
- Microsoft is investigating this recovery failure error in the May Update
- Windows 11 Home users are unlikely to be affected we will be told but that doesn’t mean they can’t run into this showstopping affair
Those who have not yet installed the latest cumulative update to Windows 11 in May – where I think the upgrade released the week before last, not the latest optional update – should be aware of an ugly error that some users encounter.
Microsoft has said it is investigating whether the update in May can cause a showstopping error, which means your PC is not starting. However, this warning comes with a welcome warning that it is not likely to affect Windows 11 home users. Still, this option is not excluded and given the error of the error it is worth keeping in mind if you are dragging the trigger on this cumulative update.
Bleeping Computer reports that Microsoft has updated its release Health Dashboard with information about the error and how the upgrade can fall over with a ‘Restore Error 0XC0000098 in ACPI.SYS’ MESSAGE.
However, this is no simple error or installation error because it leaves Windows 11 unable to start and requires a repair to be run on the system. And about that repair Will be successful is someone’s guess as sometimes it is the kind of situations that are difficult to recover from – and the operating system does not necessarily withdraw from the hole that has been dug.
The good news is that affected devices running Windows 11 22H2 and 23H2 – Note that 24h2 is not affected here – are few in number. Primarily relating to this problem virtual machines, not physical Windows 11 pitches.
Microsoft explains: “Home users of Windows who use home or pro editions are unlikely to be this problem as virtual machines are mostly used in IT environments.”
However, being ‘unlikely’ does not correspond to being impossible, and therefore there must have been some reports on Windows 11 -PCs (as opposed to virtual machines) that are affected by this unfortunate problem.
I found such a recent report on Reddit, although it is not explicitly linked to the latest update installed, so take it with a grain of salt. The error message was also slightly different, but in his warning, Microsoft recognizes that a file name other than ACPI.SYS may appear in the error.
Analysis: A cautious approach can be wise here
Microsoft would not advertise such a study easily, so if you have not yet installed the May update, I think it is worth considering postponing the installation of this upgrade a little longer. Mainly to give Microsoft the opportunity to conduct his study here, after all, you have waited a few weeks (for whatever reason) now, so what is another week or maybe a little longer?
It is possible to put us up for over a month, even on Windows 11 home, though you are forced to use a given patch after 35 days of postponement of it.
In this extra time, you can wait for Microsoft to finish its deeper dive into what is going on here, and hopefully it will lead to a solution soon to be implemented as well.
Granted, you would probably be very unlucky to encounter this recovery error, but even a small chance is disgusting, given that it can be a potentially thorny problem to unpack yourself. In the end, the choice is yours and if you have already installed the May update without meeting any such mistake, I have to make it clear that you have nothing to worry about.
Microsoft doesn’t have a good time with things recently when it comes to bugs of seriously unpleasant nature, as there was also a real stitch in the tail of some Windows 10 users with the May update.
