Unsolved

This post is more than 5 years old

1 Rookie

 • 

8 Posts

13890

November 1st, 2017 12:00

XPS 13 will only boot with F12

My computer won't boot normally. It's a Dell XPS 13 with Windows 10 installed, updated today.

If I set Legacy it says "no device found". With UEFI it gets stuck in a trying to repair, can't repair, restart cycle. It won't start either if it's in UEFI and I press f12.

The only thing that works is having it in Legacy, press f12, then under UEFI Boot select "UEFI [...] Samsung 256GB, Partition 2"

I've tried updating the BIOS, restoring factory and BIOS presets, changing the order so it boots the "UEFI [...] Samsung 256GB", repairing BIOS (esc+ctrl), running f12 diagnosis (no problems detected) and a couple other things.

I actually can boot so it's mostly just annoying, but how can I solve this?

6 Operator

 • 

4.3K Posts

 • 

15.9K Points

November 2nd, 2017 11:00

Identificador           {current}

device                  partition=C:

path                    \Windows\system32\winload.efi

The BCD Store does look fairly normal.  It is missing recovery options but that may be due to the problem.  It does have one entry I am not used to which is bootstatuspolicy  DisplayAllFailures but that may have been added during a repair operation.

Since you have not seen a message as to why the system is having a problem, the problem could be what comes after the OS loader completes and sends it to the C partition.

Were you running your NVMe drive as the OEM install or had it been modified to use the PCIe configuration?  I have a PCIe version which shows exactly as your drive details but that may just be specifics on the drive and not the controller.  I have a real M.2 SATA drive on my 9365 which shows as RAID.

If you have altered the SATA options in the Bios, you might change it back or at least check how it is currently configured.

Otherwise, I don't see anything obvious causing the problem...   I am sure you have already checked for the Windows Boot Manager to be the primary boot device in the Bios so you might try disabling Secure Boot but leave the UEFI option enabled.

No Events found!

Top