Problems starting Windows after the battery runs out

Julian Holzenthal 20 Reputation points
2026-08-19T08:24:37.8+00:00

We have been experiencing an issue for several weeks where some notebooks are unable to boot into Windows properly after the battery has been fully discharged, in some cases multiple times. Instead, the devices often enter the Windows Recovery Environment and fail to start normally.

The recovery options do not resolve the issue. Interestingly, the behavior suggests that systems configured with RAID On are no longer able to properly detect the SSD after the battery has been completely depleted. If the storage mode is changed from RAID On to AHCI, the SSD becomes visible again, but Windows still fails to boot.

Another observation is that the Windows Boot Manager entry is missing from the boot menu, leaving no option to start Windows directly.

Initially, we reinstalled some of the affected devices to get them working again. However, last week I came across a post from 2023 that described a very similar issue. (https://learn.microsoft.com/en-us/answers/questions/4121637/windows-11-boot-stuck-at-windows-recovery-environm?page=4)

The solution mentioned in that post, recreating the boot partition, also resolves the problem in our environment. While this provides a workaround, I would be interested to understand the root cause of the issue and why it appears to be triggered by a complete battery discharge.

Windows for business | Windows Client for IT Pros | Devices and deployment | Other
0 comments
Answer accepted by question author
Domic Vo 29,960 Reputation points Independent Advisor
2026-08-19T09:27:23.3566667+00:00

Hello Julian Holzenthal,

The behavior you're describing is a known issue in scenarios with RAID enabled (Intel RST/RAID Mode) and completely discharged batteries. When the battery is completely depleted, some systems lose the NVRAM entries for the boot manager, and the RAID configuration is no longer initialized correctly. As a result, the SSD is not recognized in RAID mode, while it remains visible in AHCI mode, albeit without a valid bootloader. The fact that the Windows Boot Manager disappears from the boot menu is a direct symptom that the EFI boot partition is no longer being referenced correctly.

The cause is that the firmware does not properly persist the RAID metadata during power loss, and the UEFI boot order is reset. Windows itself remains intact, but the boot partition entries in the EFI system partition (ESP) need to be recreated. This explains why the solution using bcdboot C:\Windows /s <ESP> /f UEFI or manually recreating the boot partition immediately resolves the issue. It's not a file system error, but rather a loss of the boot configuration due to the combination of RAID on and battery drain.

In the short term, you can recreate the boot partition after each incident. In the long term, you should check if a firmware update is available for the RAID controller or BIOS, as some manufacturers have already addressed this behavior. Alternatively, switching to AHCI can circumvent the problem, but this requires a clean installation, as Windows cannot easily switch between RAID and AHCI.

If my answer is helpful, please click "Accept the answer" to support me.

Thank you,

Domic.

Was this answer helpful?

1 person found this answer helpful.
0 comments

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.