Update: Win 8.1 with the update isn't creating additional new file boot entries anymore for every refresh
But there is still that one created:
Firmware Application (101fffff)
-------------------------------
identifier {65c5ef67-bf05-11e3-bcc1-00155d010832}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
causing hyper-v to create the failure message
From: [email protected] [mailto:[email protected]]
On Behalf Of Kent, Mark
Sent: Dienstag, 8. April 2014 17:22
To: [email protected]
Subject: RE: [mssms] Multiple file boot entries or faulty config on Hyper-V
Gen 2 (UEFI)
I use the SMP in a refresh, then have it format the drive.
Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Tuesday, April 8, 2014 11:08 AM
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Multiple file boot entries or faulty config on Hyper-V
Gen 2 (UEFI)
You think it's the format step?
With refresh there isn't a format, still an invalid entry (for Hyper-V) is
created.
Also if that entry is removed and Win8 rebooted it creates it again entry.
That looks like Windows is doing it
-R
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: Dienstag, 8. April 2014 15:25
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Multiple file boot entries or faulty config on Hyper-V
Gen 2 (UEFI)
No difference. If it runs the format and partition disk UEFI step, it
creates another entry.
Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Tuesday, April 8, 2014 9:16 AM
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Multiple file boot entries or faulty config on Hyper-V
Gen 2 (UEFI)
Not sure what should clean up this, if W8.x has to figure out there is
already one or CM.
In any case it is annoying and with Hyper-V it breaks the entry :(
Refresh or new install all the time?
Is there a difference for you?
-R
From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: Dienstag, 8. April 2014 15:09
To: [email protected] <mailto:[email protected]>
Subject: RE: [mssms] Multiple file boot entries or faulty config on Hyper-V
Gen 2 (UEFI)
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]>
[mailto:[email protected]] On Behalf Of Roland Janus
Sent: Monday, April 7, 2014 7:23 PM
To: [email protected] <mailto:[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:
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>>
