DC in Hyper-V VM after reboot is not working

This is why it's particularly bad to have your only Domain Controller as a virtual machine too, by the way.

What happens when you have to reboot the host, and the only Domain Controller goes down? Oh, right, the host and the other domain-joined VMs can't authenticate against the domain when they reboot, because the Domain Controller isn't available yet. They'll error out after being unable to contact the domain, which is the likely cause of the errors you're seeing.

Get yourself a second Domain Controller, and make it a physical machine this time.

And, as mentioned in the comments, you shouldn't run DHCP off a Domain Controller. It causes problems, like you're seeing.