@dinhngtu Thanks. I'll try and give that a go in the next few days and will report back.
Note that I have Windows 10 1803 installed without any issues. Trying to update to 22H2 fails with the same blue screen error as you'd expect. Sadly, no crash dump as it seems to fail very early in the boot process.
@dinhngtu sorry, I don't know how to do that offhand. If you point me in the direction of some instructions, I'm happy to give it a go.
@dinhngtu given it’s trying to boot from the installer, where would it save the crash dump to?
@olivierlambert it is a “ Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz”
@acebmxer it is UEFI, and I’ve tried with and without secure boot enabled.
@dinhngtu the host is a Dell Precision T3610 workstation with Intel Xeon processor and 120GB RAM. I used the default Windows 10 (64bit) template. The ISO was built with the Microsoft Windows 10 media creator about a month ago and it successfully installed a VirtualBox VM. The ISO is located on a NFS SR.
@dinhngtu can you please explain what you mean and exactly what information you’re asking for?
Hi,
I've just created a new VM to install the latest version of Windows 10 in. I selected the Windows 10 template and pointed it at the ISO, but whenever I tried to boot it, I get a BSOD with the error "SYSTEM THREAD EXCEPTION NOT HANDLED".
Other VMs on this server are working fine.
@XCP-ng-JustGreat thanks for the info. I have tried following your instructions for a test Windows 10 VM I have and unfortunately it has not helped the issue at all. I will note however that I haven't had a chance to update XCP-ng for a few months now, so I won't be running the latest version.
One 'issue' I have with your theory is that, in my case at least, it's the USB controller that's bombing, which is causing the mouse to stop working. I expect if USB pass-through was being used, this would also stop working for the same reason.
@DevilDan this isn't related to the mouse problem, so you are far better to create a new forum post for help with your issue.
@dinhngtu well arguably it’s one level up from that as it’s the USB controller that’s getting stopped by Windows, so I’d suggest the issue is the virtual YSB controller.
I have done some further testing on this (I have setup a test VM).
What I have learnt:
For what it's worth, my setup is:
I seem to notice the mouse pointer disappearing when moving away from the console window and then coming back (e.g. moving mouse out of the console, changing tab or something like that). Often when I come back, the mouse pointer is nowhere to be seen and I can't get it back.
Just adding a 'me too' to this one - I'm also having this issue (new XCP-ng/XO user). It's very frustrating and seems to be isolated to Windows VMs.