Separate names with a comma.
Discussion in 'Parallels Desktop for Apple Silicon (M1) Mac' started by kundanno, Jun 23, 2021.
You can set the preferences for the dock alignment and other things to look more like Win 10.
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.
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).
Had to recreate my VM due to a MBP repair but can't install Win11 any more. Anyone able to do so now?
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.
Unfortunately Microsoft only made an exception to the minimum requirements for Windows 11 for the Dev Channel. The Beta Channel requires full compatibility.
I really hope Parallels will get their software ready soon. Even if they only release another technical preview first. A slightly buggy Parallels with Win 11 compatibility would be better than no Win 11 compatibility at all.
I also hope so, because the next build in the dev channel will be build 22040 (build beyond the release branch) and and once this build is received and installed, it will be impossible to revert to a stable build without reinstalling.
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 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.
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
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
Thanks, that was easy. If I understand correctly, once Parallels becomes compatible with Windows 11, we run the script again to leave the insider program and should then be able to return to the regular Insider program that is linked to our accounts. Since we will be on a beta build, we should then be able to choose the Beta Channel without a problem.
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
Thanks @AlexeyY1 for this handy script.
What a mess with these updates. Microsoft just can't keep it simple can they?
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.
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.
Build .120 in beta channel (with OfflineInsiderEnroll fix) installed OK
Yes, it also works for me.
Not sure where Else to put this, but I was running my Win11 beta originally on P16.5, installed the P17 trial, and just now decided to uninstall the trial (expired) and it corrupted the virtual machine's drive. Sucks because I was expecting to resue' something and now I have to rebuild the OS first.
Sorry for the newbie question, but what does setting the diagnostic to *FULL*? When I got to the Diagnostics & feedback page, do I just turn every option on?