The user is clearly marked Admin and the ISO is on a file on his desktop, and shows read/write privileges. (We are downloading the ISO and will try again.) Is it possible the ISO file got corrupted or was disabled when the installation was aborted? In researching, I've seen the following possible causes mentioned: We tried deleting the new Windows VM and starting over by creating a new Windows 10 VM, but attempts to connect to the ISO file produced the same error. Unfortunately we weren't prepared with a working 'Windows Key' and had to abort.Īfter a working key was found, we tried to run the installation again, but VirtualBox, Settings -> Storage was showing a VERR_ACCESS_DENIED error on the ISO file. We were fine during the first attempt, when linking the ISO file and starting the VM. If their site thinks you're not on Windows, they'll offer you direct download links to the ISOs valid for 24h.I'm helping a friend who is trying to get Windows 10 running on his Monterey MacOS within VirtualBox.

The reason is that if they see you use Windows they'll offer you their downloader EXE, which can only download to drive C: and if it's full (which is usual when using a small SSD drive as the main one) you can't download even if you have a secondary drive with several free TBs, since you can't choose another drive. I used this one for Chrome: (User-Agent Switcher for Chrome)

You just have to either use a non-Windows PC (Linux, Mac, Android, whatever.) or use a user-agent spoofer tool so Microsoft's website thinks you're not in Windows. There's another option to download the ISOs from Microsoft.

Virtualbox iso windows 10