Windows 10 ARM install fails with BSOD on Apple Silicon

[dinosauria123]

installing Windows 10 ARM on Apple M1 from ISO image get "System thread exception not handled" blue screen when installer starts to files.

The installer also gave bsd when formatting nvme disk image.

MacOS: big sur 11.6 (Apple M1)
UTM : v.2.4.0

[GhostLestat]

I encountered the same issue with UTM 2.4.0 and 2.4.1. I tried changing the GPU emulator but it also didn't help.
This is what I saw in debugging
debug.log

I also tried changing version from QEMU from 6.1 to 5.2 but it didn't change a thing

[AaronAdams]

I'm having the same issue. Macbook Air M1, Monterey 12.0.1 (21A559), UTM 2.4.1 (40). This seems to have something to do with the disk image. I'm using NVMe disk interface according to the instructions in the UTM gallery. The installer fails when it writes to the disk image. Rebooting after the blue screen causes another blue screen. Deleting and re-creating the drive allows the installer to run again, but the install fails in the same place. I've tried some other disk interfaces but they result in no disk being recognized in the installer.

[conath]

Have any of you tried to use VirtIO disk interface and provide the driver during the install? Here's how to load the driver (video) and this is where you get the driver ISO (click the link that ends with ".iso").

[AaronAdams]

Thanks for sharing that. I followed the instructions in the video and they worked, but they're for x86 emulation, and it's so slow as to not be useful. I'm attempting to get the ARM version of Windows 10 working with some kind of disk image.

[conath]

I was trying to link you to the section of the video where I show how to load the VirtIO storage drivers. This works for Windows for ARM as well, the only difference is in the driver folder you need to choose. Here are the steps in writing.

Edit: first change the hard drive interface from NVMe to VirtIO in the VM config. then follow the steps below.

To load the VirtIO Storage driver during Windows Setup:

1. VM: Get WIndows setup to the point where it asks "Where to install Windows?" but no drives displayed
2. VM: Click Load Driver
3. VM: Click Browse
4. UTM: click CD button in toolbar, change to virtio-win-0.1.208.iso
5. VM: Browse to the path D:\viostor\w10\ARM64 and click OK
6. VM: click Next

After step 6 the drive will appear.

7. UTM: click CD button in toolbar, change to Windows ISO
8. VM: click Refresh

Now continue installing Windows as usual.

[AaronAdams]

Thank you for your patience. I did exactly what you instructed and the driver was loaded and the disk was recognized, but the install still resulted in a blue screen with "System thread exception not handled" when the Windows installer moved on to the next step, which appears to be writing data to the drive.

[jwhitehead74]

I'm having the same issue. It was nice to see others working through this in real time as I was encountering the error. I was also able to load the driver and was even able to partition the disk but immediately get the error as soon as it tries to copy files.

[conath]

Alright, so we have ruled out the hard disk interface as the cause of the problem.

I'm not sure it's a good use of everyone's time if we continue to debug each of your configurations. Please try with known-good settings by downloading my Windows 11 Template (opens in UTM) or manual download. The template is set to VirtIO storage but you can change it to NVMe if you don't want to do the "Load driver" dance. I would recommend you do the dance, though, and also load the "netkvm" driver (D:\NetKVM\w10\ARM64) to have network on first boot.

[AaronAdams]

I downloaded your template and opened it in UTM. Went through the installer and did the driver dance for both viostor and NetKVM. The install fails at the same spot with the same error.

[jwhitehead74]

I downloaded your template and opened in UTM. I mounted a Windows 10 ARM64 ISO I created from uupdump.net and began the install. Mine also fails at the same point with the same error. Is there a known good ISO I can use to install Windows 10 or another method I should be using?

[jwhitehead74]

I also wanted to point out that I'm installing on a new 16" MBP with an M1 Pro (10-core).

[conath]

It would appear the (current) Windows 10 ARM is not compatible with either UTM or the M1 Pro. I can test on M1 (non-Pro), if you point me to how to get the ISO.

In the mean time, please take a look at VM Troubleshooting and comment with your Debug Log here if there are any warnings or errors in there.

@dinosauria123 which Mac (CPU) were you using when you got the BSOD?

[conath]

For what it's worth, I have seen a M1 Pro MacBook 16" run Windows 11 ARM in UTM yesterday. However that was Windows 11 and it was already set up on my machine and just copied there.

[AaronAdams]

I got the ISO following the directions in the gallery.

I've attached my debug log. The relevant lines seem to be:

