I have seen this issue if Hyper-V services aren't started early enough in the boot process. Specifically, in my experience, Host Commute and VMMS must both be started early. If they start too late then the service fails to get the contiguous block of memory it needs to host VMs (again, in my experience). The only workaround is to reboot because once the memory is not available it is highly unlikely you'll get it.
I don't know how much memory it needs but it would need at least enough to start the VMs that should auto-start.
That's very interesting. Looks like it's the exact same thing, except we didn't update the server.
Were you able to fix it?