A computer that repeatedly opens the BIOS/UEFI Setup Utility instead of Windows can be confusing, especially when pressing F10 – Save & Exit occasionally starts Windows but, on another restart, the system returns to BIOS again.

This behavior is particularly important when the system date and time remain correct, because it suggests that the problem may not simply be a dead CMOS battery. More commonly, the system is having difficulty locating, detecting, or starting the Windows boot device.

This technical guide explains the possible causes, how to diagnose them systematically, and how to distinguish between a BIOS configuration problem, SSD/HDD problem, Windows Boot Manager issue, EFI partition corruption, or hardware fault.

1. Understanding the Problem

The normal startup sequence of a Windows computer is approximately:

Power On → POST → BIOS/UEFI → Detect Storage → Select Boot Device → Windows Boot Manager → Windows

When everything works correctly, the BIOS identifies the configured boot device and transfers control to its bootloader.

When something fails during this sequence, the motherboard may automatically enter BIOS Setup.

A typical symptom is:

Power ON → BIOS appears → F10 Save & Exit → Restart → Windows sometimes starts

or:

Power ON → BIOS appears → F10 Save & Exit → Restart → BIOS appears again

The second situation strongly suggests that the firmware cannot find a valid boot target.

2. Most Common Causes

The problem generally falls into one of these categories:

• SSD/HDD is intermittently or completely undetected
• Windows Boot Manager is missing from the boot list
• Incorrect boot priority
• UEFI/Legacy/CSM mode mismatch
• Damaged EFI System Partition
• Corrupted BCD or Windows boot files
• SATA data or power cable problem
• Failing SSD/HDD
• Faulty SATA port
• BIOS settings unexpectedly changing
• CMOS battery issue
• Recently installed/replaced storage device
• Multiple drives creating boot conflicts
• BIOS firmware problem
• Motherboard/storage controller problem

The troubleshooting process should identify which stage of the boot process is failing before attempting repairs.

3. First Check: Is the Windows SSD/HDD Detected?

This is the most important initial test.

Enter BIOS and look under menus such as:

Main → Storage

Advanced → SATA Configuration

Advanced → Storage Configuration

Advanced → NVMe Configuration

or similar options depending on the motherboard.

Look for the model number of the SSD/HDD containing Windows.

For example:

Samsung SSD 870 EVO 500GB

Kingston SA400S37240G

Crucial MX500

WD Blue SN570

If the drive is detected

The physical storage connection is at least functioning at that moment. Continue to checking Windows Boot Manager.

If the drive is NOT detected

Do not immediately attempt Windows boot repair.

Windows cannot boot from a disk that the motherboard cannot detect.

The problem is more likely to involve:

SSD/HDD → Cable → Connector → SATA/NVMe interface → Motherboard

4. Check Windows Boot Manager

Open the BIOS Boot section.

Look at:

Boot Option #1

For a typical modern Windows UEFI installation, you may see:

Windows Boot Manager (SSD Model)

This is generally what should be selected as the first boot option.

For example:

Boot Option #1: Windows Boot Manager

Boot Option #2: USB Device

Boot Option #3: Network/PXE

Save the configuration using F10 → Save & Exit.

Important distinction

Seeing the SSD in BIOS does not necessarily mean that Windows is bootable.

BIOS may detect:

Kingston SSD 480GB

but still not show:

Windows Boot Manager

That distinction is extremely useful during diagnosis.

5. SSD Detected but Windows Boot Manager Missing

Suppose BIOS detects the SSD correctly, but Windows Boot Manager does not appear under boot options.

Possible causes include:

• EFI boot entry has been deleted
• EFI System Partition is corrupted
• BCD configuration is damaged
• BIOS was reset
• UEFI mode changed
• CSM/Legacy settings changed
• Disk was cloned incorrectly
• Windows boot files reside on another disk that was removed
• EFI partition was accidentally deleted

At this stage, Windows itself may still be completely intact.

Do not format or reinstall Windows just because Windows Boot Manager is missing.

Boot repair may be sufficient.

