I've noticed in testing on live machines that it makes boot entry after boot entry when I run the image process over and over. Only way to get rid of them is to go into the BIOS and toss them.
Mark Kent (MCP) Sr. Desktop Systems Engineer Computing & Technology Services - SUNY Buffalo State From: [email protected] [mailto:[email protected]] On Behalf Of Roland Janus Sent: Monday, April 7, 2014 7:23 PM To: [email protected] Subject: [mssms] Multiple file boot entries or faulty config on Hyper-V Gen 2 (UEFI) 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: [cid:[email protected]] A new deployment of 8.1 to such a system creates a new entry in that list and works fine: [cid:[email protected]] But when that VM is re-installed, every new installation creates an additional "file" entry. [cid:[email protected]] 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: [cid:[email protected]] 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?
<<inline: image001.png>>
<<inline: image002.png>>
<<inline: image003.png>>
<<inline: image004.png>>
