Hyper-V Dynamic memory fails when you have Memory Integrity on

Question

On a Windows 2019 Server with Hyper-V on, I am running a Windows 2019 Server.

The VM has Memory Integrity on and, because Memory Integrity is a Virtualization technology, I also switched on nested Virtualization.

In the VM, the following Event is logged:
Source: Hyper-V-Guest-Drivers
Event ID: 5
Message: The dynamic memory driver failed because a nested instance of Hyper-V was detected.

I know you can not use Dynamic Memory with a nested HyperV server, but I don't think that the VBS should block the use of Dynamic Memory.

The most strange thing is that with multiple VM's, all configured the same, only a few give this message; all others are working fine with VBS and Dynamic Memory.

Is it a bug that Dynamic Memory won't (always) work with VBS security on the VM or is there somewhere a setting that enables this configuration?