![]() ![]() To my knowledge and from my own attempts, running 64-bit VirtualBox VMs alongside Hyper-V is still a 'no-go' area. At that time no-one was reporting any success with such an arrangement, hence the oft-repeated (and still current) forum advice to deactivate Hyper-V and more recently Windows features that now make use of the inbuilt Windows Hyper-V architecture such as WSL2 when problems are experienced.Īs you will see from more recent comments there have been some improvements, but these, from reports received, are only apparent when running 32-bit VMs and there are fewer and fewer of those available. The original post was about the VirtualBox developers' early attempts to try to get VirtualBox working on a Windows PC that did have Hyper-V activated. In fact, it was and is still the case that, for most people, it's best to not have Hyper-V installed or activated when they want to see VirtualBox VM's performing effectively. There is no requirement and never has there been a requirement to have Hyper-V active in order to run VirtualBox. I think you are possibly misreading that first post. ![]() It's working great! Thanks to all of you who support this effort! I usually reboot the VM occasionally during installations.ġ7) I finished up by running sfc /scannow from admin Powershell. Maybe only the first one needs to be done, but I did all three.ġ6) Now do your updates, but manually. Here's how:ī) Go to: Computer Configuration | Administrative Templates | Windows Components | Windows UpdatesĬ) I disabled Configure Automatic Updates, Automatic Updates detection frequency, and Allow Automatic Updates immediate installation. I found this wonderful tidbit that turned the turtle into a ghost:ī) Enter this command: bcdedit /set hypervisorlaunchtype offĬ) (WARNING: This will reboot your host computer so make sure everything is closed before you do it.)ġ3) When the host has restarted, open the VirtualBox.ġ5) I restricted updates in the VM so I could pick when to do them, but you must update the original disc to current Windows. Rocketranch dot com/images/1-Processor.PNGġ2) The real bugger was the Hyper-V apparently running in Windows. Rocketranch dot com/images/1-Motherboard.PNG ![]() (The forum rules will not let me post the screenshot links I have saved on my own webserver, sorry.) Select Insert Guest Editions CD image.ġ0) Click the Settings for the VM in VirtualBox Manager. (I can usually find one inexpensively online.)Ĩ ) Go to the Devices tab in the VM. I installed via "Run as administrator."ģ) Double-click the Extension Pack to install it into the VirtualBox.Ĥ) Find an iso of Windows. HyperV is enabled in the BIOS.ġ) Download VirtualBox 6.1.18 and the VirtualBox Extension Pack.Ģ) Install VirtualBox. The operating system is loaded on a Samsung 970 EVO NVMe M.2, 1 TB SSD. The CoffeLake processor has 6 cores/12 logical. I am operating Windows 10 Pro on an ASUS Prime Z370-P with 16GB 2400Mhz memory and an Intel i7-8700K CPU. I thought it important to list the steps I took to reach the endpoint. It was an agonizing experience but I have successfully completed the installation. I spent most of two days trying to install VirtualBox on my Windows Host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |