“Operating System Not Found” appears before Windows loads. The message means the computer’s firmware could not hand startup over to a usable operating system. Your files may still be intact, so do not format, initialize, or reinstall the drive before checking what the computer can actually detect.
The safest diagnosis begins with one question: Does the SSD or hard drive appear in BIOS or UEFI? A missing drive points toward hardware, its connection, or a firmware storage setting. A detected drive points toward boot order, Windows Boot Manager, or damaged boot files.
Read this before changing BIOS settings
Avoid switching randomly between UEFI and Legacy or CSM mode. Windows 11 normally uses UEFI with a GPT-partitioned drive. Changing the firmware mode can make a healthy Windows installation appear unbootable without repairing anything.
Also avoid these common mistakes:
- Do not format the EFI System Partition.
- Do not initialize a drive because another computer calls it unallocated.
- Do not make partitions active on a modern UEFI/GPT installation.
- Do not run every
bootreccommand copied from an older BIOS/MBR guide. - Do not run a heavy disk repair on a drive that is clicking, disappearing, or reporting hardware errors before protecting the data.
Take a photo of the original error and any firmware settings before making changes. If BitLocker is enabled, locate the recovery key because Windows Recovery Environment may request it.
Remove devices that can change the boot target
Shut down the computer and disconnect nonessential storage devices:
- USB flash drives
- External SSDs and hard drives
- Memory cards
- USB docks and storage adapters
- Recently connected secondary drives
Leave the keyboard, mouse, display, and power connected, then start the PC again.
Firmware can attempt to boot from removable media before the internal Windows drive. If Windows starts after a device is removed, reconnect the devices one at a time and correct the boot priority later.
Check whether BIOS or UEFI detects the Windows drive
Enter the firmware setup during startup. The key varies by manufacturer and commonly includes F2, Delete, Esc, or F10. My guide to opening BIOS in Windows 11 includes the common access routes.
Look under a section such as Storage, System Information, NVMe Configuration, SATA Information, or Boot. Record the drive model and capacity if they appear.
The SSD or hard drive is not detected
Windows commands cannot repair a drive that the firmware cannot see. Shut down the computer and consider the hardware path:
- Run the manufacturer’s built-in storage diagnostic if it is available.
- On a desktop, check the SATA data and power connections or the seating of an NVMe drive.
- On a laptop under warranty, use the manufacturer’s support process before opening it.
- Undo only a known recent change to RAID, AHCI, Intel VMD, or another storage-controller setting.
- Check whether the drive appears intermittently or fails a diagnostic.
A drive that disappears, makes unusual mechanical sounds, or repeatedly fails diagnostics may be failing. Stop repeated boot repairs and prioritize professional data recovery when the files are important and not backed up.
HP computers that display Boot Device Not Found or error 3F0 have a more specific diagnostic path. Use the HP Boot Device Not Found guide instead of treating every manufacturer’s firmware the same.
The drive is detected
Continue with boot-order and Windows recovery checks. Drive detection does not prove the SSD is healthy, but it makes a missing boot entry or damaged startup files more plausible.
Put Windows Boot Manager first
Open the firmware’s boot-order screen. On a normal UEFI Windows installation, look for Windows Boot Manager, often followed by the SSD model.
- Move Windows Boot Manager above network boot, USB storage, and other drives.
- Save the change and restart.
- If the error started after a BIOS reset or firmware update, compare the current boot mode with the mode used by the existing Windows installation.
Do not select a similarly named empty drive simply because it appears first. Windows Boot Manager is normally the appropriate UEFI entry.
When Windows Boot Manager is missing but the SSD remains detected, the EFI boot files or firmware entry may need repair. Continue to Windows Recovery Environment rather than changing unrelated Secure Boot settings.
Use Startup Repair before manual commands
Open Windows Recovery Environment from Advanced options if the computer already offers Automatic Repair. When built-in recovery is unavailable, boot from official Windows installation media and select Repair your computer, not Install now.
Go to:
Troubleshoot > Advanced options > Startup Repair
Choose the Windows installation when prompted and allow the process to finish once. Startup Repair is designed to address several problems that prevent Windows from starting, including damaged startup configuration.
If Startup Repair reports SrtTrail.txt and returns to the recovery screen, do not keep repeating it. Follow the SrtTrail.txt Automatic Repair guide to examine the recorded cause.
Undo the change that immediately preceded the error
The timing often identifies the correct recovery tool.
After a Windows update
From Troubleshoot > Advanced options, open Uninstall Updates. Start with Uninstall latest quality update when the error appeared immediately after a monthly update. Do not remove updates randomly when the problem began earlier.
After a driver, application, or system-setting change
Choose System Restore and select a restore point created before the failure. Review the programs and drivers that will be affected. System Restore is useful only when a suitable restore point exists.
After cloning or replacing a drive
Shut down and verify that the intended destination drive is installed and selected. If both the old and cloned drives are connected, firmware may be using the wrong boot entry. Do not erase the source drive until the clone has started successfully on its own and your files have been checked.
Cloning software can copy the Windows partition without producing a usable firmware entry. When the Windows folder exists on the new drive, BCDBoot may recreate the required boot files.
Confirm that the Windows installation still exists
Use this section only when the internal drive is detected and Startup Repair did not solve the problem.
Open:
Troubleshoot > Advanced options > Command Prompt
Windows drive letters can change inside recovery. Do not assume the installation is C:. Enter:
diskpart
list volume
exitUse the volume sizes, labels, and file systems to identify likely Windows volumes. Test them without modifying anything:
dir C:\Windows
dir D:\Windows
dir E:\WindowsStop when one command displays the normal Windows directory. In the example below, assume it is D:\Windows. Replace D: with the actual letter on your computer.
If no readable Windows folder exists, do not proceed with BCDBoot. The volume may be locked by BitLocker, corrupted, missing, or no longer contain Windows.
Recreate Windows boot files with BCDBoot
BCDBoot can copy fresh boot-environment files from an existing Windows installation to the system partition and recreate a Windows Boot Manager entry. Microsoft documents it as a tool for repairing the system partition and boot menu.
Using the example Windows directory identified above, run:
bcdboot D:\WindowsA successful operation should report that the boot files were created. Close Command Prompt and restart the PC.
Microsoft’s BCDBoot documentation also stresses identifying the Windows volume before running the repair. I deliberately do not include instructions to format the EFI partition. Formatting it is rarely justified for a general reader and can remove working boot files for Windows or another operating system.
If the screen specifically shows error 0xc0000185 or says the Boot Configuration Data is missing, use the focused Windows error 0xc0000185 guide for that BCD condition.
Why the usual bootrec command block is not the first answer
Older troubleshooting guides often present all four commands together:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcdThey are not a universal solution. Modern Windows 11 computers normally use UEFI firmware and GPT partitions, while some bootrec operations originate from BIOS/MBR recovery scenarios. The correct action depends on whether the firmware sees the disk, whether a Windows installation exists, and which boot structure is damaged.
Running commands without identifying the installation can produce confusing results such as Access is denied or Total identified Windows installations: 0. BCDBoot is the more focused option when the Windows directory is readable but its boot files or firmware entry need rebuilding.
Check drive health before reinstalling Windows
Reinstallation is not a repair for failing storage. Before erasing anything, run the PC manufacturer’s SSD or hard-drive diagnostic, or have the drive checked from another trusted environment.
Treat these signs as possible hardware failure:
- The drive vanishes from BIOS intermittently.
- Diagnostics report a SMART, short-test, or long-test failure.
- Files cannot be read consistently.
- Recovery commands stop with repeated input/output errors.
- A mechanical hard drive clicks, spins down, or repeatedly retries.
Avoid repeatedly running chkdsk /r on a clearly unstable drive when recovering the files is the priority. A repair scan writes to the file system and is not a substitute for imaging or professional recovery.
Reinstall only when the drive is healthy and recovery fails
A clean Windows installation is reasonable when the storage device passes diagnostics, important files are backed up, and the Windows installation or partition is genuinely absent or beyond repair.
Boot from official installation media, confirm the correct target disk, and protect any other connected drives from accidental deletion. My Windows 11 reinstallation guide explains the difference between recovery, reset, repair installation, and a clean install.
Microsoft’s Windows recovery options compares what the supported recovery methods keep or remove. When the existing Windows installation is readable, try the least destructive method that matches the evidence before choosing a clean installation.
The repair is complete only when Windows Boot Manager remains available and the PC starts normally after more than one shutdown. Reconnect external drives individually afterward. If the error returns when one device is attached or after the drive disappears from firmware again, the underlying cause is hardware or boot selection, not missing Windows files.