6. UEFI vs Legacy/CSM Boot Mode

Modern Windows installations generally use:

UEFI + GPT

Older installations may use:

Legacy BIOS/CSM + MBR

If Windows was installed using UEFI but the BIOS is configured for Legacy boot, the firmware may fail to find the expected UEFI bootloader.

Likewise, an old MBR/Legacy Windows installation may not start when the machine is configured for UEFI-only boot.

Typical UEFI configuration

You may see:

Boot Mode: UEFI

Windows Boot Manager

Secure Boot

Legacy configuration

You may instead see:

Legacy

CSM

Legacy Boot

HDD model directly as boot device

Do not randomly switch UEFI/Legacy settings on a production computer. First determine how Windows was originally installed.

7. Why F10 Sometimes Makes Windows Start

This symptom is particularly interesting:

Computer enters BIOS → Press F10 → Restart → Windows starts

It can indicate an intermittent detection problem.

During the first power-on, the SSD may not become ready quickly enough or may fail detection.

After entering BIOS, several seconds pass.

When F10 is pressed, the computer restarts, and the SSD may now be ready and detected correctly.

Possible causes include:

• Aging SSD/HDD
• Slow initialization
• SATA cable problem
• Loose power connection
• Weak SATA connector
• SSD controller issue
• Motherboard SATA controller issue
• PSU power instability
• BIOS compatibility/initialization issue

This behavior deserves hardware investigation even when Windows eventually starts.

8. Check the SATA Data Cable

For a SATA SSD/HDD, shut the PC down completely and disconnect power.

Inspect:

Motherboard SATA Port → SATA Cable → SSD/HDD

Reconnect both ends firmly.

If possible, replace the SATA cable with a known-good cable.

A SATA cable can fail intermittently. The disk may work normally for days and then disappear during POST.

This can produce exactly the symptom:

BIOS → Restart → Windows

9. Check the SATA Power Cable

The SSD/HDD also needs stable power from the PSU.

Check:

PSU → SATA Power Connector → SSD/HDD

Try another SATA power connector if available.

A drive receiving unstable power may fail to initialize during cold boot but work after a restart.

That can easily be mistaken for a Windows software problem.

10. Try Another SATA Port

If the SATA cable is known to be good, move the drive to another motherboard SATA port.

For example:

SATA1 → SATA2

Then enter BIOS and confirm detection.

This helps distinguish between:

Drive problem

and:

Motherboard SATA port problem

11. NVMe SSD Systems

For an NVMe SSD, there is no SATA data cable.

Check BIOS for something similar to:

NVMe Configuration

Confirm that the NVMe drive is detected.

If not, possibilities include:

• SSD not seated correctly
• M.2 slot issue
• SSD failure
• BIOS configuration
• M.2/SATA lane-sharing configuration
• Motherboard compatibility
• SSD controller failure

Power the machine off before physically reseating an M.2 drive.

12. Check SSD/HDD Health

If Windows eventually starts, use that opportunity to check drive health immediately.

For SATA drives, SMART data can reveal problems such as:

• Reallocated sectors
• Uncorrectable errors
• Pending sectors
• Interface errors
• Excessive temperature
• Drive health warnings

For SSDs, also check:

• Remaining life
• Media/data integrity errors
• Critical warnings
• Available spare
• Unsafe shutdown count
• Manufacturer-specific health indicators

However, a SMART status of "Good" does not guarantee that the drive, cable, power connection, or controller is healthy.

13. Back Up Important Data First

When a computer intermittently fails to detect its boot drive, data backup should become a priority.

Once Windows successfully starts, copy important business and user data before performing aggressive repair operations.

The system might currently recover after F10, but an intermittently failing drive could eventually stop being detected completely.

14. Check Whether BIOS Settings Are Being Lost

A weak CMOS battery can cause BIOS settings to reset.

Common symptoms include:

• Incorrect system date/time
• Boot order repeatedly resetting
• UEFI/Legacy settings changing
• BIOS configuration being forgotten after power removal
• CMOS checksum messages

