Hello i installed vmware fusion and download windows for arm but the vmware doesn't see the vhdx extention file which is windows 10 for arm. Does it have support for windows for arm? Thanks
@MartyLVT I'm sorry you don't like the answer, but it is what it is.
You make the determination if you can live with it. There are those of us on the forum that can see if we can help if you run into something unexpected. There's also always the chance that "it won't work and there's no fix for that".
VMware has made its decision based on its legal team's examination of Microsoft's support and licensing stance and Microsoft's public statements that it will not support Windows on Apple Silicon.
@DapperDonnie - I found that some audio capability was enabled when I edited the VM's .vmx file and changed the guestOS type to arm-windows10-64. You might want to give that a whirl....
What exactly is going wrong with the Microsoft Store? Is it not present on the VM or is it there but doesn’t work?
myself I solved it as below
Step 1 (finding ARM Win version & Installing BREW)
On below link find ARM version which you would like to run and download it from UUP dump: https://uupdump.net
Install BREW via terminal (Homebrew: https://brew.sh)
1. To install it run below command on terminal
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
2. Follow the screen on terminal, once done, check last few lines on terminal with “Next Steps”
copy past comand and run following “Next Step” : “echo….”
Step 2 (getting ISO file)
for me direct run of sh file didn't work so i followed below steps
1. still in terminal got to folder where UUP was downloaded
2. once you are inside folder run below command
brew install aria2c cabextract wimlib-imagex chntpw genisoimage
3. when is done you will have to give permission to run the .sh file with below command
chmod +x uup_download_macos.sh
4. Run the sh file (upp_download_macos.sh)
5. Leave it to do the process at the end
Step 3 (Installing VMware)
Follow the standard VMware
Step 4 (Windows Installation)
1. When windows setup starts and you are on the step to choose Windows version (Home, Pro etc) do not clieck next but you will first need to open CMD
fn+shift+F10 to open CMD
2. Run below command to open registery editor
3. Go to HKEY_LOCAL_MACHINE/SYSTEM
4. Rght click on Setup folder choose New and option Key
5. inside of new key create 2 DWORD (32bit) values
6. Modify both as with 1 hex value (ON)
7. Close registery editor and CMD
8. Continue the process to finish Windows instalation
Step 5 (Fixing Internet problem)
1. When you are in Windows profile you will not have internet
2. Open CMD as admin to fix it
3. Run below commands
1st bcdedit /debug on
2nd bcdedit /dbgsettings net hostip:10.0.0.1 port:55555
4. Restart the VM and you should have internet
I too have had issues with that error message. The discussions say to "go download a build from uupdump.net" but don't give you a lot of help for which build to download. My gut feeling was that I was somehow downloading the wrong build.
I just had success downloading the Latest Beta Channel build
This build seemed to find the installation media and virtual hard drive. I installed is successfully using the complete set of instructions posted by @ZigaD with one exception:
In the Windows Installation step 4, after creating a new key under HKLM\System\Setup with regedit, you should rename the key to LabSetup. Then create the two DWORD values under that.
I had the same issue with the Windows installer not seeming to find the media. My thought was that I downloaded the wrong build but couldn't get reliable guidance on what build to download. I had success with the instructions provide by @ZigaD and the Latest Beta Channel Build from uupdump.net.
While the instructions above were a good collection of all the steps needed in the installation process from an ISO, I found what I think to be one addition to the procedure. During the Windows installation step, there are instructions to open regedit and create a new key under HKLM\System\Setup. Other sources I found recommend that this new key be called LabConfig, and not the default name that's presented for a new registry key. Once I renamed the key, the two DWORD entries were added to that key and installation proceeded successfully.
I've followed the instructions with a Win10 and Win11 ISO....
Both give me a Load Driver error... "A media driver your computer needs is missing...." and then "No device drivers were found. Make sure the installation media contains the correct drivers."
Did I miss something? Any idea why this may be?