But one of the issues is that the tools the poster referenced only work on Windows. The script makes that really post, and interesting that they consider what Parallels did "amateurish". Or I can post a manual procedure - but that's complicated if your system language is not US English as you have to go to Microsoft to find the files for the download. I'd appreciate some kind souls to test it out before I include it as part of the Companion. I have a prototype script that automates the build process. And it works on the Mac with only one open-source package download. The ISO build process from a downloaded ESD from Microsoft is actually relatively quick compared to building from. And Parallels' note that they are getting Windows "from Microsoft", while technically true, isn't exactly the same as getting an ISO from Microsoft. I'm still not finding anywhere that Microsoft is providing a ISO, but having an ESD is big step forward. Similar to what Fusion does for its easy install where supported. The Parallels installation process is injecting something in the install, though, since there are a lot of questions in the Parallels installation from ISO that are being answered for you. Keep your fingers what I'm seeing in reverse engineering the process, Parallels appears to be taking the bits for the arm64 boot loader that Microsoft provides in the ESD. If this works out, I'm set to remove all references to uupdump from the Companion guide in favor of this process. It's installing files to the hard drive right now, and in about an hour or so I should have a working VM. I'm going through final testing right now, but the initial tests have the ISO booting entering Windows Setup. The reverse-engineered process uses the utilities in the open source package wimlib-imagex, and the macOS command hdiutil. What they're doing is not rocket science. I did not feel comfortable extracting stuff from the Parallels ISO, so I went down the reverse engineering path to see exactly what they were doing. Given the information the (the link was very helpful) - I have reversed engineer the process that Parallels is using to get a Windows 11 ARM ISO directly from Microsoft (well, they don't get the ISO from Microsoft, but they are getting the ESD and using open source and macOS tools to create the ISO). Hey everyone! I think I have a breakthrough. So who blinks first? Microsoft to release publicly the ISO for Windows 11 ARM, or VMware to provide a similar ISO for download like Parallels does? So, if you have this Windows 11 ARM ISO that Parallels downloaded for you, the installation of a Fusion Windows 11 ARM VM just got a little easier. So far the VM is behaving fine and updating itself to the 2023-02 Cumulative Update for Windows 11 for arm64-based Systems. No issues with the ISO and no changes to the procedures in the Companion Guide. I skipped the procedures in the Companion Guide for building an ISO from and jumped straight to the procedure to create a VM and install from ISO. The ISO appears to be a pretty vanilla version of Windows 11 22H2 (build 22621.525). So I asked myself: "Self, I wonder if this ISO will work with Fusion?" Parallels tech notes say that they are downloading the file "from Microsoft". The first thing that it did was to download a Windows 11 ARM installation ISO file named:ΔΆ_release_svc_refresh_CLIENTCONSUMER_RET_A64FRE_en-us.iso After installation I proceeded to have it install a Windows 11 VM. I installed the trial version of Parallels Desktop 18 as I was curious what build of Windows 11 they were using. I ran a little experiment after seeing what Microsoft and Parallels announced this week.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |