Windows 11 on Arm

I think it depends on how old your Windows 10 image is and if you were a member of Insiders before a certain date. If you create a new Windows 10 ARM64 VM and try to update to Windows 11, you'll get the TPM error. Messing around with ISO files is your only chance, until Parallels bring out TPM2.0 emulation.
 
I think it depends on how old your Windows 10 image is and if you were a member of Insiders before a certain date. If you create a new Windows 10 ARM64 VM and try to update to Windows 11, you'll get the TPM error. Messing around with ISO files is your only chance, until Parallels bring out TPM2.0 emulation.
I've been testing Windows 10 ARM for a few months, updating it several times.
 
Anybody having trackpad issues when running windows 11? My trackpad is pretty much limited to point and click- can't scroll at all. Looking at the settings in windows, there is no trackpad options- only mouse. Didn't have any of these issues with windows 10. Anyone have any tips?
Thanks!
 
Just got the Windows 11 update on my M1 MBP running Monterey. So far so good. Both MacOS dev beta and Win 11 beta are running with Parallels perfectly. It is running the Win 11 beta better than my Razer Blade Advanced 15 (2021) did on bare metal... less buggy at least (Win 11 sucks at Thunderbolt currently).
 
Anybody having trackpad issues when running windows 11? My trackpad is pretty much limited to point and click- can't scroll at all. Looking at the settings in windows, there is no trackpad options- only mouse. Didn't have any of these issues with windows 10. Anyone have any tips?
Thanks!
Finally found a way to use the M1 MBA's trackpad to do something other than point and click. It worked scrolling when in Settings looking for information on mouse settings. If you have a built-in trackpad, I would think Parallels would need to include drivers for that in their Tools installation. I checked Parallels settings and they don't mention anything about a trackpad either so I assume (bad idea) normal built-in trackpad use is built into Parallels but not necessarily external trackpads. I'd contact Parallels service directly on how they handle trackpads. Not sure how much they read these forums.
 
Finally found a way to use the M1 MBA's trackpad to do something other than point and click. It worked scrolling when in Settings looking for information on mouse settings. If you have a built-in trackpad, I would think Parallels would need to include drivers for that in their Tools installation. I checked Parallels settings and they don't mention anything about a trackpad either so I assume (bad idea) normal built-in trackpad use is built into Parallels but not necessarily external trackpads. I'd contact Parallels service directly on how they handle trackpads. Not sure how much they read these forums.
I installed the Monterey beta today and for some reason, the trackpad works on parallels now. No idea if they are related or not. There is still no trackpad setting on the options in my windows 11... not going to mess with it anymore.
 
Hi,
Fix is more simple. I have Win11 ARM works correctly in Parallels 16.5. MacBook Pro M1

Steps:
1- Create ISO in UUPDump
2- Extract ISO content in your hard disk
3- Replace in source folder appraiserres.dll files
4- Run setup.exe

Great solution, took a little while to download the UUPDump ISO, also found it impossible to locate the appraiserres.dll on my existing Win 10 ARM installation so I downloaded from the Youtube link where there is a very useful video on installing Win11 in this exact way. Now running smoothly on parallels on MBP M1.
 
Also the UUPDump ISO failed on my computer. During the installation, after a couple of reboots, some error occurred (no idea which error) and the system was reverted to windows 10 ("undoing the changes to your computer" and then reboot to last checkpoint).
 
Has anyone been able to "switch" from Dev Channel to Beta Channel in your Windows Insider Program options under Windows Update?
I only have the Dev Channel option available, other two are greyed out.
Not sure if this is because the Beta Channel is still not available for ARM or due to failing any minimum hardware requirements check.
 
Temporary workaround: You can use the following script to select any Inisider Preview channel. I used it and switched to beta channel in Windows 11. I'm not sure that new beta channel builds can be installed due to lack of TPM support, but at least, if you will switch now, you won't get new unstable dev channel builds.

Download link: OfflineInsiderEnroll (github.com)

OfflineInsiderEnroll
--------------------

### Description
OfflineInsiderEnroll is a simple Windows Command Prompt script to enable access
to the Windows Insider Program on machines not signed in with Microsoft Account.

This script is compatible only with Windows 10 RS5 and later.

### Usage
This script requires administrative priviliges to run. You can simply execute it
by right clicking it > `Run as Administrator`.

#### Installation and configuration changes
After starting the script offers selection of *Windows Insider Program* channels.
To make a selection, press a letter coresponding to option you choose and press
ENTER.

If the machine was not enrolled to the Insider Program, you will get prompted to
restart your machine to enable *Microsoft Flight Signing* which is required by
*Windows Insider Program*.

**Notice:** Windows Insider Program requires telemetry to be set to *Full*.
After enrolling your machine to the *Windows Insider Program* please make sure
that your diagnostic data collection settings are set to *Full*. Some *Insider
Preview* builds may not get offered in *Windows Update* if you do not have
correct telemetry settings. You can verify or modify your telemetry settings in
*Settings* > *Privacy* > *Diagnostics & feedback*.

#### Restoring Windows Insider Program to default options
To restore *Windows Insider Program* to default settings simply choose `Stop
receiving Insider Preview builds` in OfflineInsiderEnroll. You will get prompted
to reboot, because this option will disable *Microsoft Flight Signing*.

### How does this work?
This script takes advantage of undocumented `TestFlags` registry value.
If this value is set to `0x20`, all access to online *Windows Insider* services
gets disabled. Because of this, we can set our own *Windows Insider Preview*
configuration without being overriden by the contact to the service. Since
Windows Update does not check if machine is actually enrolled to the program,
you will get offered *Insider Preview* builds by just setting correct values in
the registry.
 
If I understand correctly, once Parallels becomes compatible with Windows 11, we run the script again
It's not even necessary: if beta channel was selected in the script, the system will receive all beta builds via Windows Update. (or for any other selected channel). But of course, the new beta builds cannot be installed without TPM support in Parallels. So we stucked for build 22000.100 for a while ;)
 
I'm more concerned when they move to release and cut off insider builds. The only real solution is support for a retail Win 10 ARM or TPM support for insider Win 11.
 
I'm more concerned when they move to release and cut off insider builds. The only real solution is support for a retail Win 10 ARM or TPM support for insider Win 11.
My hunch says there will be backlash and they (MSFT) will need to give in a bit. This TPM support more than anything is very annoying.
 
Microsoft just can't keep it simple can they?
Yeah. Actually, even this spring new Windows 10 release was on the way, with new cute "glass Aero" live tiles. But suddenly, everything was cancelled and Windows 11 appeared (with a very bad copy of MacOS dock, as for me). Almost everybody is still shocked, especially about TPM. ;)
 

Attachments

  • Windows-start-menu-from-glass.jpg
    Windows-start-menu-from-glass.jpg
    29.1 KB · Views: 38
Back
Top