Bootable USB for UEFI installation in scripted install

I'm currently experimenting with Windows 10 and wanted to use UEFI instead of BIOS.In the forums I've seen that PXE is not supported when using UEFI.

So I created a bootable USB stick with my current image which I use over PXE.But when booting to the USB in UEFI mode, the computer is stuck in a loop...When booting to legacy mode, it's no problem, but then the scripted installs fails.

Have also tried this.. My computer is detecting the USB as an UEFI device. I can select it to boot and it appears to start, but then it just keeps on looping a reboot.. I have to do a hard shutdown in order to regain control..

That sounds more like the boot files on the stick are bad. which adk are you using and which bit for booting. I will create a test stick myself to see if this works for me. Also have you tried to uefi boot another model of computer with this same stick

I have helped a couple of others who used the MDT vs the ADK. Helping them we discovered that the KBEM has a requirement for the ADK vs the MDT because location of the source files needed to build the KBEM are not the same between the 2.
see for requirements

Is the ADK really needed to create the bootable USB stick? In the past, I've already oploaded the boot image to Dell KACE. Now, I've just downloaded it from the console and run the install.exe program to write it to disk..

I've just installed a clean windows 8.1 machine, installed the ADK from your link and followed the same procedure.. Same test results apply.. Any other ideas since it's still stuck in a reboot loop? Thanks for your assistance!

Have you tested the stick on another computer? The one thing I got into trouble with testing uefi was putting the stick in the boot sequence. uncheck the stick, you may also have to delete everything out from under boot options also but save that for the second try if unchecking does not work. When you clear that, power the machine off not just reboot. Cold start and hit f12 and bring up the option menu and see if it sees the stick as a boot option.

I've just tested it on another computer and it doesn't work either.. But on this computer I get the Windows logo from the WinPE and then it reboots again and the same loop continues. Also done the other suggestion but same results as before :( Other suggestions?

Thanks for the extended information, SMal.tmcc! I did exactly the same thing, but it didn't work (only in legacy mode)..

I just tried it with another boot image and this seems to be working in UEFI and BIOS mode..
This brings me to my question: What could be the cause of it not working on UEFI but still on BIOS..

The boot image I'm trying to use was manipulated by another engineer with a prestart command (launch a HTA file in the temp folder on the KACE server. HTA is used to insert computername & user which needs to be local admin on the computer). I've manipulated it later with DISM so it has an AZERTY lay-out. Upload was done with the KBEM.

Maybe it's the prestart command but it works in legacy mode, so strange it doesn't in UEFI.. Any ideas? Appreciate the help!

With the new kbem you can add that file to the boot and call as boot step vs trying to run it from the server. This is what I do currently on KBE designed for capturing purposes only. Create a folder on your tech station, place the file(s) in it to upload into the KBE and in the kbem under configure - modify kbetools check add files to kbe and point it to that folder. then under add custom dos commands add a command to open that hta "x:\applications\file.hta"

Thanks for the suggestions! I will try this first thing on monday (No connection to the office atm) :) Not sure if this would help.. Either way the custom dos command is trying to run the HTA locally from the stick (X:\) or the petemp on the K2000 (T:\).. But worth the try ofcourse!

Did you manage to get an USB stick (FAT32/UEFI) running on a computer with a prestart command from the local drive?

Alright, I've just done some additional troubleshooting.. There was also another bootimage located in KACE which used a prestart command to run a HTA-script on a remote server.

I downloaded this bootimage, created bootable USB-stick (FAT32/UEFI) and tested it ==> Bootimage is loaded..

So I guess the bootimage (which works great in production by using PXE and NTFS bootable stick) may be corrupted I guess..

I will create a new bootimage with the KBEM, add a prestart command (connection to server), use DISM to change locale, upload to Dell KACE + download the bootable files to create a new FAT32/UEFI boot stick.

Alright, so I've finally got UEFI USB booting to work in my specific scenario.. Since KBEM doesn't let me choose a different keyboard lay-out, I need to use DISM for my support engineers so they can enter some values in the custom HTA.

Below, I list all tests which I've tried to get a working KBE in KACE from which I can create a boot image.. Sadly enough, it wasn't possible. I refer to test 5 & 6. In test 5 I got a working boot.wim file which I can use on a bootable USB stick. When I upload this custom WIM-file to Dell KACE and download the bootable stick, it isn't working.. I have no idea what the KBEM changes to the BOOT.WIM.

Anyone got a solution for this? I would like to get this boot.wim also in KACE...

try this trick. take your modified boot.wim file and rename it winpe.wim and replace the wim in the adk with yours.
C:\Program Files\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim
Then use the kbem to create a boot env

Hi SMal.tmcc! Thanks for the suggestion!! I will try this tomorrow @ the office and report my findings at the forum and also to the author of the kbem. It might help other users.. CU 2morrow and thanks for the suggestion!!

Hi Smal.tmcc, I just tried to replace the winpe.wim in de 8.1 ADK, but it didn't work. The KBEM is stuck in the phase "Adding KBE registry settings". It let it be for 30 minutes, but it just didn't work. After copying the Original winpe.wim back, it uploaded in 1 minute.. I'm now going to create winpe 10 boot image, maybe better luck with this.. We'll see and I let you know ;-)