Is the SSD visible in BIOS/UEFI or not?
That determines whether you should troubleshoot Windows boot files or stop and protect the data. I’d also add Point-in-Time Restore as a 2026 recovery option, but only after the files are protected because Microsoft warns it can roll local files back along with Windows.
“No Bootable Device” — Recovering Windows Without Losing Your Files
You switch on your Windows 11 PC and instead of the sign-in screen you see:
No bootable device
Boot device not found
Operating system not found
Default boot device missing or boot failed
Windows Boot Manager not found
It can look as though Windows—and all your files—have disappeared.
Fortunately, that is not necessarily what has happened.
A No bootable device message means the computer’s firmware cannot find a valid route into Windows. Your documents may still be completely intact on the SSD; the problem may simply be that the PC cannot locate or start the Windows boot files. Your existing article already makes this distinction correctly.
The most important rule is:
Do not format, initialise, reset or reinstall Windows until you know whether the files are safe.
A boot problem can often be repaired. Overwriting the disk can turn a recoverable situation into genuine data loss.
First Question: Can the Computer See the SSD?
This is the most important diagnostic step.
Enter the computer’s BIOS or UEFI settings. The exact key varies by manufacturer, but commonly includes:
F2, F10, F12, Delete or Esc
Look under sections such as:
Storage
NVMe
Drives
System Information
Boot
Diagnostics
You are looking for the internal SSD or hard drive.
If the drive is detected
That is encouraging.
The fault may involve:
Windows Boot Manager
boot order
UEFI settings
damaged boot files
the EFI System Partition
a recent firmware change
Your data may still be intact.
If the drive is not detected
Stop trying Windows repair commands.
Startup Repair, BCDBoot, SFC and CHKDSK cannot repair a storage device the firmware cannot see. Your current article correctly identifies this as the point where the priority changes from repairing Windows to protecting the data and assessing the hardware.
Possible causes include a failed SSD, loose connection, storage-controller problem, motherboard fault or physical damage.
If the data matters, avoid repeatedly power-cycling a drive that appears and disappears. Intermittent detection is a warning sign, not an invitation to keep rebooting until it works.
Before Going Further: Disconnect External Devices
Turn the PC off and remove unnecessary:
USB drives
external SSDs
memory cards
docks
card readers
phones
bootable USB media
Leave only power, keyboard, mouse and one monitor where required.
Then restart.
A computer can occasionally attempt to boot from removable media rather than the internal Windows drive.
If Windows starts normally afterwards, review the firmware boot order and identify which device caused the problem.
Check Windows Boot Manager
If the SSD appears in UEFI, open the Boot section.
On a normal modern Windows 11 installation you would usually expect to see:
Windows Boot Manager
That should normally be ahead of:
USB storage
PXE/network boot
removable media
other non-Windows drives
Microsoft’s own Surface troubleshooting similarly advises verifying that a valid boot device and Windows Boot Manager are enabled when Windows reports that it cannot find a bootable operating system.
If Windows Boot Manager exists but is simply below another device, correct the boot order and restart.
If the SSD is present but Windows Boot Manager is missing, the boot files may need repairing.
Do not format the SSD.
Make Sure the PC Is Still Using UEFI
Modern Windows 11 installations normally use:
UEFI + GPT + EFI System Partition + Secure Boot
If firmware settings have recently been reset or changed, the computer may have been switched into:
Legacy BIOS
or:
CSM
A Windows installation configured for UEFI may then appear unbootable.
For a normal Windows 11 PC, UEFI is generally the correct mode.
But do not repeatedly switch settings to see what happens.
Record the original configuration first.
Do Not Randomly Change RAID, RST, VMD or AHCI
This is another important warning from the existing article that I would retain.
Modern PCs may use storage-controller settings such as:
Intel RST
Intel VMD
RAID
RAID On
AHCI
Windows may have been installed with drivers expecting that exact mode.
Changing it can produce:
No bootable device
or:
INACCESSIBLE_BOOT_DEVICE
even though the SSD itself is perfectly healthy.
If the problem started after:
BIOS update
loading firmware defaults
CMOS reset
motherboard replacement
check whether the storage-controller configuration changed.
Do not assume “AHCI is better” or “RAID should be disabled.”
Restore the known original setting rather than experimenting.
Get Your BitLocker Recovery Key Before Advanced Repairs
Modern Windows 11 computers frequently use BitLocker or Device Encryption.
A completely healthy Windows partition can appear inaccessible from recovery tools simply because it is encrypted.
Microsoft’s BitLocker recovery key is a 48-digit number used to regain access when Windows cannot automatically unlock the drive.
For a personal device, the key may be stored with the Microsoft account originally used to configure it.
For a business device, it may be stored in:
Microsoft Entra ID
Active Directory
the organisation’s IT records
another managed key repository
Microsoft confirms that WinRE can require the BitLocker key before accessing recovery tools or protected drives.
Do not clear the TPM simply because you cannot find the key.
That does not decrypt the data.
Enter Windows Recovery Environment
If Windows begins loading but then fails repeatedly, it may automatically enter Windows Recovery Environment (WinRE).
If the internal recovery environment is unavailable, create official Windows 11 installation media on another PC.
Boot from it and choose:
Repair your computer
not:
Install now
Microsoft confirms that Windows installation media can be used to access recovery options when a PC will not start.
From WinRE, start with the least destructive repair.
Run Startup Repair First
Choose:
Troubleshoot > Advanced options > Startup Repair
Microsoft describes Startup Repair as a tool for diagnosing and repairing startup problems that prevent Windows from loading.
Let it complete.
If Windows starts afterwards, check:
Windows Update
firmware
storage health
recent changes
so you understand why the failure occurred.
If Startup Repair says it cannot repair the computer, that does not mean your files are lost.
It only means the automated repair could not fix the boot problem.
Confirm the Windows Partition Still Exists
From:
Troubleshoot > Advanced options > Command Prompt
run:
diskpart
Then:
list disk
and:
list volume
You are looking for two important volumes.
Windows volume
Usually:
NTFS
large
contains Windows, Users and Program Files
EFI System Partition
Usually:
FAT32
relatively small
no ordinary drive letter
Drive letters can change in WinRE.
Your normal Windows C: drive may appear as D: or something else.
Test carefully:
dir C:\Windows
then, if required:
dir D:\Windows
or:
dir E:\Windows
The correct Windows volume should contain folders such as:
Windows
Users
Program Files
Do not format unfamiliar partitions merely because the drive letters look different.
Check BitLocker Status
Run:
manage-bde -status
If the Windows volume is locked, unlock it with the genuine recovery key before proceeding.
Once unlocked, confirm that you can see the user data.
For example:
dir D:\Users
If your user folders are visible, that is a very positive sign.
At this point, if the data is important and no reliable backup exists, I would strongly consider copying it before performing deeper repairs.
Protect the Files Before You Get Clever
This is arguably the most important practical step.
Once the Windows partition is readable, copy important files to another storage device before:
modifying partitions
running repairs
resetting Windows
reinstalling
changing firmware settings
replacing the drive
Your existing article rightly puts file protection ahead of more invasive recovery.
Important locations can include:
Desktop
Documents
Pictures
project folders
accounting data
local databases
local email archives
virtual machines
files stored outside the normal user profile
Be aware that OneDrive Files On-Demand entries can be online-only. Seeing a filename in a recovered OneDrive folder does not guarantee the full content exists on the local SSD.
Recreate Windows Boot Files With BCDBoot
If:
the SSD is healthy
Windows is visible
BitLocker is unlocked
your important data is protected
the EFI System Partition has been positively identified
then rebuilding the UEFI boot files can be appropriate.
On a modern UEFI Windows 11 installation, BCDBoot is often more relevant than copying old bootrec instructions from guides written for BIOS/MBR systems.
Your current article already explains this distinction particularly well.
After assigning a temporary drive letter to the correct EFI System Partition, a command may look like:
bcdboot D:\Windows /s S: /f UEFI
where:
D: is the confirmed Windows installation
and:
S: is the confirmed EFI System Partition.
A successful command should recreate the Windows boot files.
Restart and check whether Windows Boot Manager has returned.
Do not guess the partitions
This command should only be used after positively identifying:
the Windows installation
EFI partition
firmware mode
Do not format the EFI partition merely because BCDBoot fails.
Find out why it failed first.
What About BOOTREC?
Older recovery guides often begin with:
bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd
Those commands still have uses.
But they are frequently presented without distinguishing between:
BIOS/MBR
and:
UEFI/GPT
systems.
A normal modern Windows 11 computer is likely to use UEFI.
bootrec /fixmbr does not recreate missing UEFI boot files, while bootrec /fixboot can return Access Denied in some UEFI configurations.
Don't blindly follow a ten-year-old boot repair sequence on a modern Windows 11 PC.
Be Careful With CHKDSK
If the drive appears healthy and the important files are already safe, a file-system check may be appropriate.
For example:
chkdsk D:
A repair can be requested with:
chkdsk D: /f
But avoid immediately running intensive surface scans on a potentially failing drive.
Your current article correctly warns that chkdsk /r can place a deteriorating disk under prolonged stress.
If the SSD:
disappears intermittently
disconnects during copying
produces increasing read errors
fails diagnostics
stop trying to “repair” it.
Data recovery or cloning becomes the priority.
If the Problem Started After an Update
If Windows Boot Manager works and Windows begins loading before failure, WinRE also provides:
Troubleshoot > Advanced options > Uninstall Updates
You may be able to remove the latest quality or feature update.
This is useful for a Windows startup failure.
It will not fix an SSD that the firmware cannot detect.
That distinction matters.
What About System Restore?
WinRE also provides:
Troubleshoot > Advanced options > System Restore
Microsoft confirms System Restore can return system files and settings to an earlier restore point.
System Restore is more relevant when a driver, application or Windows configuration change has broken startup.
It is not a substitute for backing up your personal files.
New for 2026: Point-in-Time Restore
Newer Windows 11 systems may also offer Point-in-Time Restore.
Microsoft made this feature generally available in 2026.
It can restore:
Windows
applications
settings
local files
to a recent automatic restore point.
That makes it more powerful than traditional System Restore.
It also makes it potentially more destructive to recent local work.
If you select a restore point from yesterday, local files created or changed since that point can also be rolled back.
For an article specifically about recovering without losing your files, my recommendation is:
Protect the files first. Use Point-in-Time Restore second.
If there is unsynchronised business-critical local data, do not treat it as a harmless “Undo Windows” button.
If the SSD Is Detected Intermittently, Stop
This deserves much more prominence than it gets in most recovery guides.
If the SSD:
appears on one boot
then:
disappears on another
that is a serious warning sign.
Possible causes include:
SSD controller failure
NAND failure
thermal problems
power problems
loose connection
motherboard-slot failure
Don't use the moment when it happens to reappear to run:
a feature update
a full CHKDSK
repeated diagnostics
Windows Reset
Use the opportunity to protect the data.
When to Stop DIY Troubleshooting
Stop ordinary repair attempts if:
the drive is not detected in UEFI
manufacturer diagnostics report failure
the SSD repeatedly disconnects
copying produces increasing read errors
the drive reports the wrong capacity
a mechanical hard disk clicks or grinds
important data has no backup
you cannot confidently identify the Windows and EFI partitions
BitLocker is enabled and you cannot obtain the recovery key
Every extra operation on physically failing storage can reduce the chances of successful recovery.
Do Not Reset or Reinstall Windows Too Early
Resetting or reinstalling Windows can be appropriate after the data is safe and when repairing the existing installation no longer makes sense.
Microsoft provides Reset this PC through WinRE, but it may require a BitLocker recovery key and can remove applications, settings or—in some modes—personal files.
A clean installation is more destructive again.
Microsoft explicitly warns that reinstalling Windows using installation media can remove files, apps and settings depending on the chosen method.
So the order should be:
Diagnose → protect the files → repair → reset/reinstall only when necessary.
Not:
No bootable device → reinstall Windows.
The Safe Recovery Order
For most Windows 11 “No bootable device” problems, use this sequence:
1. Disconnect external storage.
2. Restart once.
3. Check whether the SSD appears in UEFI.
4. If it doesn't appear, stop Windows repair attempts.
5. Run manufacturer hardware diagnostics.
6. Check Windows Boot Manager and boot order.
7. Verify UEFI mode.
8. Check for unintended RST/VMD/RAID/AHCI changes.
9. Find the BitLocker recovery key.
10. Enter WinRE.
11. Run Startup Repair.
12. Confirm Windows and EFI partitions.
13. Unlock BitLocker if required.
14. Back up important files.
15. Recreate boot files with BCDBoot where appropriate.
16. Use update rollback/System Restore when the evidence points there.
17. Consider Point-in-Time Restore only after understanding its effect on local files.
18. Reset or reinstall only after recovery options have been exhausted.
That order protects the most valuable thing first:
your data.
How Hamilton Group Can Help
A “No bootable device” message can be a simple boot-order problem—or the first warning that an SSD is failing.
The difficult part is knowing which one you are dealing with before making changes that affect the data.
Hamilton Group can help with:
Windows 11 boot problems
Windows Recovery Environment
BitLocker recovery
Startup Repair
SSD diagnostics
Windows Boot Manager
UEFI and firmware configuration
data recovery assessment
Windows reinstallations
backup and disaster recovery
business device support
If your computer contains important business data and the drive is disappearing, failing diagnostics or producing read errors, stop experimenting before the fault becomes worse.
Visit hgmssp.com or call 0330 043 0069 to speak with Hamilton Group.