A common desktop motherboard battery is a CR2032.

But what if the time is correct?

If the BIOS date and time remain correct, a completely dead CMOS battery becomes less likely.

However, it should not be ruled out solely based on time. Check whether the boot settings themselves remain saved after:

1. Saving BIOS settings
2. Shutting down
3. Disconnecting AC power
4. Waiting
5. Powering the machine on again

If settings revert, investigate CMOS/RTC power and motherboard behavior.

15. Do Not Immediately Load Optimized Defaults

Many BIOS screens provide:

F9 – Optimized Defaults

Loading defaults is useful in some situations, but it should not be the first troubleshooting step on an existing Windows installation.

It can potentially alter:

• UEFI/Legacy mode
• CSM
• Secure Boot
• SATA controller mode
• AHCI/RAID configuration
• Boot priority
• Virtualization settings
• Other hardware options

A SATA mode change is particularly important.

For example:

AHCI → RAID

or:

RAID → AHCI

can cause Windows boot failure if the OS is not prepared for that controller mode.

Record the current BIOS settings before making changes.

16. Check SATA Controller Mode

Look under BIOS options such as:

Advanced → SATA Configuration

Possible modes include:

AHCI

RAID

IDE

If Windows was installed with AHCI and the setting unexpectedly changes to RAID or IDE, Windows may fail to start.

Do not change it blindly.

If the system previously worked with the existing setting, document it before experimenting.

17. Check for Multiple Drives

Systems containing multiple SSDs/HDDs require additional attention.

A surprisingly common configuration is:

Windows installed on SSD

but:

EFI boot files stored on another HDD

This can happen when Windows Setup is performed while multiple disks are connected.

Windows may physically reside on Disk 1 while the EFI System Partition used for startup resides on Disk 0.

If Disk 0 is later:

• Removed
• Replaced
• Formatted
• Disconnected
• Failing

Windows on the SSD may stop booting.

Therefore, don't assume that the disk containing C:\Windows necessarily contains all required boot files.

18. Repairing Windows Boot Manager

If the SSD/HDD is consistently detected but Windows Boot Manager is missing or damaged, boot into the Windows Recovery Environment using Windows installation media.

Choose:

Repair your computer → Troubleshoot → Advanced options → Startup Repair

Try Startup Repair before performing manual BCD reconstruction.

19. Using BCDBoot for UEFI Boot Repair

For a UEFI installation, bcdboot can recreate Windows boot files on the EFI System Partition.

The concept is:

bcdboot C:\Windows /s S: /f UEFI

However, inside Windows Recovery Environment, the Windows partition may not be C:.

It could appear as D:, E:, etc.

Therefore, identify the correct partitions before running the command.

20. Identify the Disk and Partitions with DiskPart

From Windows Recovery Command Prompt:

diskpart
list disk
list volume

Check the volumes carefully.

A typical UEFI Windows installation might contain:

EFI System Partition: FAT32, usually relatively small

Windows Partition: NTFS, large partition containing the Windows folder

Exit DiskPart:

exit

Then identify the Windows partition.

For example:

dir C:\Windows
dir D:\Windows
dir E:\Windows

Once the correct Windows partition is known, boot files can be repaired appropriately.

21. Assigning a Drive Letter to EFI Partition

If necessary:

diskpart
list volume
select volume <EFI volume number>
assign letter=S
exit

Then, assuming Windows is actually on C::

bcdboot C:\Windows /s S: /f UEFI

A successful operation should report that boot files were created.

The volume number and Windows drive letter must be verified on the actual computer. Do not copy example values blindly.

22. What if the Disk Is MBR?

Check:

diskpart
list disk

DiskPart can help determine whether the disk is using GPT.

If the installation is an older Legacy/MBR configuration, the repair process differs from a modern UEFI/GPT installation.

This is another reason not to switch firmware modes randomly.

23. Could Secure Boot Cause This?

Potentially, but Secure Boot is not the first suspect when a previously working PC suddenly starts entering BIOS.

