To prove this, I've found these won't crash: a pe with empty disk, in installing process, the "working windows" just created, then crash.a pe installing vioscsi/viostor driver from fedora, it will find working drive, then crash.a pe (installation media) booting found another working windows drive.a working windows (at tcg/kvm) copy booting and found the drive itself installed in.windows os discovered a dirve that installed windows, whatever installed by dism+bcdboot or from install media.current qemu using hvf at macos arm64 machines (I've tried 6.1.0 with utm patches, 6.2.0-rc1 6.2.0-rc2 and master with a little modification).windows 10 arm64 os, whatever pe(installation media) or running copy at tcg/kvm, not sure if windows 11 is the same.whatever the drive is connected via viostor/nvme/uas/vioscsi. Using self compiled qemu, with windows 10, I've found this bsod always happen when windows kernel discovered a drive that installed windows. On the other hand there are plenty of people which try and fail. What seems strange to me is that there are apparently a lot of guys out there on which machines it works (at least to run a completely installed Windows). Result: freeze of system after random time (several minutes during installation) I have tried to use a qcow2 file converted from a VHDX file of Win11 from Microsoft following this tutorial may be updates are missing, try to connect to internet. Result for Win11: after nearly complete installation -> reboot after installation failed with BSOD-like screen and message that: "reboot failed. Result for Win10: BSOD (during installation process)
(according to tutorials like this and discussions like this here) I have tried different ISOs: Win10, Win11 (with and without backups, with NVME or dancing with the VirtIO setting)
0 kommentar(er)
