Hi, this issue has been just fixed as https://www.ventismedia.com/mantis/view.php?id=17812
So please re-test in build 2404 once it is posted.

Thanks!

Also, when MM hangs on the copyright screen, it remains the topmost window, and can't be moved, which blocks everything underneath. If you simply close the window, the MM processes (3) still keep running and if you try and restart MM you will not get the copyright or anything else. You must kill the underlying processes to retry. NBD, just info for those trying to recreate.

Are you saying that build 2401 fails to run while 2338 works fine in Hyper-V ?
==============
I just tested to confirm.

1. 2401 hangs on the copyright screen on all my VM's. Not dead still using CPU, but never gets to main window.

2. I uninstalled 2401, then installed 2330. Worked fine on win 10 x64 Hyper-V VM.

3. I uninstalled 2330, then installed 2338. Worked fine on win 10 x64 Hyper-V VM.

4. I uninstalled 2338, then installed 2402. Hangs like 2401 on copyright on win 10 x64 Hyper-V VM.

Just for info, incase it helps: Running MM5 v5.0.02338 on HyperV-VM // OS: Win2016Std without any issues.

I'm able to reproduce GPU process crashing in virtual machine ... hopefully i'll find how to fix it.

Are you saying that build 2401 fails to run while 2338 works fine in Hyper-V ?
Might be related to https://www.ventismedia.com/mantis/view.php?id=17812

Latest MM hangs on MM startup showing MM logo on Hyper-v machines. Works fine on bare metal. Tested 4 different VM's. 64 and 32 bit, all running win10 pro latest updates, both regular and portable MM install. Same results. First test of MM on VMs. Clean install on 3 VM's. One VM is a 64 bit image port of bare metal where MM was working previously. Other 3 VMs are image ports where MM was never installed.

One difference, on bare metal I saw MM com.exe start first time after install, and I had to OK startup. Never saw this on the VM's. No idea if this is related. Running win 10 pro 64/32 bit all around, latest updates, bare metal i7-10700 CPU, 24GB memory. AV is windows defender all around with controlled folder access on. No notification that windows is blocking MM startup.

Hyper-V install is nothing unusual. EFI boot GEN 2 VM on the 64 bit and bare metal machine. MBR boot GEN 1 VM on the 32 bit. VM within VM enabled on 64 bit VM's not on 32 bit.