Separate names with a comma.
Discussion in 'Parallels Desktop for Apple Silicon (M1) Mac' started by kundanno, Jun 23, 2021.
Glad it all worked. Thanks to everyone who's replied to me on this subject as well!
And thanks for your help too!
You can download via UUDump the ARM version. It's a bit trickier to make an ISO with a Mac, but I made one with a Windows machine without any trouble or installation of additional software. YOu can use the instructions here to get the ARM 22000.194 vs the 22458 Dev channel release (that is the only one being pushed anymore): https://www.tomshardware.com/how-to/clean-install-windows-11
I installed the windows 11 but seems to have not Microsoft Store on it can you guys verify for me ::
So far so good. Just performed a Windows Update on my M1 Macbook Pro with Parallels Desktop 17 for Mac. Windows 11 Pro, version 21H2 works fine for mail, YouTube, Netflix, and web browsing so far. More testing to do.
Windows 11 from the Windows Insider Program.
I see anf understand how to install 22000.160, and it will upgrade to 22000.194. I am in the Insider beta program, and am on 22000.282. Once on 194, am I able to rejoin the Insider program and get beta updates, say to the current 282?
Using build 22000.160 from uupdump is outdated. You can build an iso for 22000.282 (https://uupdump.net/selectlang.php?id=2cd33c3d-825f-4216-9ef4-2e2cef0bc077). I haven't tried installing that build myself, but I have tried 22000.258 and can confirm that that works. I put the link here as well in case there's a problem with 282. https://uupdump.net/selectlang.php?id=24b475a3-b2b0-4464-82d1-2dd0d4a9eed8.
22000.282 is also the current release version, so you don't even need to join the Insider Program to update to that build. But, of course, you can join the Insider Program again if you want to.
Thanks @MichaelH63 ! So once I got on the latest build and joined Insiders again (I am on it now), would I get new updates as I do today on my Intel Mac?
Yes, you would.
hi - what happens if you don't enter a key and what happens if you do enter a key?
i'm getting the message on screen that i need to register a key. as others have mentioned, to do that, you have to install the microsoft store app. i believe finally have the store app installed. (it was difficult!) but then what shows up to purchase is windows 10/11 pro "upgrade to workstation" for $199.
1) is that the product i want? i don't really need any of the pro features. i just want to run the windows program tradestation. but as others have pointed out, what parallels installed was windows 11 arm pro.
2) will the key work? one of the consultants i paid today to help me download the store app said that the current build shown on my virtual machine can't be registered on arm even if you buy a key. that the arm version is an unofficial beta release and can't be registered.
3) do i even need a key? the consultant said that even when the "trial period" expires, i will still be able to run my windows program, tradestation, i just won't have access to various other windows features. does anyone have experience with what happens if you don't enter a key?
Hello. I am new to this party, first time attempting to use Parallels virtualization on a Mac. I am using a Mac Mini (2020, M1, 16GB RAM, macOS Big Sur v. 11.6). And I am attempting to use Parallels Desktop 17 for Mac (v. 17.1.0 (51516)).
If I am understanding things correctly, the only version of Window OS that Parallels can accommodate for an M1 machine is Windows 11 Insider Preview through the Windows Insider Program. Is that correct? Or are there other options available? I would prefer Windows 10, since that is the last Windows OS that I have experience with, but it seems that is not possible...
For those of you who are in this (or a similar) situation and using Windows 11 Insider Preview, how is that working for you? Is it running fairly smoothly? Or any issues I should be aware of?
I am looking at the Insider Program registration page, and I don't like this line about potentially experiencing crashes, security vulnerabilities, data loss, or damage to my device... But is this actually something to be concerned about?
My main objective is to use Microsoft Word in its native Windows environment without having to go to the extreme of investing in a PC... the Mac version of MS Word is fine, but it lacks some quality of life features that would help make life more efficient for me.
1) No, you probably want a Windows 11 Pro key. If you already have a Windows 10 Pro retail key from a previous installation that you no longer use, you can just use that.
2) Your consultant is wrong. The key will work on an insider Preview.
3) Not necessarily. If you run Dev Channel builds you don't need a key unless you want to use personalisation features.
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) arm64" where xxxxx.xxx is the version you selected. Be careful not to select the AMD version,
"Upgrade to Windows 11 (xxxxx.xxx) amd64". 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:
%sh uup_download_macos.shYou'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/chntpw2.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/chntpwThese take awhile and produce LOT of terminal messages.
2.5 Try to run the script again
%sh uup_download_macos.shcommand 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.
Thank you for the detailed explanation. This is the first confirmation I have seen that Windows Home does work.
Two quick notes.
1) You wrote that you would choose build 22000.160 if you had to do it again, but the build you chose this time (22000.282) is actually the most recent release build and the best option. Build 22000.160 is a Beta build that predates the release version of Windows 11.
2) That's a great explanation of how to build an iso on macOS in steps 2.0-2.5. If you already have a Windows installation, it is much easier to do with the Windows script, though. There's no need for any extra software. Just double-click on the script and wait for it to finish. Then copy the iso file to macOS.
No. You can install the release version of Windows 11. I was on the Dec Insider channel for several months, and then one Dev build blocked M1 Macs. There were threads here about that, and also about installing the release build with uupdump, which is what I have done and been getting regular updates.
I don't know if the Dev Insider channel is working again for M1 macs. I also don't know anything about the current Windows 10 ARM situation.
It certainly is a confusing and frequently changing situation, but this forum has followed the twists and turns and has been the only useful source of info for me, with some great contributors.
One aspect to be aware of is that the Windows ARM EULA says it is only licensed for use on OEM machines, which means M1 Macs are contravening the EULA. In corporate business contexts they would fail a software audit. I am told that this does not make using it illegal per se, but does mean MS could theoretically sue. Since MS knows I am using an M1 Mac and still activated my Windows 11 release with licenses linked to my MS account, I am not losing any sleep over this. But it is a consideration for corporate users. I think we are probably in a tolerated limbo while MS, Apple and Parallels work out their positions.
Been doing some catchup and re-reading and think the build I was thinking of when I wrote the above was a minor perturbation. I have the impression that the Insider options are now working, though since I made a fresh Windows 11 release VM I have been out of touch with the Insider programme. Apologies if I misled.
I installed Win 11 Insider Edition and was able to activate it with a youtube video related to misguides. It was fairly simple, although the server was busy and it took a few attempts to finally activate. Since then, I have spoken to Parallels tech support, and surprisingly, they have no information as to the status of Win 11 Insider Edition (can it be activated, should it be activated, and if so, can you use a Win 10 product key to do so). It is really surprising that Parallels is not more definite about this issue considering if Windows doesn't work properly, there is no need for Parallels!
I tried to to install the Windows 11 release per the instructions with uup, but when the terminal windows opens and asks to hit any key, the terminal window disappears and nothing else happens.
Going forward, do we know if the Insider Edition (which says "evaluation copy" on the bottom right hand side) will eventually be updated through Windows Update to a release version where you will be able to activate with a proper Win 10 product key?
Can the Insider Preview be activated? Yes.
Should it be activated? That depends on how much it bothers you to be reminded to activate it and on your need for personalisation options.
Can you use a Windows 10 key? Yes, a Windows 10 Pro key works.
Will the Insider Preview be updated to the release version? No. The builds are far ahead of the release version. There will be frequent updates to newer builds in the Dev Channel, though.