I got an error whilst installing Windows 10 from .iso file as virtual machine via Parallels 9 on OSX 10.10 which read something like: Media driver missing. It leaves you in a loop which requires you to add the drivers. But you cannot install any cause there are no suggestions.
Now the main issue seemed that the iso wasn't on a bootable device which is what most sources say you need to do. Obviously that seemed like an unneeded step and i got the installation going. Mostly because you were already inside the installation that had been booted in the first place.
Software i use:
OSX 10.10 (latest)
Parallels 9 (latest updates, i know Parallels 10 is out)
Windows 10 iso from http://preview.windows.com
VM setup with iso from external HD (NTFS) and locally stored.
So what to do?
(see my answer below)
What you can do is shut down your virtual machine (close out the installation first to make sure). Go to the settings of the parallels by clicking:
-> Menubar: Virtual Machine
-> Configure
-> Hardware tab
-> CD/DVD 1 (where your image is inserted)
-> Location dropdown
-> Select IDE 0:1 (instead of SATA 0:1)
-> Restart VM
Done!
Installation will continue normally and you can start trying Windows 10 from Parallels 9 on your Mac.
I'm not sure if this works for Parallels 10 (i think so) and i'm also not sure if this will work for other (older) Windows installations. But to remove the steps required for making a bootable disk is good enough for me.
You can tell to parallels to install it as windows xp and it will work fine.
This issue occurs, also, when you have a MacBook Pro (10,2 or similar) without a DVD drive, while installing Windows 10 via USB.
So, during the Parallels 10 or 11 Guest setup, choose to configure using an ISO instead.
Related
Windows 10 N Pro, version 2004
I had a few different OS VM's setup before I decided to try Docker out.
After installing it and realizing I better stick to VM's I went on my Virtualbox, tried starting my old VM's and couldn't get past the boot screen - the issue is it goes to a black screen.
I created a few new VM's all resulting in the same issue. I tried restarting the machine, Windows Restore, trying different BIOS settings, uninstalling docker, reinstalling Virtualbox, increasing VRAM to 128MB, uninstalling subsystem for Linux, disabling the Hypervisor and sandboxing. The only thing that let me interact with the VM was enabling EFI - although after choosing "boot" option I had the same black screen.
After trying all possible solutions on SO and Google I stumbled upon a comment (which unfortunately I can't find) which pinpointed that Docker installer explicitly overwrites VM/Hypoer registries or processes. I don't know if that's the issue however it is the case.
How can I get my VM's running again without reinstalling Windows?
It sounds like the problem is: 1) You were successfully running VMs with VirtualBox on Windows 10 Pro, 2) You installed Docker, 3) Docker broke VBox. Correct?
Look here:
https://superuser.com/questions/1290051/virtualbox-no-longer-works-after-uninstalling-docker-on-windows-10.
Control Panel -> Programs and Features
On the left side choose "Turn Windows features on or off
Uncheck Hyper-V
reboot
After reboot you have to reinstall/repair your installation of VirtualBox with the original installer!
Reboot again and it should work 🙂
In general, please try posting these kinds of questions on https://serverfault.com or https://superuser.com. StackOverflow is for "programming" questions.
I have VMware and windows 10 installed on a virtual machine on my Macbook Pro. I have an ISO file of windows 10 mounted and sometimes when I restart windows and expect it to restart I'm prompted with the "install windows screen" instead.
It scares the shit out of me. Why is this happening? There seem to be some kind of delay as it seems to auto-magically open windows when I try again.
This morning I thought I had to restart windows all over again and go through 3 days of headache (setting up / installing programs etc), but then I went on a meeting and then it worked. Any thoughts?
Changing the BIOS boot order to ignore the CD-ROM should fix the issue.
However, is there any reason you have the ISO mounted still?
I think it was the iso file on the host, it is mounted. And delete your snapshots.
I have an macbook air 2012, I recently installed Windows 10 in it using bootcamp.
I also downloaded the bootcamp drivers, and a folder named "BootCamp" and "$WinPEDriver$" were created in my Windows10 bootable usb. I was able to use it to install Windows10 and use it.
Then due to space issues I deleted the Windows partition, thinking I can always reinstall it, if needed.
Now I wish to reinstall it, but when I took a backup of the bootcamp drivers, I only backed up the "BootCamp" folder, I forgot to backup the "$WinPEDriver$" folder. Without "$WinPEDriver$" folder, Windows10 get installed without the drivers. When I try to manually start the setup.exe in BootCamp folder, it quits saying "$WinPEDriver$" folder is missing. So I created a empty folder named "$WinPEDriver$". With this the driver installation does proceed, but everything except the Broadcom_Bluetooth_Driver are getting installed. I tried to install the Bluetooth driver alone manually, that also didn't help.
So my question is,
Is there a way were I can download the "$WinPEDriver$" folder alone from Apple site. I live in a place where bandwidth is very low, so downloading another 2 GB of drivers will take 3 more days, and may also get interrupted frequently.
Or can I create the "$WinPEDriver$" folder manually, just as BootCamp Assitant creates it.
Or Is there a way to download the bluetooth drivers alone from apple site.
My bluetooth chipset information is Broadcom USB 20702A3.
Thanks.
Just create a blank folder called '$WinPEDriver$'and it'll work, I know you've probably sorted it by now but i thought i'd leave this here in case anyone else runs into the same problem.
I was able to download Apple bluetooth for windows drivers from a Parallels KB article on titled Unable to use Apple Bluetooth USB Host Controller in Virtual Machine
As for the "$WinPEDriver$" it is included in the newest version of Boot Camp Support Software 5.1.5769 although it is still large at 542.3 MB it is not the 2 GB you feared it would be.
The download includes both the BootCamp and $WinPEDriver$ folders.
Good luck!
Incase anybody needs this when you open up Bootcamp Assistant below the 'Action' tab there is a download button to install 'Windows Support Software'. You can download from there and plug in to the Windows by using flash drive or hard disk and make the setup.
After downloading windows 8 install ISO with Windows 8 media creation tool I booted the ISO from my USB to install windows but when I clicked "install" an error said "A media driver on your computer is missing" How do i fix this?
I had the very same behaviour when trying to install Windows 10 through from a USB flash formatted with Microsoft's MediaCreationTool. The solution has been to install Windows 10 from a DVD rather than from the USB: using a DVD burnt with Microsoft's iso file, the software did not complain.
I have faced the same problem while installing windows 10 using USB and i too downloaded ISO using creation tool only... later again i changed the option like flash drive and downloaded then it worked for me ... may be you can try in this way.
CREDIT TO IllusionX
ORIGINAL SOLUTION HERE
If you are using a USB stick to install, When you get to that error, close everything till you get back to the install windows button. At that point unplug your USB stick and place it into another port and install as usual.
I am using win7. I wish to use Fedora on my machine, but don't know just how much I will be needing either of my OS. I wish to install Ferdora and configure it as a dual boot system.
At the same time, when time calls for it, I want to run the same Fedora installation as a virtual machine on top of win7. Is there a way to do it?
VMWare Workstation supports this, but I've never tried in Windows.
Here's an article on their site (it discusses VMWare 5 and they're now on 7.1, so a newer one can probably be unearthed):
http://www.vmware.com/support/ws5/doc/ws_disk_dualboot.html