Secure Boot-related problems become more relevant after:

• BIOS reset
• Firmware update
• OS migration
• Disk cloning
• Bootloader modification
• UEFI configuration changes

Do not disable Secure Boot automatically as a generic fix.

24. Could the Power Supply Cause It?

Yes.

A weak or unstable PSU can prevent a storage device from initializing correctly during cold boot.

You might observe:

Cold Boot → Drive missing → BIOS

followed by:

Restart → Drive detected → Windows

Possible reasons include:

• PSU aging
• Weak voltage rail
• Poor SATA power connector
• Splitter/adapter problems
• Loose power cable

If multiple computers develop the same issue around the same time, also consider common environmental factors such as power quality, UPS behavior, or identical aging hardware.

25. Two Computers Showing the Same Problem

When two separate systems start showing the same behavior, investigate what they have in common.

For example:

• Same SSD model/age
• Same motherboard model
• Same BIOS configuration
• Same recent hardware maintenance
• Same disk cloning procedure
• Same Windows deployment image
• Same UPS/power source
• Same BIOS update
• Same storage replacement process

Two machines failing similarly does not automatically mean Windows is responsible.

A shared hardware age, deployment method, or configuration change may be the common factor.

26. Recommended Troubleshooting Order

A safe diagnostic sequence is:

BIOS Date/Time → SSD/HDD Detection → Windows Boot Manager → Boot Priority → UEFI/Legacy Mode → SATA Mode → Cable/Power → Drive Health → EFI/BCD Repair → BIOS/Hardware Investigation

This order is important.

Do not start repairing Windows boot files when BIOS cannot reliably detect the physical disk.

27. Diagnostic Decision Tree

Case A: SSD/HDD not visible in BIOS

Investigate:

Drive → SATA/NVMe connection → Power → Port → PSU → Drive failure

Windows repair is not the priority.

Case B: SSD detected, Windows Boot Manager missing

Investigate:

UEFI configuration → EFI partition → BCD/boot files

Case C: Windows Boot Manager exists but isn't first

Set:

Boot Option #1 = Windows Boot Manager

Save and test.

Case D: Everything looks correct but cold boot still enters BIOS

Investigate:

Intermittent SSD detection → SATA cable → power → PSU → SSD health → BIOS firmware

Case E: BIOS settings keep resetting

Investigate:

CMOS battery → BIOS/RTC settings → motherboard

28. When Should the SSD/HDD Be Replaced?

Replacement should be considered when:

• Drive intermittently disappears from BIOS
• SMART reports serious warnings
• SSD health indicates critical problems
• HDD produces abnormal mechanical sounds
• Read errors occur
• Windows freezes during disk activity
• File corruption repeatedly occurs
• Drive works only after repeated restarts
• Another known-good drive works correctly on the same hardware

Back up data before the drive becomes completely inaccessible.

29. When Should BIOS Be Updated?

BIOS updates can resolve:

• Storage compatibility issues
• NVMe detection problems
• UEFI bugs
• Boot-device compatibility problems
• Hardware initialization problems

But BIOS flashing should not be used as the first diagnostic step.

A failed firmware update can make the motherboard unbootable.

First establish the motherboard model, current BIOS version, target BIOS version, and manufacturer instructions.

30. Important Technician Advice

When diagnosing a PC that repeatedly enters BIOS, avoid making many changes simultaneously.

Record the original settings or photograph the BIOS pages before changing anything.

Change one variable at a time and test:

Change → Save → Shutdown → Cold Boot → Observe

This makes it possible to identify the actual cause rather than merely obtaining one successful boot.

Frequently Asked Questions (FAQ)

Q1. Why does my PC automatically enter BIOS instead of Windows?

Usually because the firmware cannot find or start the configured Windows boot device. The cause may be an undetected SSD/HDD, incorrect boot priority, missing Windows Boot Manager, wrong UEFI/Legacy configuration, or damaged boot files.

Q2. Why does Windows start after pressing F10?

