I'm creating a new Windows 10 VM and following the same methods (Spaceinvader1 and Proxmox) that have worked previously for me, but this time I'm stuck.  I've read countless posts on this forum and none of them seem to fit my situation exactly but did provide some good insight on things to try.  Config and logs are attached - this is running in unraid 6.8.3.

 

I've created the VM as I normally do preferring OVMF to allow pass-through of various devices (My existing Win10 vms are all OVMF).  I'm using a Win ISO downloaded yesterday, and a recent copy of the VirtIO drivers.  I booted fine to the WinISO, and when it came time to choose an installation location I loaded the virtiostor driver to access the vdisk.  I selected the disk and Windows installer went on it's merry way installing.  I left expecting to come back to the "first-run" setup for Windows but the VM is stuck booting to the UEFI shell.

 

Reset goes through the BIOS startup and boot to DVD option, then back to the UEFI shell

Continue goes to boot to DVD option and then to the UEFI shell

 

You can see the misc device appears to be the vdisk image yet it won't boot.

 

If I boot to the ISO and use the system repair tools --

Running command prompt  and diskpart list-disk results in "There are no fixed disks to show."

Running command prompt and browsing the local filesystems I actually see on drive X: what appears to be my windows installation (program files, users, windows, etc.)

Startup Repair couldn't repair your PC.

 

W10-Template-config.txtW10-Template-log.txt
 

Thanks in advance to all!

Try starting a new template with Q35 machine type. Your template doesn't have virtio iso so I would suggest to keep the virtio ISO connected + make sure you install the right viostor driver. And run ISO images as SATA and not IDE.

 

If all fail, try a brand new vdisk as SATA instead of virtio. If that also fails then the problem is with the Windows iso.