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.
me_likey_sbsAsked:
Who is Participating?
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Got a backup that can be restored to a new set of VHDX files on the same VM husk (leave existing VHDX files for later)?

If that can be done, then once the restore completes use the existing VHDX files to recover more recent data by mounting them in the VM guest after it has booted using the SCSI Bus.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Is the VM's OS up to date?
0
 
me_likey_sbsAuthor Commented:
Yes. Both Host & VM are up to date.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
On the host:

Get-NetAdapter
Get-NetLbfoTeam
Get-VMSwitch
0
 
me_likey_sbsAuthor Commented:
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
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.
0
 
me_likey_sbsAuthor Commented:
Thanks Philip, but the Intel supplied drivers only do to Server 2012, not R2. So I am unable to team the NICs.
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
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.
0
 
me_likey_sbsAuthor Commented:
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
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Boot to Safe Mode.

Start a command prompt
set devmgr_show_nonpresent_devices=1 [Enter]
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.
0
 
me_likey_sbsAuthor Commented:
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
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Suggestion: Create a new VM. Attach the existing VM's VHDX files. Boot. Does the problem go away?
0
 
me_likey_sbsAuthor Commented:
I have tried that twice, on 2 other hosts, and the same problem persists.
0
 
me_likey_sbsAuthor Commented:
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.
0
 
Seth SimmonsSr. Systems AdministratorCommented:
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
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.