UEFI post-deployment issues on a Latitude 5289

Hi all -- just beginning to explore the possibilities of UEFI deployments.  For now, deploying via UEFI USB drive, until my university network people can make the proper DHCP scope changes to allow for PXE UEFI booting.

I have successfully performed a few UEFI boots, using task suggestions I found here on ITNinja.  I have a pre-installation DISKPART script, and a mid-level bcdboot task that I'll paste below.  This deployment (using an existing .WIM Windows 10 image) has worked perfectly on a few new Latitude 7480s as well as a Latitude 7280.  But on a Latitude 5289 (Dell's new convertible 2-in-1) I get a "no boot device" found error after deployment.

I have the 5289 in my Driver Feed, and rebuilt the KBE with those drivers included (as well as the 7280 and 7480 drivers).  I can see the proper drivers pulled over during the deployment sequence.  The Windows files are there -- if I open a command prompt, I can browse C: all day long -- so I don't think it's a storage driver issue.  I think it's something with my DISKPART or bcdboot tasks, but I can't figure out what, and I can't figure out why the 5289 behaves different from other hardware.  (This is the only 5289 I have right now, so it's a population of 1 for testing.)

Here are my scripts.  Would appreciate any suggestions!

Create UEFI Partition (pre-installation task)
select disk 0
convert GPT
create partition efi size=499
select partition 1
format fs=fat32 quick label=system
assign letter=h
create partition MSR size=128
create partition  primary size=235125
select partition 3
format fs=ntfs quick label=windows
assign letter=c
create partition primary
select partition 4
format fs=ntfs quick label=recovery

UEFI Set Partition (mid-level task)
@echo on
bcdboot c:\windows /s h: /f UEFI

1 Comment   [ + ] Show comment
  • Was the image from a fresh install, usually on UEFI images you would only capture C and S partitions. Since there is another its possible there is a 'ghost' driver in the capture if captured from another physical system and not a fresh install. - TheAustinDave 4 years ago
    • This is a .WIM originally captured from a Legacy boot machine. I used some instructions found here (http://www.itninja.com/question/uefi-k2000-use-existing-wim-image) to use this .WIM for UEFI boots as well.

      I talked with KACE support yesterday; this "hybrid WIM" approach is not officially supported. However, it works just fine on my 7280s and 7480s. We'll have one foot in both worlds for a while, so it would be really nice to be able to use the same WIM for both infrastructures. - erzeszut 4 years ago

Answers (3)

Posted by: mikedouglas 4 years ago
Senior White Belt

I recommend the BIOS be updated on all the laptops before attempting this.

Also, there maybe a slight variation in wording or options in the BIOS that can cause this.

The other thing I have noticed that can cause this exact error is when you are testing on a computer you already tested on and so there maybe 2 or more Windows Boot Managers.

Ensure all Windows boot Managers and partitions are erased before attempting again.

Posted by: rdroste@obdnoordwest.nl 4 years ago
Senior White Belt
Try to the do the following :

Bios Restore Settings
Factory Settings
Change Bios Mode
Legacy Secure OFF
Select your nic and start the deployment 

we had this issue for our 13-2-1 also. 
Posted by: sfrank42 3 years ago
Senior White Belt
I had a similar issue and changing from RAID to AHCI fixed, this would only apply if you got the model with the M.2 SATA drive
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