Submitted some logs/dumps yesterday and we identified it was because my CPU doesn't have the BMI2 instruction set (old proc).

Weird that this would only happen on persistent VMs

It's because my persistent VMs are on old hardware. My ICs are on new hardware. 🙂

Ah. What CPUs are you on?

My persistent VMs are running on E5-2660v2 (because those servers have vGPU), and my ICs are running on whatever new AMD proc the MS-A2 units have from Minisforum

Ok. Good to know. Will keep VMs off of my old R620s. :)

Which hypervisor (and version) are you running on that E5? I'm going to assume it's not supported on vSphere 7, yes?

vSphere 8, and it's not supported. But either way this bug needed to be found and fixed because I have lots of clients that use special hardware and run the same CPUs, running Windows 11 native and Horizon agent for remoting in to the physical systems. So this would have popped up anyways in those cases as well (forgetting about hypervisor support)

IIRC, those CPUs can do vSphere 7. I don’t think they’re officially supported on 8 but will work…maybe with some tweaks/workarounds that are only found on William Lam’s blog. I just removed my last vSphere host, which was an R620 with an E5-v2, so I can’t check

Windows 11 is fine, it's the CPU check on vSphere that needs to be bypassed.