Hyper-V framework delayed startup (not the VMs)

I finally upgraded my home server to Windows 11 at the weekend which went fine overall. I use it for my lab with Hyper-V running DCs and other VMs.

Because the server itself boots up in the AD domain it was handy that Hyper-V started up during bootup and usually had the DCs online (from saved shutdown state) before the server desktop loaded.  This was also working straight after upgrading to Windows 11.

I installed the latest VMware workstation 16 in an effort to be able to run a vSphere lab (since Hyper-V doesn't have drivers for vSphere 7) and during the install it said it would have to enable the Windows Hypervisor Platform API in order to better share the underlying hypervisor.

Once that had all been done, now when Windows boots Hyper-V doesn't startup until a few minutes after Windows 11 has booted to desktop.   If I open Hyper-V manager straight away all the VMs are shown in saved state, and you can't interact with anything.  If you try to open the Virtual Switch Manager, it just shows as empty and you can close the dialog box (it doesn't freeze up).

After all other delayed services are started and then some time after, suddenly Hyper-V comes to life and the VMs all startup on their own.

I've attempted to roll back this change by uninstalling VMware workstation and WHP, and even uninstalled Hyper-V and re-installed, but it is now locked into this delayed start.

Does anyone know where to fix this so that Hyper-V fully initialises during bootup rather than waiting minutes after?  I need it to work like this as I have many delayed services that need AD to be present.