Microsoft is investigating annoying Windows 11 -Bug that does not leave PCs on startup – this is what you need to know
- Advertisement -
- Windows 11 22h2 and 23h2 have been hit by a bug that can leave a PC that cannot start up
- Microsoft is investigating this recovery error in the May -Update
- Windows 11 -Thuis users will probably not be hit, we will be told, but that does not mean that they cannot encounter this showstopping affair
Those who have not yet installed the latest cumulative update Windows 11 In May – by which I mean, the upgrade that was last released the week, not the Most recent optional update – must be aware of an annoying bug that some users encounter.
Microsoft has said that it is investigating whether the May update can cause a showstopping error, which means that your PC will not start. However, this warning is supplied with a welcome reservation that it will probably not affect Windows 11 Home Users. Yet that possibility is not excluded, and given the severity of the bug, it is worth keeping in mind when you are about to pull the tractor over this cumulative update.
Bleeping Computer Reports that Microsoft has updated its release Health Dashboard with Information about De BugAnd how the upgrade could fall with a ‘recovery error 0xc0000098 in the ACPI.Sys message.
However, this is not a simple error or installation failure, because Windows 11 is unable to start up and a repair requires to be performed on the system. And whether that repair Will be successful, a person’s gamble is, because sometimes these are the kind of situations that are difficult to recover from – and the operating system will not necessarily pull itself out of the hole that has been dug.
The good news is that affected devices with Windows 11 22h2 and 23h2 – notice that 24h2 is not influenced here – are little in number. In the first place, this problem relates to virtual machines, not physically Windows 11 -PCs.
Microsoft explains: “Windows house users using home or pro editions will not face this problem, because virtual machines are usually used in IT environments.”
However, being ‘unlikely’ is not equal to being impossible, and so there must have been some reports of Windows 11 PCs (in contrast to contrary to Virtual machines) are influenced by this unfortunate problem.
I have found such a recent report about RedditAlthough it is not explicitly linked to the latest update that is installed, so take that with a grain of salt. The error message was also somewhat different, but in his warning Microsoft acknowledges that a different file name than ACPI.Sys can appear in the error.
Analysis: A careful approach can be wise here
Microsoft would not announce such an investigation lightly, so if you have not yet installed the Update May, I think it is worth postponing the installation of that upgrade for a little longer. Mainly to enable Microsoft to complete his research here, after all, did you wait a few weeks (for whatever reason), so what is another week, or maybe a little longer?
It is possible to pause OS updates for more than a month, even on Windows 11 Home, although you are forced to apply a certain patch after 35 days after postponing.
In this extra time you can wait until Microsoft completes its deeper dive in what is going on here, and hopefully that will lead to a solution being implemented soon.
Admittedly, you would probably be very bad luck to come across this recovery error, but even a small chance is unpleasant, since it could be a potentially thorny problem to free yourself. Ultimately, the choice of you is, and if you have already installed the May update without encountering such a mistake, I have to make it clear that you don’t have to make anything.
Microsoft has not had a great time of things lately when it comes to bugs of a seriously unpleasant nature, because there was a real stab in the tail Some Windows 10 users with the update Mayat.
Maybe you like it too …
- Advertisement -