F10 saves BIOS settings and restarts the computer. If Windows starts after the restart, the disk may have been detected on the second initialization. This can indicate an intermittent drive, cable, power, or initialization problem.

Q3. Does correct BIOS time mean the CMOS battery is definitely good?

No. Correct time makes a completely dead battery less likely, but does not conclusively prove that the CMOS/RTC battery and settings retention are perfect.

Q4. Should Windows Boot Manager be Boot Option #1?

For a standard Windows installation using UEFI, normally yes.

Q5. My SSD appears in BIOS but Windows Boot Manager does not. Is the SSD bad?

Not necessarily. The SSD may be physically detected while the EFI boot entry or boot files are missing or corrupted.

Q6. Should I reinstall Windows?

Not initially. First check disk detection, Windows Boot Manager, UEFI settings, EFI partition, and BCD configuration.

Q7. Will Startup Repair delete my files?

Startup Repair is intended to repair startup-related problems rather than erase personal data. Nevertheless, maintaining a backup before significant repair work is strongly recommended.

Q8. Can a SATA cable cause the PC to enter BIOS?

Yes. A damaged or loose SATA data cable can make the disk intermittently disappear during startup.

Q9. Can a faulty power supply cause this problem?

Yes. Unstable power to the SSD/HDD can prevent the drive from initializing during POST.

Q10. Should I load BIOS Optimized Defaults?

Not as the first troubleshooting step. Defaults can change boot mode, SATA mode, CSM, Secure Boot, and other settings required by the existing Windows installation.

Q11. Can a failing SSD still boot Windows sometimes?

Yes. Intermittent SSD problems can allow successful boots on some attempts and fail on others.

Q12. What does it mean if the SSD is completely missing from BIOS?

This generally points toward the SSD/HDD, cable, power connection, interface, SATA/NVMe port, PSU, or motherboard rather than the Windows bootloader.

Q13. What if Windows Boot Manager exists but Windows still doesn't start?

Then investigate boot configuration, EFI/BCD corruption, Windows startup problems, disk errors, or storage hardware instability.

Q14. Can changing UEFI to Legacy fix it?

Only when the Windows installation actually requires Legacy mode. Changing it without verifying the disk/installation type can make the machine unbootable.

Q15. What is the EFI System Partition?

It is a small partition used by UEFI systems to store boot files required to start operating systems such as Windows.

Q16. Can the EFI partition be repaired without reinstalling Windows?

Often, yes. Windows Recovery tools and bcdboot can recreate boot files when the Windows installation and disk are otherwise healthy.

Q17. Why can Windows be on one SSD but its boot files be on another disk?

During Windows installation, Setup may use an existing EFI/System partition on another connected disk. Removing that disk later can prevent Windows from booting.

Q18. Should I update BIOS immediately?

No. Diagnose storage detection, boot configuration, cables, and drive health first. Update BIOS when there is a valid reason and a suitable firmware update from the motherboard/system manufacturer.

Q19. What should I do immediately when Windows finally starts?

Back up important data, then check drive health and investigate the cause before the next failure.

Q20. Two PCs have started entering BIOS. Could both SSDs be failing?

Possible, particularly if they are similar models and age, but also investigate shared factors such as BIOS settings, recent maintenance, disk cloning, UPS/power, and common hardware.

#BIOS #UEFI #Windows #Windows11 #Windows10 #WindowsBoot #BootProblem #BIOSError #BIOSLoop #WindowsBootManager #BootManager #BootRepair #StartupRepair #WindowsRecovery #WinRE #SSD #HDD #NVMe #M2SSD #SSDRepair #HardDrive #DiskHealth #SMART #BootDrive #BootDevice #BootOrder #BootPriority #EFI #EFIPartition #BCD #BCDRepair #BCDBoot #UEFIBoot #LegacyBoot #CSM #GPT #MBR #SecureBoot #AHCI #SATA #SATACable #CMOS #CMOSBattery #CR2032 #Motherboard #ComputerRepair #PCTroubleshooting #WindowsTroubleshooting #ITSupport #TechnicalSupport