I think there is an issue with Gen 2 VMs with UEFI on Hyper-V (Win 8.1).
A new VM might have those entries for boot:
A new deployment of 8.1 to such a system creates a new entry in that list
and works fine:
But when that VM is re-installed, every new installation creates an
additional "file" entry.
Another issue with UEFI:
When such a system is refreshed, it installs without a problem, but then
Hyper-V says the boot data is broken:
Deleting that entry fixes it:
Firmware Application (101fffff)
-------------------------------
identifier {65c5ef67-bf05-11e3-bcc1-00155d010832}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
Anyone else seeing any of those?
<<image001.png>>
<<image002.png>>
<<image003.png>>
<<image004.png>>
