This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Problem Description
Initial values and settings of my Dell laptop
My Dell Vostro 3559 laptop was purchased one year and a half ago coming with its service tag FHY0GC2. Under the Firmware Settings, the boot mode was set to UEFI with all Legacy Option ROMs disabled, and the secure boot was set to Disabled. However, there was no change made to any information stored inside the PTT (Platform Trust Technology, i.e. a Trusted Platform Module implemented by Intel): the PTT was turned on and visible to Operating Systems, whose owner information had never been cleared.
I have made the following changes to my Dell laptop
Did a clean install of Windows 10 Team build 15063 on an empty GPT disk, which is the firmware provisioned for Surface Hub only but was used for my laptop for testing purposes.
UEFI boot issues with Windows 10 Build 14393 or 14393+ firmware bootloaders that these changes resulted in
After install, the UEFI firmware bootloader of Windows 10 Team was able to boot normally. However, it was found that whatever bootable Windows 10 or Windows 10 PE (greater than or equal to Build 14393) (UPDATED February 14, 7:50 AM UTC) systems or media (usually within a USB stick or a portable disk) unable to boot from the UEFI on my laptop. Fortunatelly, I have been still able to get Windows 8.1, Windows 10 Build 10586 (UPDATED February 14, 6:40 AM UTC), Linux or Hackintosh (Clover) systems and media booting from the UEFI on my laptop since the last change was made. I tried the following 5 scenarios but none of them helped. Please help me to get any Windows 10 or Windows 10 PE media Build 14393 or 14393+ booting from the UEFI on my laptop, thanks.
Scenarios that I tried
I have tried each version (in 1.2.1 - 1.2.8) of valid BIOS ROM files from the Dell Support official server downloads.dell.comto process the BIOS recoverybut every time it didn't help.
3. Clear the PTT owner information while the PTT was turned on under the Firmware Settings.
4. I also tried clearing all credentials inside the TPM while the PTT was on under the Firmware Settings by selecting Clear TPMin tpm.msc, restarting my latop and pressing a key when prompted. (UPDATED February 14, 6:40 AM UTC)
5. I also tried clearing the TPM while the PTT was on under the Firmware Settings by doing a factory reset (i.e. recycling this PC) on Windows 10 Build 15086 booting from the UEFI, pressing F12 to clear the TPM when prompted before the Second Boot. (UPDATED February 14, 6:40 AM UTC)
Bootability Test that I did
Dell Vostro 3559 Laptop, Windows Setup Media Bootability Test Result
| <PTT State, Boot Mode> | PTT ON | PTT OFF | ||
|---|---|---|---|---|
| Windows Setup Media | BIOS | UEFI | BIOS | UEFI |
| ⅰ) Windows 10 Team Build 15063.97 Setup (MBR Partition Scheme for BIOS Target System Type) | MEMORY MANAGEMENT ERROR | N/A | Successful | N/A |
| ⅱ) Windows 10 Enterprise Build 16299.15 Setup (MBR Partition Scheme for Dual Boot) | MEMORY MANAGEMENT ERROR | Failed | Successful | Failed |
| ⅲ) Windows 8.1 Enterprise Build 9600.17031 Setup (MBR Partition Scheme for Dual Boot) | A spinning circle in death loop | Successful | Successful | Successful |
| ⅳ) Windows 10 Team Build 15063.97 Setup (GPT Partition Scheme for UEFI Target System Type) | Selected boot device failed | [FAIL] Start failure: [17] No Mapping; Failed | Selected boot device failed | [FAIL] Start failure: [17] No Mapping; Failed |
| ⅴ) Windows 10 Home China Build 15086.0 Setup (MBR Partition Scheme for Dual Boot)<br>(UPDATED February 14, 6:40 AM UTC) | MEMORY MANAGEMENT ERROR | Successful | Successful | Successful |
| ⅵ) Windows 10 Team Build 14393.0 Setup (GPT Partition Scheme for UEFI Target System Type)<br>(UPDATED February 14, 8:00 AM UTC) | Selected boot device failed | [FAIL] Start failure: [17] No Mapping; Failed | Selected boot device failed | [FAIL] Start failure: [17] No Mapping; Failed |
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Thank you for the information. It appears that you'll need more advancde assistance regarding your query. We highly recommend posting your query to Microsoft TechNet Windows 10 IT Pro discussions. IT professionals specialize in Windows 10 will be able to address any of your concerns there.
In case that you have further inquiries, feel free to post here in our community.
I NEVER tried dual boot, keeping only ONE Firmware Bootloader with only ONE boot entry on my laptop, which could be one of the items below.
... but failed to let bootable Windows 10 or Windows 10 PE media boot from the UEFI on my laptop? Can you help identify the issues, please?
Frankly speaking, Firmware Bootloadersare independent with each other, which was proved by a group of experiments that I did, where all the three bootloaders were able to boot from the UEFI in whichever sequence they had been installed:
Had your statement highlighted above proved to be TRUE?
If you install multiple Windows Operating Systems (Windows 7, Windows 8.1 or Windows 10) on to a disk configured with the same UEFI boot file (usually located at "$($ESPPartitionDriveLetter):\efi\Microsoft\Boot\BCD"), then these boot entries will share the same Firmware Bootloader, which you can learn by typing in "bcdedit.exe /Enum All" and press Enter in an elevated Command Prompt.
If you add multiple boot entries to the same EMPTY bootloader in an ascending order by version number (MajorVersion.MinorVersion.BuildNumber.BuildRevision) (i.e. from the lower version to the higher version), then all boot entries will definitely work, the exact contrary to what you said. However, if you install Windows 10 before installing other versions of Windows, in most cases, the lower versions of Windows will boot but might encounter any issues such as the mouse pointer not working, because this time the Windows Boot Loader has been updated by the lower versions of Windows, which will never be compatible with Windows 10 boot entries, more briefly, Backwards Compatibility.
If you are dual booting with Windows 10 and the other operating systems are installed before Windows 10 is installed, Windows will not boot. Dual booting with Windows 10 requires Windows 10 to be installed first. Try removing your other operating systems, then install Windows 10. After doing so, configure dual boot on your device. This would definitely work.
Do reach us out if you need further assistance.
Hi Allan,
I have been keeping using the correct Firmware Settings to make my firmware bootloaders boot from the UEFI on my laptop, where Boot List Option has been keeping UEFI and Enable Legacy Option ROMs has been keeping unchecked under Advanced Boot Options, for which Windows 8.1, Linux or Hackintosh (Clover) media have been still bootable from the UEFI since the last change was made.
As you see from the Bootability Test Result Table, Windows 10 was dramatically an EXCEPTION upon booting from the UEFI on my laptop even if I used official Windows 10 media created on my own following the instructions at this page. See the table cells highlighted below.
I also tried clearing all credentials inside the TPM by selecting Clear TPMin tpm.msc, restarting my latop and pressing a key when prompted. However, it was impossible clearing the TPM by doing a factory reset, cleaning the drive, pressing a key to process the clear when prompted, since Windows 10 was unable to boot from the UEFI.
You just need to help analyze the phenomena please ----
why were bootable Windows 10 or Windows 10 PE media unable to boot from the UEFI on my laptop, while other OS (such as Windows 8.1, Linux or Hackintosh (Clover)) media still booted successfully from the UEFI on my laptop?
Any ideas will be appreciated.
Hi Zefa,
You might have used a wrong configuration on your PC. If you've chosen UEFI upon installing Windows, you need to switch firmware modes. For further guidance regarding booting to UEFI Mode or legacy BIOS mode, kindly refer to this link. Also, we recommend creating your own installation media in installing Windows 10. You can create your own installation media by referring to this link. When prompt for the product key, simply click I don't have a product key.
Should you have more concerns, feel free to post.
Regards.
If you think this was useful, you may "mark it as an answer" to help those who are facing the same problem.
