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.