qemu-aarch64-softmmu: warning: Spice: playback:0 (0x1430c0120): setsockopt failed, Operation not supported on socket
qemu-aarch64-softmmu: warning: Spice: record:0 (0x1430c01d0): setsockopt failed, Operation not supported on socket

debug.log

[jwhitehead74]

I created my ISO using the scripts and instructions from uupdump.net. Specifically, I chose version 21H1 (19043.1348).

https://uupdump.net/selectlang.php?id=3a8bd75d-4189-4223-84c3-ce2b6f9e9460

English, Windows Pro only, Download and Convert to ISO, all boxes unchecked (no updates).

[conath]

@AaronAdams I don’t believe those lines are related to this issue as I have seen those elsewhere before. You can verify by starting the VM again, booting into Setup and then closing the VM without attempting to install. Are the lines still there in the new log?

[jwhitehead74]

I got the ISO following the directions in the gallery.

I've attached my debug log. The relevant lines seem to be:

qemu-aarch64-softmmu: warning: Spice: playback:0 (0x1430c0120): setsockopt failed, Operation not supported on socket
qemu-aarch64-softmmu: warning: Spice: record:0 (0x1430c01d0): setsockopt failed, Operation not supported on socket

debug.log

I had the same errors. I then disabled sound and network. I tried again and got the same blue screen without those lines in my debug log.

[AaronAdams]

@conath I did as you requested and the same two lines still appear in the new log. The new log is identical to the old even though I did not attempt an install. It would seem that the error causing the blue screen is not being captured by debug mode.

[jwhitehead74]

@conath I just now downloaded Windows 10 18363.1916 arm64 and converted to ISO. I used your utm template to attempt the install. I received the same error. Is there a known good version of Win10 on uupdump that I can test?

I was really hoping to run Windows 10, but I'll attempt an install of Windows 11 22499.1000 once it finishes download/convert to ISO...

16" MBP M1 Pro 10-core
UTM 2.4.1 / MacOS 12.0.1
WIndows 10 19043.1348 (21H1) -- System Thread Exception Not Handled
Windows 10 18363.1916 -- System Thread Exception Not Handled

[conath]

Win11 requires TPM bypass to run in UTM. Easier way for Windows 11 is to use DISM to install - @AaronAdams it has not occurred to me earlier but you could try DISM method as well.

[AaronAdams]

The DISM method also does not work because attempting to format the drive in step 1.6 causes the VM to blue screen.

[jwhitehead74]

Windows 11 install is now failing due to the QEMU USB-EHCI reset issue. I think maybe the universe has decided I shouldn't use the Windows. I'm on 2.4.1 where this is supposed to be fixed, too. I enabled debug logging and will try again and post a log.

[wingcomm]

Same issue here. I'm running an M1 Max.

[conath]

Based on the M1 Pro / Max hosts mentioned here I changed the title of the issue.

If indeed this is a Hypervisor related problem specific to M1 Pro/Max:

One way you all should be able to work around the BSOD is to turn on “force slow emulation” in the UTM Preferences. The install will take 2-3x longer but should not crash. After you arrive at the OOBE/desktop for the first time, shut down the VM and disable slow emulation again. It might very well BSOD again after that, but it could be worth a try.

[GhostLestat]

Based on the M1 Pro / Max hosts mentioned here I changed the title of the issue.

If indeed this is a Hypervisor related problem specific to M1 Pro/Max:

One way you all should be able to work around the BSOD is to turn on “force slow emulation” in the UTM Preferences. The install will take 2-3x longer but should not crash. After you arrive at the OOBE/desktop for the first time, shut down the VM and disable slow emulation again. It might very well BSOD again after that, but it could be worth a try.

I have this issue on 13" Macbook Pro with regular M1

[AaronAdams]

Based on the M1 Pro / Max hosts mentioned here I changed the title of the issue.
If indeed this is a Hypervisor related problem specific to M1 Pro/Max:
One way you all should be able to work around the BSOD is to turn on “force slow emulation” in the UTM Preferences. The install will take 2-3x longer but should not crash. After you arrive at the OOBE/desktop for the first time, shut down the VM and disable slow emulation again. It might very well BSOD again after that, but it could be worth a try.

I have this issue on 13" Macbook Pro with regular M1

I also have an M1, but a MacBook Air.

[MichaByte]

I'm also having this issue. MBA M1.

[supersonic-jet]

Any news on this issue? Looking forward to a solution.

[dbz2k]

I could never got any stable build windows 10 to run on apple silicon I even tried parallels desktop, and got a blue screen. Only builds of windows 10 that worked for me we're insiders builds, and those are expired builds because of the time bombs.

