Been a trying process so far, unfortunately.  First two USB's I tried, the USB creator wouldn't believe had GUIDs (even though I could see them through various tools).  Third one (all sandisk 16GB usb3.2) recognised the guid but then 'couldn't' complete the format, not clear what the issue was there, because windows thought the formatting was fine, at that point fell back on the manual install.

 

There appears to be a typo in the windows make bootable script and it failed as a result (pretty sure the below is meant to be setup)

 

# from make_bootable.bat

:select
echo:
set/p boot="Permit UEFI boot mode [Y/N]: "
if /i %boot%==N (

# pretty sure this should be setup not set/p (at least that's what windows terminal thought it was trying to do):

 

but even after fixing that it still didn't quite seem to work, every time I booted in, got the missing operating system message.  At that point, I flipped the USB into zip mode, added an autorun to point it at syslinux and the .cfg and tried again.  Worked like a charm, I am in, I have got in through the UI.

Now, when I go to start the trial, I get something went wrong > Trial Key Installed Successfully > calculating trial expiration which may or may not be related to the trials that happened before this point..

 

Please let me know what additional info you need.

 

Persistent of Gloucestershire.

I usualy use ubunut mate live boot format fat32 with disk app and lable the whole flash drive as UNRAID... Then extract the files to the USB. then run the make bootable script in windows.

https://docs.unraid.net/unraid-os/download_list/

Trails are 1 month only. contact support with key issues...
 

Make sure date and time are correctly set, reboot and try again, if you get the same, please post the diagnostics.

set/p is not a typo, the SET command is used to set environment variables that can be used by other programs, such as the computer-name for example, or the path where to look for programs.

Specifically that instruction (set/p) says to display a prompt "allow uefi" where you would say Y or N, and store the result in the variable named boot.

Then the next instruction would check if the boot variable contains 'N' and if so, it would disable the EFI folder by renaming it EFI-, or if it was Y, enable UEFI booting by naming it EFI.

Ah, cool, well I guess that's my 5 mins of code learning done for today.  Sadly windows didn't like it anyway!  Curently moving as much away from windows as humanly possible, can't wait to see the back of it.