Hi just bought a 17r se,mine refused to switch off,that did seem to be ok on the second attempt,but now it has the same prob with second attempt boot,i have just followed the procedure involving changing to dvd/cd first in the sequence,so far so good.

As some of you guys have said it seems that dell techs did not know about the prob,maybe because it was so new,hopefully everyone with the prob can use this fix.Methinks most dell owners need to be techs too.

Hello

I have founded this on the internet, it's for Vostro, but it's a problem to boot with UEFI, when we don't have access to Windows and don't have the "Windows Boot" in the Bios, only the "Network Boot":

He didn't do anything and one day his computer had lost the way to boot,

www.frenchytech.com/.../dell-pc-wont-start-boot-windows-8-uefi-problem

"1-Entrer dans le bios (F2 sur le Dell)

2-Onglet BOOT, allez sur la section UEFI :

3-ADD BOOT OPTION :

4-tapez HDD en nom, en fait on s’en fout, puis TAB

5-Choisir la ligne PCI….numéro 1, si vous vous déplacez avec les flèches vous verrez en bout GPT et partoche 1, TAB puis Filename

6-Là , on dit merci Jean-Marc, et on tape exactement EFI\Microsoft\Boot\Bootmgfw.efi (si le clavier est en anglais \=* et m=?)

Voilou et ça rebooooooote."

I don't take responsability for this answer, because I don't have tested this one and I'm not enough qualified to play with my Bios.

Cheers

To ALLan Dell,

I have a similiar problem on my Inspiron 7720, but it just has a blank(black screen) in the F12 BOOT OPTIONS, with an empty progress bar in the middle. It DOES NOT give me the option to run ANY DIAGNOSTIC, and the progress bar stays empty forever, (I waited for 4.5 hrs).

What do u guys suggest?

Thanks in advance for yur time.

I am having the same issue with my daughtes computer.  I tried this and it did not work.  Any other suggestions.  I stil lhave a blue screen

when i try to add boot option it shows "Warning file system not found?"

so i can't try this method at all

by the way my computer doesn't boot no matter what no second time booting for this 7720 and i also have the A10 bios

PLEASE HELP

I have a 17R SE experiencing the same problems.  A 7720 running bios A11.

I’ve looked around on a few other posts and this one got me thinking (en.community.dell.com/.../19487317.aspx , specifically the post from Temiscouta on 24 Jan 2013 at 8:33am).  So, through it I’ve worked out a solution for my problem.  Maybe it’ll help you all?  [Without having to send the machine back to Dell]

I think basically what has happened is that somehow the system has lost understanding of how it is to boot…

So.  Boot the machine and go into the BIOS – (press F2 at power on).  In the BIOS screen go to the BOOT option and review the settings.  There should be a list of Legacy boot options (in priority) and UEFI boot options, again in priority.  There will be a “Boot List Option” which selects which boot type your computer is using.  Legacy or UEFI.  If this is set to UEFI, then you need to look at what is in that part of the list.  

In my case, the only option I had in UEFI was “Network Boot”.  This post (en.community.dell.com/.../19487317.aspx ) got me thinking that I would need a “Windows Boot Manager” option.  So I went to “Add a Boot Option”.  In this, you should have a new window with a list…

“Boot Option Name”

“File System List”

“File Name”

In my case – the Boot Option Name and File Name sections were empty, but the File System List had two entries…

Something like…  

“PciRoot(0x0)/Pci(0……”  

(Besides this should be different from machine to machine as it should be a reference to the hardware; physical disk and a particular part/sector/file of that disk).  So, I entered into the Boot Option Name field, “Windows Boot Manager”, tabbed to “File System List” field and highlighted the first of the two entries.  Then tabbed over the “File Name” field to the “Yes” selection and hit enter.

This put a “Windows Boot Manager” into the UEFI boot list.  I moved that entry to the top of the list (+ or – keys promote/demote entries).  Save and Exit, and my system booted first time.  And has continued to boot first time every time since.  Around seven re-boots now.

Maybe this will be a fix for you too…  I also wonder what shifting the boot option to “Legacy” might do?  Maybe that could help.  But as my systems working fine now – I’m not too bothered.  

I have tried DRRLN's solution, but I do not have Network Boot under the UFEI boot list, the only thing it has is windows boot manager when I add it.

I also don't understand what to do in the "File System List" field, when you highlight the first of the two entries.

You don't need the network boot option to boot the machine.  If it's not there then it's not a problem. 

The File System List field should already be populated and then you don't need to do anything except make sure that you have "Windows Boot Manager" as an option, and the boot mode set to UEFI.  In the case of my problem, I did not have Windows Boot Manager as an option in the UEFI boot list.  So I went to "Add a Boot Option", followed the steps in the post, and in the window containing the "File System List" field, all I did was give that "Boot Option Name" a name: "Windows Boot Manager", and saved that.  As below, the File System List entry was already populated.  I did not change it - or put anything in it.   

For the UEFI system to boot the File System List needs to point to the drive(s) and sectors which contain the UEFI equivalent of the master boot record for previous versions of windows.  For operating systems using UEFI (Unified Extensible Firmware Interface), like Windows 8, what the system needs to find is the GPT (GUID Partition Table - GUID being Globally Unique IDentifier).  On my system, the File System List has two entries - and these are already populated...  The content looks like:

[PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0,0x0)/HD(1,GPT,903AECA3-11EC-5C21-BF80-9EF891F601D9,0x800,0xFA000)]

[PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0,0x0)/HD(2,GPT,E5321371-A8FD-1C2D-64ED-602A313B1215,0xFA800,014000)]

Most of this is unique to each individual machine (especially the parts after GPT...).  So - do NOT use what I've put here on your system - It is absolutely guaranteed NOT to work!!!  What you might want to do is take a note of what you have in these fields on your system - it may help you or help Dell help you. 

If this information is not already in the File System List - then I have no idea how you populate it - as it really needs to be done when the system is created/windows is installed.  If you have created system restore disks, then you may be able to recover from that - or it is a case of getting onto Dell technical support to help.  I'd probably contact Dell technical support first before trying an install - as they (and you) really need to understand how the system lost this information.  It might require you to send the system back to them.  If that's the case (and you have system restore disks) - you might want to suggest to them that you try a system restore first.  That is, if you really don't want to send the system back. 

I hope this helps and you get your system running. 

So "Load Legacy Option Rom": enabled, and "Boot List Option": Legacy as well?

And after that, I should try the steps included with the USB drive?

Also, just as an FYI, I only have one HDD, no mSATA, Windows 8, and BIOS A07 version.

I can only seem to find one option in the File System List, and it is

"PciRoot(0x0)/Pci(0x1D, 0x0)/USB(0x0)/USB(0x1,0x0)/Unit(0x0)/HD(1,GPT,E8AC336C-D14C-4CA2-8154-5A790A5DF7EA,0x800,0x5B4800)"

I tried doing what you suggested, but for some reason, I think I can only access "Add Boot Option" when I connect the USB Windows 8 Recovery drive that Dell sent me. Your method didn't work for me...

Should I run it in secure boot enabled or disabled?

I have a few more details here: en.community.dell.com/.../19505799.aspx

If you're booting the recovery flash drive, be sure you do so in legacy mode -- NOT UEFI mode.

Legacy boot list option (and F12 at powerup) will allow the USB drive to boot the system and kick off the recovery process.

I'm having the same problem still, is there a solution to this now?