Describe the issue
Using UTM 4.3.2 beta release with a Windows 11 ARM guest, with the new TPM and Secure Boot support, out of the box Windows Update still refuses to change the insider channel to Canary and update to a new build.
I created a fresh VM using 4.3.2, deliberately using a VHDX from an outdated build (25346, while 25905 is current). Windows Update then claimed that no updates were available, other than the usual antivirus definition updates. On the Windows Insider screen, after linking my account, I still had a yellow box warning
Your PC does not meet the minimum hardware requirements for Windows 11. Your channel options will be limited.
The Insider Settings were locked to Release Preview with other options greyed out.
I downloaded and ran PC Health Check which complained "The processor isn't currently supported for Windows 11. Processor: virt-8.0". However it did give green check marks for Secure Boot and TPM 2.0, as well as RAM, disk space and number of cores.
Not sure if it might be as simple as just changing the name reported for the processor (is there a qemu command line option for that?) or if it is doing some deeper checks.
This can be circumvented with the following two regedit hacks as described here:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability : BranchName -> CanaryChannelComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\UI\Selection : UIBranch -> CanaryChannel
At that point Windows Update is able to begin downloading and installing build 25905 (though UTM crashes before it can complete, see #5477). Note that the other registry hacks and TPM bypass scripts listed at the above link are not needed.
Configuration
- UTM Version: 4.3.2
- macOS Version: 13.4.1 (c)
- Mac Chip (Intel, M1, ...): M1 Pro
Debug log
debug2.log
Upload VM
config.plist.zip
Describe the issue
Using UTM 4.3.2 beta release with a Windows 11 ARM guest, with the new TPM and Secure Boot support, out of the box Windows Update still refuses to change the insider channel to Canary and update to a new build.
I created a fresh VM using 4.3.2, deliberately using a VHDX from an outdated build (25346, while 25905 is current). Windows Update then claimed that no updates were available, other than the usual antivirus definition updates. On the Windows Insider screen, after linking my account, I still had a yellow box warning
The Insider Settings were locked to Release Preview with other options greyed out.
I downloaded and ran PC Health Check which complained "The processor isn't currently supported for Windows 11. Processor: virt-8.0". However it did give green check marks for Secure Boot and TPM 2.0, as well as RAM, disk space and number of cores.
Not sure if it might be as simple as just changing the name reported for the processor (is there a qemu command line option for that?) or if it is doing some deeper checks.
This can be circumvented with the following two regedit hacks as described here:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability:BranchName->CanaryChannelComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\UI\Selection:UIBranch->CanaryChannelAt that point Windows Update is able to begin downloading and installing build 25905 (though UTM crashes before it can complete, see #5477). Note that the other registry hacks and TPM bypass scripts listed at the above link are not needed.
Configuration
Debug log
debug2.log
Upload VM
config.plist.zip