Yes and when I go back to V1 I get: Boot failure. Reboot and Select proper Boot device or Insert Boot Media in selected Boot device.
I have already setup a new virtual network adapter and have the BIOS configured to boot to the Legacy Network adapter. Thanks, Brian From: [email protected] To: [email protected] Subject: RE: [MDT-OSD] PXE issue on Hyper-V (Srv 2012 R2) Date: Wed, 11 Dec 2013 09:54:19 -0800 C:\windows\system32>err 0xc0000359# for hex 0xc0000359 / decimal -1073740967 : STATUS_INVALID_IMAGE_WIN_32 ntstatus.h# The specified image file did not have the correct format,# it appears to be a 32-bit Windows image.# 1 matches found for "0xc0000359" Are you running as a v2 style Virtual Machine? What happens when you go back to v1 style? From: [email protected] [mailto:[email protected]] On Behalf Of Brian McDonald Sent: Wednesday, December 11, 2013 9:39 AM To: [email protected] Subject: [MDT-OSD] PXE issue on Hyper-V (Srv 2012 R2) I am attempting to PXE boot a Hyper-V VM running on a Windows 8.1 host. I have an SCCM 2012 R2 environment running on Windows Server 2012 R2 (PXE Server). I get the following error: File: \Windows\System32\boot\winload.efi Status:0xc0000359 Info: The application or operating system couldn't be loaded because a required file is missing or contains errors. The searches I have done are relating to UEFI. Thought I'd try my luck here to see if anyone else has run into this. Thank you, Brian
