This KB is like VMware spitting in people's face.

There's a reason one might want to have an autostart for VMs.
There's also a reason why someone might want to have a *working* console for a VM in case something goes sideways.

How come HyperV also offers autostart for VMs without need to mess with service configuration AND on top of that, the console works just fine? If it's a system limitation/security thing, HyperV gets around that somehow.

I do realize this isn't something that's sitting on the top of priority list to fix by devs, but come on... 200$ for a software that's a hypervisor that doesn't have one of the basic functionalities of a hypervisor?

What would the business say if some admin logged into a vCenter after a power failure in a DC just to see that maybe thousands of machines need to be suspended and resumed, because the console doesn't work? That definitely sounds like fun.

VMware is starting to sound like a Todd Howard stating "it just works". Though this time it's the other way around.