Surface Pro 6 – Bootable Operating System Not Found

Shivam Prajapati 0 Reputation points
2026-09-10T18:42:49.01+00:00

Dear Microsoft Support Team,

I am facing a boot issue with a Microsoft Surface Pro 6.

The device is showing the following error:

“Couldn't find a bootable operating system.”

I have performed some non-destructive checks:

  • Windows Boot Manager and Internal Storage are visible in Surface UEFI.
  • Windows Recovery USB boots successfully.
  • However, in Windows Recovery Command Prompt, DiskPart does not detect the internal SSD.
  • WMIC also detects only the USB flash drive, not the internal SSD.
  • No formatting, partition deletion, clean, reset, or Windows reinstallation has been performed.

The device contains important official data, so data preservation is extremely important.

Please advise on the non-destructive diagnostic and recovery procedure. We do not want to reset, format, reinstall Windows, or modify/delete any existing partitions without confirming the impact on the data.

Kindly let us know the next recommended steps and whether the device requires hardware-level diagnosis.

Regards, Shivamimage

WhatsApp Image 2026-09-09 at 5.10.37 PM

Windows for home | Windows 11 | Performance and system failures

1 answer

Sort by: Most helpful
  1. AI answer

    2026-09-10T18:43:16.38+00:00

    The current findings point to storage-level failure or loss of SSD visibility rather than a normal boot configuration issue.

    Given these facts:

    • Windows Boot Manager and Internal Storage appear in Surface UEFI
    • the USB recovery drive boots successfully
    • DiskPart and WMIC in Windows Recovery do not detect the internal SSD
    • no reset, reinstall, formatting, or partition deletion has been performed

    The next recommended non-destructive path is:

    1. Re-check Surface UEFI boot configuration
      • In Surface UEFI, open Boot configuration.
      • Confirm that valid boot options are enabled. Microsoft states that Windows Boot Manager, Internal Storage, USB Storage, and PXE Network should be selected by default.
      • This confirms the device is not blocked by a disabled boot entry.
    2. Perform a forced restart
      • Press and hold the power button until Surface restarts and the Windows logo appears, which can take about 20 seconds.
      • This is a non-destructive step and is the recommended restart method for this condition.
    3. Use the Surface recovery USB only for startup diagnostics, not reset
      • Since the recovery USB already boots, that confirms the device can start external recovery media.
      • Do not choose reset or recovery actions if data preservation is required.
    4. If USB recovery media ever stops booting, verify USB boot prerequisites
      • Ensure boot-from-USB is enabled in Surface BIOS/UEFI.
      • If needed, configure the boot order so USB is first.
      • Check Secure Boot configuration, because newer Surface recovery images require the 2023 Secure Boot certificate.
    5. Treat lack of SSD detection in WinRE as a hardware-diagnosis trigger
      • When recovery tools detect only the USB drive and not the internal SSD, there is no supported non-destructive software repair step in the provided guidance to rebuild Windows from that state.
      • At that point, the next recommended step is hardware-level diagnosis / service rather than reset or reinstall.
    6. Escalate to service options
      • If the documented checks do not resolve the problem, Microsoft’s next path is self-repair, send to Microsoft, or in-person support where available.
      • For a device containing important official data, avoid any action that writes to the internal drive until hardware assessment is completed.

    Based on the documented guidance and the reported SSD non-detection, hardware-level diagnosis is warranted.


    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

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.