[p85dl]

I could never got any stable build windows 10 to run on apple silicon I even tried parallels desktop, and got a blue screen. Only builds of windows 10 that worked for me we're insiders builds, and those are expired builds because of the time bombs.

Thats exactly my case, only useless iso work....We are far away from this working as it used to with Intel cpu...

[Peter-991]

I have the same issue as @2231puppy, @AaronAdams, @wingcomm, @GhostLestat, ... on my MacBook Air M1 (Big Sur 11.5.2). It ends up with a BSOD.

I have tried different ISOs: Win10, Win11 (with and without backups, with NVME or dancing with the VirtIO setting)
(according to tutorials like this and discussions like this here)

Result for Win10: BSOD (during installation process)
Result for Win11: after nearly complete installation --> reboot after installation failed with BSOD-like screen and message that: "reboot failed, ... may be updates are missing, try to connect to internet. Ensure internet connection..."

I have tried to use a qcow2 file converted from a VHDX file of Win11 from Microsoft following this tutorial
Result: freeze of system after random time (several minutes during installation)

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). On the other hand there are plenty of people which try and fail.

What (detail ?) makes the difference?

[TylerHagan1980]

Same issues on an M1Pro

[dixyes]

Using self compiled qemu, with windows 10, I've found this bsod always happen when windows kernel discovered a drive that installed windows. whatever the drive is connected via viostor/nvme/uas/vioscsi.

this bsod needs these conditions:

1. windows 10 arm64 os, whatever pe(installation media) or running copy at tcg/kvm, not sure if windows 11 is the same.
2. 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)
3. windows os discovered a dirve that installed windows, whatever installed by dism+bcdboot or from install media

this can happen at a hvf qemu when

1. a working windows (at tcg/kvm) copy booting and found the drive itself installed in
2. a pe (installation media) booting found another working windows drive
3. a pe installing vioscsi/viostor driver from fedora, it will find working drive, then crash
4. a pe with empty disk, in installing process, the "working windows" just created, then crash

I have no idea about that. that's so strange.

To prove this, I've found these won't crash:

1. a working windows without viostor driver, linked in vm with virtio-blk, this will cause a boot error.
2. a pe linked in vm with nvme/uas, and a working windows linked in with virtio-blk, only if you installed viostor driver
3. a pe and a formated disk (esp+ntfs) linked in with virtio-blk, loading viostor wont make it crash,

[Tazovsky]

I'm working on MBP with M1 Max. I used this Windows 10 Pro build https://uupdump.net/download.php?id=89eb19cc-ed12-45c1-8a99-f06535b800ca&pack=en-us&edition=professional + set Set Isolate Windows from Mac + removed TMP chip and it successfully installed Win 10 Pro and I am able to run VM:

See my Parallels config below:

[eodrap]

@Tazovsky thanks for this info. Using the build you linked to with UTM and either a NVMe or virtio disk, installation starts to copy files but eventually fails...

This is on a 2021 MBP with the M1 Max processor.

[Tazovsky]

@Tazovsky thanks for this info. Using the build you linked to with UTM and either a NVMe or virtio disk, installation starts to copy files but eventually fails...

Did you remove TPM Chip?

[eodrap]

@Tazovsky thanks for this info. Using the build you linked to with UTM and either a NVMe or virtio disk, installation starts to copy files but eventually fails...

Did you remove TPM Chip?

Nope - I'm using UTM not Parallels, but thought you might have stumbled across a good build which worked in both.

[tycho]

I think this discussion of installing build 21390 is off-topic, as that is an older (May 2021) insider build in the branch that eventually became Windows 11. This issue is about installing Windows 10 specifically.

[conath]

I am wondering if we should close this with the recommendation to install Windows 11 for ARM.

I just successfully installed Windows 11 ARM (build 22523.1000) in UTM 3.0.0 beta. I used the Windows 11 for ARM template available on my website, and also attached here: Windows 11 for ARM.utm.zip

I followed these steps to bypass the TPM and Secure Boot checks during install.

[eodrap]

@conath are you using a M1X processor? When trying here using your template and the same build of Windows 11, ISO built via UUP, I get the "Windows cannot install required files" error during the copy phase.

[conath]

@eodrap No, I am on M1. The install error you are seeing is a known issue, just have to re-try - sometimes it goes through just fine. It's pretty random. See #3194

[osy]

Note this only applies to the issue in the OP. There is a separate issue with "Windows cannot install required files" that is tracked in #3194

