0

I've got a Server 2016 Standard guest running on a Server 2016 Datacenter Hyper-V 4 node cluster which cannot start the Hyper-V NIC due to the following error:

"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)"

I'm facing all the same problems and have tried all the same solutions, that were tried in THIS thread, all to no avail. This includes:

  • Removing recently installed updates
  • Removing and re-adding the vNIC at the host level
  • Removing all phantom NICs from the guest
  • Attempting to update the driver in the guest, but it's the most recent one
  • Attempting to update the driver for the host NIC, also the most recent one
  • Restoring from backup, but the problem comes back after installing any updates released after October 2017
  • Screaming into the void

I can get it working by disabling driver signature verification, but I really don't want to do that as this is a security related server. I have multiple other VMs running extremely similar configurations, at the guest and OS level, in the cluster, all of which are fully patched, none of which have any issues.

I really don't want to have to reinstall and reconfigure, especially if this is caused by some particular configuration on the VM which will make this occur again. Reinstalling means I need to reconfigure not only the server, but a bunch of the clients that depend on it as its certificate will change.

There's nothing that seems pertinent in the eventlogs.

  • Removing and re-adding the vNIC at the host level - Do you mean you removed it from the settings of the VM? Removing all phantom NICs from the guest - Why would there be phantom NICs? – joeqwerty Mar 2 '18 at 2:45
  • Was this a p2v machine? – Jim B Mar 2 '18 at 4:01
  • @joeqwerty yes, removing from settings, then rebooting. By phantom, I mean ones that Windows holds on to after they're deleted in device manager that cause Windows to yell at you when you set the same IP on a new NIC. – RobbieCrash Mar 2 '18 at 4:14
  • @JimB no, it was created via the New VM wizard in MSFCM. – RobbieCrash Mar 2 '18 at 4:14
  • this is strange. VM should see Microsoft Virtual Switch as the network adapter in case if you are not passthrough this NIC. Maybe updating integrated services will solve this. – Strepsils Mar 5 '18 at 14:42
0

Try this:

  1. Power off the VM
  2. Remove all NICs from the VMs configuration
  3. Start the VM
  4. Start a new CMD and run the following commands: set devmgr_show_nonpresent_devices=1 start devmgmt.msc
  5. Go to View and then select Show Hidden Devices
  6. Start regedit.exe
  7. Go to HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\Interfaces
  8. This registry key should be completely empty now, if you find some sub-keys, export those registry keys (backup) and delete them
  9. Power off the machine
  10. Re-add the NICs
  11. Reinstall the Hyper-V guest drivers
  12. Reboot again and retry
0

As i mentioned i have problems with 7 drivers and not just the NIC.

I took a Snapshot of the VM, and replace that 7 files, which were not signed, from another VM with same IS version. The file version on the affected server was wrong, but if i try to update the IS, it told me that it'S up to date.

Then reboot, the server rebooted twice, and everything is ok. Additional reboot was also ok.

Can't guarantee that this will work forever, or cause later other problems, but it is not a critical server. So will see:)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.