VM's fail to start on 7.2.14 after upgrade from 7.2.8

[JoeUK]

I upgraded my VirtualBox env on Windows 11 on my server desktop to 7.2.14. That all seemed fine, however when I tried to start any of my VM's they failed with the below error. The D:\tinderboxa referenced does not exist. If I revert back to 7.2.8 everything is fine.

The upgrade on my laptop which is the same Windows version 7.2.14 works fine. My laptop does not have a D: drive but my server does.

Any ideas.

00:00:04.975548 AssertLogRel D:\tinderboxa\win-7.2\src\VBox\VMM\VMMR3\target-x86\NEMR3Native-win-x86.cpp(2356) int __cdecl nemR3NativeInitAfterCPUM(struct VM *): pVM->nem.s.cbXSaveArea <= sizeof(pVCpu->cpum.GstCtx.XState)
00:00:04.975554 Returned XSAVE area exceeds what VirtualBox supported (10752 > 8192)
00:00:04.975561 NEM: Destroying partition 000001e77e2f38b0 with its 4 VCpus...
00:00:05.154642 VMSetError: D:\tinderboxa\win-7.2\src\VBox\VMM\VMMR3\VMR3.cpp(341) int __cdecl VMR3Create(unsigned int,const struct VMM2USERMETHODS *,unsigned __int64,void (__cdecl *)(struct UVM *,void *,int,const char *,unsigned int,const char *,const char *,char *) noexcept,void *,int (__cdecl *)(struct UVM *,struct VM *,const struct VMMR3VTABLE *,void *) noexcept,void *,struct VM **,struct UVM **); rc=VERR_NEM_VM_CREATE_FAILED
00:00:05.154660 VMSetError: NEM failed to create a native VM instance.
00:00:05.168166 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={6ac83d89-6ee7-4e33-8ae6-b257b2e81be8} aComponent={ConsoleWrap} aText={NEM failed to create a native VM instance. (VERR_NEM_VM_CREATE_FAILED)}, preserve=false aResultDetail=-6805
00:00:05.169592 Console: Machine state changed to 'PoweredOff'
00:00:05.185512 Power up failed (vrc=VERR_NEM_VM_CREATE_FAILED, hrc=E_FAIL (0X80004005))
00:00:05.263083 GUI: Cannot notify guest about VM window in-focus event
00:00:05.263601 GUI: Aborting startup due to power up progress issue detected...
00:00:05.282279 GUI: UICommon: Handling aboutToQuit request..
00:00:05.831043 GUI: UICommon: aboutToQuit request handled!

[klaus]

Very odd... it means that Hyper-V needs more space for saving the FPU state than VirtualBox can provide. Could you attach (if it happens to be too big please ZIP it) a VBox.log from such a failed run?