Windows 10 Home stops booting possibly due to end-of-life status.
Windows 10 Home stops booting possibly due to end-of-life status.
Hello Friends
Today I tried using a laptop with Windows 10 Home installed on one laptop. Normally the machine boots as expected, but this time it loads the BIOS directly instead. That means it can't boot into Windows 10. What should I do? I think it might be related to the end of support, but I wonder if it's still possible to install the OS safely. Of course, no updates are coming soon. Thanks in advance.
What is the make, model, and SKU of your laptop? When prompted for the BIOS screen, check the Boot Device Priorities—ensure the OS drive and Windows Boot Manager appear. If they aren't listed, it may indicate the drive has failed.
Both of your 2x Windows 10 systems are still booting without issues. The issue must be elsewhere.
Based on the provided details, here is the rewritten version:
Thanks for all the responses.
I have the following information.
In the BIOS under the "Boot" Menu, there is a setting labeled "Empty here should appear the SSD." Even when the USB is connected, the boot process does not start; instead, the BIOS loads. However, later it becomes possible to identify both devices—USB and SSD.
For the "Add New Boot option," the item appears.
Therefore, when working with the first two options, the "Add boot option" field must be given a custom name such as "USB" or "Windows10" depending on the context.
For the "Path for boot option," it shows the SSD and USB respectively with specific configurations according to navigation.
Note: The "*" is only used to enhance the hierarchy.
Code:
Path for boot option
PCI(1D|0)\PCI(0|0)\DevicePath(Type 3, SubType 17)HD(Part1, Sig<possible-uuid>) <--- SSD
* <EFI>
* <..> (to return)
* <Microsoft>
* <..> (to return)
* <Boot>
* <..> (to return)
* ... more options ...
* <en-GB>
* <en-US>
* <es-ES>
* <es-MX>
* ... more options ...
* <Fonts>
* ... more options ...
* <qps-ploc>
* <..> (to return)
* <Resources>
* <..> (to return)
* <en-US>
* <es-ES>
* <fr-FR>
... more options ...
* SecureBootRecovery.efi
* memtest.efi
* bootmgr.efi
* bootmgfw.efi
</...>
* <Recovery>
* <..> (to return)
</EFI>
* <Boot>
* <..> (to return)
* bootx64.efi
* <System Volume Information>
PCI(14|0)\USB(15,0)\HD(Part2,Sig23919B4D) <--- USB
* <grub>
* <arm64-efi>
* ... (details omitted for brevity)
</...>
* <System Volume Information>
PCI(1D|0)\PCI(0|0)\DevicePath(Type 3, SubType 17)HD(Part2, Sig23919B4D) <--- USB
</...>
* ... additional sections ...
</EFI>
Thank you.
Thank you for the explanation.
I only tested for the SSD... I picked "bootmgfw.efi" and made the save and exit steps.
But it didn't work; the BIOS reappeared.
I repeated the process a few times, but there was a section labeled "Boot Overridden" showing a custom boot option.
So I selected that instead of saving and exiting.
The result was that the BIOS closed and Windows 10 Home loaded.
It's unclear if the motherboard battery is nearly dead and needs replacement. The BIOS might be reacting as a protective measure. This seems like a simple theory since the BIOS time matches what I see.
Thanks for your help!
It seems the boot choice was introduced but not set as the standard setting. Typically, a BIOS selection screen appears during startup (BBS), and pressing F11 usually activates it, though it might differ from what you expect.