me_likey_sbs
asked on
Win2012R2 Hyper V "Integration Services Setup" upgrade fails & causes error Code 52 for important Hyper V drivers
Our Windows Server 2012 R2 Hyper V server hosts a Windows Server 2012 R2 VM. An update brought an Integration Services Setup upgrade to version 6.3.9600.18692 (I haven't had time to locate which update this is). This upgrade doesn't appear to complete successfully in the VM, and a number of critical devices (including the NIC) have an exclamation sign on them. The Device status in the device properties says:
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
After much research, I was able to implement a temporary fix by pressing F8 on the VM's boot, and selecting "Disable Driver Signature Enforcement". The VM then boots into the OS fine, and the devices do not have an error.
But this is just a temp (and potentially unsafe) fix. This appears to have occurred previously when Integration Services Setup upgraded to version 6.3.9600.18398, with MS releasing a "fix".
I would like to resolve it permanently. Any help would be greatly appreciated.
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
After much research, I was able to implement a temporary fix by pressing F8 on the VM's boot, and selecting "Disable Driver Signature Enforcement". The VM then boots into the OS fine, and the devices do not have an error.
But this is just a temp (and potentially unsafe) fix. This appears to have occurred previously when Integration Services Setup upgraded to version 6.3.9600.18398, with MS releasing a "fix".
I would like to resolve it permanently. Any help would be greatly appreciated.
Last Comment
Philip Elder
Is the VM's OS up to date?
ASKER
Yes. Both Host & VM are up to date.
On the host:
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
ASKER
Those are pretty dated NICs.
Remove the vNIC from the VM.
Delete the vSwitch
Create a native team with the two ports
Create a vSwitch on the team shared with the host OS
Add a new vNIC to the VM and bind to the vSwitch
Try IS again.
Remove the vNIC from the VM.
Delete the vSwitch
Create a native team with the two ports
Create a vSwitch on the team shared with the host OS
Add a new vNIC to the VM and bind to the vSwitch
Try IS again.
ASKER
Thanks Philip, but the Intel supplied drivers only do to Server 2012, not R2. So I am unable to team the NICs.
New-NetLbfoTeam -Name MyTeam -TeamMembers "Ethernet","Ethernet 2"
Or, in Server Manager on the Local Server page click teaming.
Use the native teaming in the OS. We do that for all of our standalone and clustered virtualization solutions.
Or, in Server Manager on the Local Server page click teaming.
Use the native teaming in the OS. We do that for all of our standalone and clustered virtualization solutions.
ASKER
Apologies Philip, I missed your suggestion for "native" teaming. I did this & still no go.
Just to highlight, the issue is affecting more than the NIC. I've attached a screenshot of all affected devices, along with the message that all devices affected have in their respective "status" windows.
Capture.JPG
Just to highlight, the issue is affecting more than the NIC. I've attached a screenshot of all affected devices, along with the message that all devices affected have in their respective "status" windows.
Capture.JPG
Boot to Safe Mode.
Start a command prompt
set devmgr_show_nonpresent_dev
start devmgmt.msc [Enter]
View --> click on Show hidden devices
Delete anything that should not be there. Once done, remove the Hyper-V components and reboot. They should re-install correctly.
Start a command prompt
set devmgr_show_nonpresent_dev
start devmgmt.msc [Enter]
View --> click on Show hidden devices
Delete anything that should not be there. Once done, remove the Hyper-V components and reboot. They should re-install correctly.
ASKER
Thanks for the suggestion Philip, but im unable to boot into the OS in (any) Safe Mode. When i send the Alt+Ctl+Del key at the prompt, I get an error "Could not send keys to the virtual machine" (See screenshot)
I did try your suggestion booting in normal mode, but still same issue remains.
Capture.JPG
I did try your suggestion booting in normal mode, but still same issue remains.
Capture.JPG
Suggestion: Create a new VM. Attach the existing VM's VHDX files. Boot. Does the problem go away?
ASKER
I have tried that twice, on 2 other hosts, and the same problem persists.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks Philip. I was hoping to avoid that :-) We have a heap of 3rd party software that's a PIA to restore. Plus, i'm afraid we'll still have the same issue once we run updates again.
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: Philip Elder (https:#a42365198)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: Philip Elder (https:#a42365198)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