This is caused by using a version of Windows that is too old. Use https://uupdump.net/known.php?q=21390

The default on UUP Dump for Windows 10 is 19043 which doesn't support Windows 10 ARM64.

[devi3g]

FYI : Have been. able to install windows 11 arm64
kudos to directions from @conath (#3304 (comment))
On a. MBA M1: had. been. experiencing the issue with windows 10 installation failing "System thread exception not handled"

• had used the UUMP compiled iso for. ARM64
• was using UTM v3.03 ( build 44)

Working Configuration
using UTM v3.03 ( build 44). ( same. as. before )

• using windows 11 arm64. downloaded from MS site
• url : Windows 11 ARM (build 22523.1000)
• format : VHDX file
• size :9.5. gigs
• NB : you will need a windows insider program. account ( free to sign up for one when you attempt download)

I used the following setup instructions
used instructions. provided with the UTM windows 11 page

• start VM. set up. wizard. ( add VM )
• selected the. option "import. vhdx*
• browsed and. selected the downloaded. VHDX
• selected. default. RAM setting ( 4GB ie half of what. I have : )
• Started the VM
  When the. VM. boots the first time , it does load the virtual disk , and. initiates the window set up. After a few minutes , it reboot ( first thought is had. crushed ) , then when back up , it spits some hardware info, AND CONTINUES with the. windows set up .
• i chose to setup without an internet. connection ( wanted to get a basic. setup working first )
• set up completed without a hitch
  now trying to get networking working , and to. test the. window11 ( new to it )

Attached is my resultant. UTM VM. template (

• too big. to share ; 4.67GB

[devi3g]

Issues with Network and. Display after initial install of windows 11. ( not a. real issue )

• the network connectivity. was not. available, and the. window display resolution was. stuck at. 800x800
• these issues got. resolved. after installing. the spice tools ( as per UTM windows 11 installation instructions .

[N0rdmann]

I know old/closed thread but as this showed up when searching for most recent win10 build to run on my M1 Pro I wanted to summarize my findings:

• Win10 def. runs way faster/snappier than 11 for me 😋
• The only Win10 Build running virtualized on M1 ARM VM (no matter if UTM/Parallels/VMware Fusion) seems to be #21390 which unfortunately is only available as an expiring Insider Build
• Like on later win11 builds MS Security UI is missing (Get-AppxPackage Microsoft.Windows.SecHealthUI did not fix it for me)
• running mmc.exe in last win10 arm build is blocked by security (cant be unblocked since Security UI is not working), still runs from an elevated cmd, e.g. using pstools: PsExec.exe -d -h mmc devmgmt.msc
• x64 emulation is included & runs very well 👌
• Nag screen after every boot can be disabled by renaming C:\Windows\System32\LicensingUI.exe (need to take ownership and set full permission for your user)
• Main problem after expiring Build (in October) is that it wont boot anymore due to expired certificates > this can be fixed by disabling flightsigning

this command will enable the system to trust Windows Insider Preview builds that are signed with certificates that are not trusted by default

Maybe this helps someone a bit ;)
Went through quite some hassle with this but in the end i still prefer it over current W11 arm builds 😎

[cdowen]

Win 11 installation from iso is also failing with the same behavior.

[mio-19]

21390 is not downloadable anymore on uupdump. Are there other sources for getting 21390 iso?

[HaroleDev]

Based on the M1 Pro / Max hosts mentioned here I changed the title of the issue.

If indeed this is a Hypervisor related problem specific to M1 Pro/Max:

One way you all should be able to work around the BSOD is to turn on “force slow emulation” in the UTM Preferences. The install will take 2-3x longer but should not crash. After you arrive at the OOBE/desktop for the first time, shut down the VM and disable slow emulation again. It might very well BSOD again after that, but it could be worth a try.

Yeah, it is a hypervisor-related issue, even with all the other virtualization software. I think I should try other builds I can gather on the internet and see if one works with the earliest build working. (with hypervisor acceleration)

[SG5]

Have same issue like in message #3304 (comment)
Used an instruction from https://docs.getutm.app/guides/windows/

Macbook air m2. UTM 4.3.5

cc: @osy

[TheBobPony]

Bump, found out the first available ARM64 build that works with Apple hypervisor enabled is Windows 10 Build 19577. There's some quirks due to time bomb such as more UAC popups.
https://twitter.com/TheBobPony/status/1721451923537019008

[N0rdmann]

quirks due to time bomb such as more UAC popups

Try renaming LicensingUI.exe + disabling flightsigning as I've mentioned above