I got a Windows 11 21H2 for ARM Home
edition version 22000.282 from UUDUMP last night, downloaded it, installed it, and activated it by transferring the Windows 10 Home digital license I had been using on an X86 Mac. I'm ignorant about Windows versions and totally baffled about what UUDUMP does so I don't have much confidence in the system, but I've installed Microsoft Office and 1Password and they appear to be running happily. The remainder of this message is a step by step procedure. It's really long. I apologize if it irritates those of you who already know how to do this but I surely wish I'd found something like it. Maybe Parallels will use it as an outline of a kb article and delete this post.
1.0 On UUDUMP.NET
1.1 On the Home page:
I selected "Windows 21H2" in the row of "buttons" for different versions in the middle of the page but I don't really remember why. 282 is working OK for me so far but, if I was starting over, I'd pick the first (most mature) Windows 11 for ARM version in the Quick Options, currently 22000.160 in "Latest Beta Channel build".
1.2 On the "Browse known builds" page:
Click "Upgrade to Windows 11 (xxxxx.xxx) arm
64" where xxxxx.xxx is the version you selected. Be careful not
to select the AMD version,
"Upgrade to Windows 11 (xxxxx.xxx) amd
64". It's easy to do as I can tell you from sad experience.
1.3 On the "Upgrade to Windows 11 (xxxxx.xxx) arm64" page:
I just kept clicked Next without changing any of the defaults.
1.4 On the next page, also titled "Upgrade to Windows 11 (xxxxx.xxx) arm64":
Uncheck "Windows Pro" in the "Choose edition" list along the left side. I don't know what will happen if you leave both Home and Pro checked.
There's nothing to select in the "Additional edition", "Required edition" lists on the right. I think they're just information for people building other editions.
1.5 On the "Summary for your selection" page:
Verify the Update is "Upgrade to Windows 11 (22000.282) arm64"
and the Edition is Windows Home.
I left the default "Download and convert to ISO" and "Include updates (Windows converter only)" options selected.
Click "Create download package".
In the new file dialog box that appears, select a folder on your desktop computer where UUDUMP will put stuff.
"Create download package" doesn't do anything but put a small ZIP file containing command line scripts there. When you run one of them below, it will download all the Windows components and build an ISO file in subfolders of that folder. These took 8 GB for me so pick a location with enough space.
2.0 On your desktop computer in macOS, Download Windows components and build an ISO file:
UUDUMP supplies linux, macOS and Windows scripts. The instructions that follow use the macOS script on the ARM Mac where Windows will be installed.
2.1 In Finder, unzip the ZIP file if it didn't unzip automatically.
2.2 Start a Terminal session. (Finder -> Applications -> Utilities -> Terminal)
%cd to the unzipped folder.
It should contain the file "uup_download_macos.sh" among other things. I've never used UUDUMP before and have no idea what could have gone wrong if it doesn't. All I can suggest is to start all over from the beginning.
2.3 Try to run the script
Enter the command:
You'll probably get something like the following:
One of required applications is not installed.
The following applications need to be installed to use this script:
- genisoimage or mkisofs
macOS requires Homebrew (https://brew.sh
) to install the prerequisite software.
If you use Homebrew, you can install these using:
brew tap sidneys/homebrew
brew install aria2 cabextract wimlib cdrtools sidneys/homebrew/chntpw
2.4 Install HomeBrew
On the "brew.sh" web site, follow the instructions to install HomeBrew. Then enter the commands from the previous message:
%brew tap sidneys/homebrew
%brew install aria2 cabextract wimlib cdrtools sidneys/homebrew/chntpw
These take awhile and produce LOT of terminal messages.
2.5 Try to run the script again
The script should download the Windows packages and produce LOTs of terminal output. Eventually it shows a list of all the packages and whether they were or were not successfully downloaded. The first time I ran it, a half dozen were not and it stopped with the message:
aria2 will resume download if the transfer is restarted.
So I entered the same command again. It skipped the packages that had already downloaded successfully, downloaded the ones that had not, and went on to create an ISO file with no input from me. I don't know why downloads fail sometimes, how often you might have to try to get them all or how to tell when something's so badly wrong you need to do something other than just keep retrying.
3.0 On your desktop computer in macOS: Create a new Virtual Machine in Parallels.
In Finder, navigate to the folder where the script was stored. The ISO file should be there now.
Right-click the ISO file, select Open With and Parallels.
Parallels will create the new Virtual Machine as it usually does when you start with an ISO file.
4.0 On your desktop computer in Windows: Activate it
Start the new Windows Virtual machine if Parallels didn't start it automatically.
I'd Exit Coherence so it's easier to find and see Windows programs.
Select Start -> Settings -> System -> Activation which opens the Activation window.
I'm working from my memory now. Since my copy is activated, it doesn't display the activation procedure anymore.
On the window that asks how you want to activate Windows, click "Troubleshoot".
It will display a dialog that, among other things, give you the option to transfer a license you already own.
When you select it, it will open a window that shows all the licenses you own that could be transferred to the new installation. Just pick one.
This makes it sound a LOT easier than it was. I spent a couple of days wrestling with it First it said the license server wasn't working at all. Then it wouldn't display my existing Windows 10 licenses. Then it said they couldn't be transferred. I don't know what I did to fix it or whether Microsoft just finally got the license servers working properly again but last night it all went just as smoothly as I described above. The moral is, if About on the new Windows does say it's a Home edition and if you know you have valid Windows 10/11 Home edition licenses, don't give up too easily.
Click to expand...