I recently installed windows 7 on VirtualBox and installed battle.net.
When I start battle.net I get this error: http://i.imgur.com/006cpRC.png
I googled a lot but I was not able to find an anwser :/
Also tried to put Windows 7 on VMWare but that resulted in me getting the same error.
Before this I tried downloading the driver for the GPU I have but then I get this error, http://i.imgur.com/kMacwB8.png
Hope you guys can help me :)
You may need to enable 3D acceleration on VirtualBox. By default it is disabled.
The steps to enable:
Right click the Windows 7 VM in Virtual Box and click Settings.
Click the Display category.
Check Enable 3D Acceleration and increase Video Memory as needed.
Install drivers:
While the VM is running, click Devices menu and then Install Guest Additions
Click Run VBoxWindowsAdditions.exe in the popup and run through the installer.
See: http://www.howtogeek.com/124479/how-to-enable-3d-acceleration-and-use-windows-aero-in-virtualbox/ for extra information.
Note that the article states the 3D acceleration is experimental and should run older games, but possibly not newer games. The article was written in 2012, so I'm not sure what the current state is. You should be able to tell if it's enabled by whether or not the Aero interface is usable.
Related
I am trying to boot up a saved am using Macbook pro with M1 chip.
I tried the steps given at this answer. But was not able to boot up the VM. Can someone confirm this problem or already found out a solution to it?
I got the error "The virtual machine 'Ubuntu 20.04 64bit 1' has terminated unexpectedly during startup with exit code 1 (0x1)." below:
Had the same issue on Mac OS Big Sur 11.4 when I was trying to add my Ubuntu instance (on Intel tho), nothing suggested here and other topics helped.
Turned out you have to give access (Full Disc Access) to Virtual Box in Settings. Go to Settings -> Security & Privacy -> Privacy -> Full Disc Access -> plus sign (unlock it if needed) -> choose Virtual Box Application -> Open.
After that I was able to choose my Ubuntu image in Finder.
<New user, reputation too low to comment on David's post!>
As per David Leitko's answer, VirtualBox is an x86 (more specifically, AMD64/x86_64) virtualization hypervisor. However, it appears from various discussions I've seen on this topic that many users don't really understand what this really means.
So, it means not only that VirtualBox only runs on x86 CPUs, but also that it requires all the other elements of the x86 platform. These include system memory, various bus controllers (PCI, USB), hard disk controllers, sound cards, graphics, BIOS/UEFI, etc. None of these take the same form on the Apple Silicon platform - i.e. they don't use any of the standards built up in the PC ecosystem over the last 40 years.
So, not only will VirtualBox not work on Apple Silicon, it will never work on Apple Silicon. There will never be any way to run a VirtualBox image that ran on an Intel Mac on an Apple Silicon Mac. Ever.
The canonical discussion thread on the VirtualBox forums that covers this in more detail is here.
VirtualBox is an x86 virtualization hypervisor. It only runs on an x86 platform. See https://www.virtualbox.org
While Rosetta 2 will run many x86 apps very well on an M1 Mac, virtualization products are not supported per this Apple document
I just had the exact same problem after updating my VirtualBox app on MacOS Big Sur. What worked for me was to go to System Preferences - Security & Privacy - General, and then click the Allow button to allow extensions by Oracle (first click the lock symbol in the lower left of the screen and enter your password).
Actually, during installation I got this pop-up window telling me to do this, but I wasn't quite sure what exactly it wanted me to do. Only after getting this error I took the trouble of looking closer, ahem...
Hope this will fix your problem too!
Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 months ago.
The community reviewed whether to reopen this question 3 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I'm running windows 10 enterprise trying to launch a VM in Virtualbox and it fails with the error.
"VMMR0_DO_NEM_INIT_VM failed: VERR_NEM_MISSING_KERNEL_API_2 (VERR_NEM_MISSING_KERNEL_API_2).
VT-x is not available (VERR_VMX_NO_VMX)."
I have HyperV disabled in windows features and core isolation turned off
I've checked the registry as well and core isolation / memory itegrity is off there. I've also made sure that in group policy settings that virtualization based security is disabled.
My BIOS does have VT-X /VT-D enabled.
I'm currently on Virtual box 6.1.6 but have tried previous versions back to 6.0.12 with no success.
This happens to me from time to time on my Windows 10 host. I tried a lot of things to fix it, but what worked in the end is running this command as an administer in PowerShell:
bcdedit /set hypervisorlaunchtype off
and rebooting the computer.
I got this error too. I got passed it by uninstalling VirtualBox, removing any residual files, and then reinstalling VirtualBox.
Based on Google search results of this error, posts about it started appearing only a few days ago. I found out how to get passed this error from one of the comments on https://www.reddit.com/r/Windows10/comments/g4hksf/virtualbox_problems/.
By the way, the only Windows feature that needs to be turned off is HyperV.
I had the same problem. Tried the turning the HyperV off and rebooting but that did not work. My BIOS had Virtural turned on too. What fixed it for me was to go into BIOS, turn the virtual off then reboot it. Then reboot again and go back into the BIOS and turn virtual back on.
I got the same error, and simply enabling BIOS VT-x was enabled, but simply enabling again BIOS VT-x got rid of the error. Uninstall virtual box, delete Virtual box files in program files, and in ProgramData
In windows 10
Settings-> Update & security->Recovery -> Advanced startup ->Restart now
Next after restarting choose
Troubleshoot ->Advanced options->UEFI Firmware Settings ->click Restart
Then select F10 ->System configurations->Virtualization Technology select enabled and pressed enter
Exit Saving changes->Select yes
Then reinstall virtual box, hope it helps
I followed these steps here (like you did) and nothing worked.
Eventually, I disabled VT-d in my BIOS, and suddenly I was able to run VirtualBox machines. I have no idea why it worked, just try it if you have nothing else to do.
I did all the steps I found on the Internet, but I solved the problem by installing virtualbox version 7. The previous version was version 5 and my windows version is 10
This happend with me when windows 10 updated to windows 2004
So to fix this Make sure you disable the feature HyperV of windows feature
start -> Windows Features -> Windows Hypervisor Platform -> uncheck if checked.
restart your PC.
then try vagrant up or start the virtualbox machine again
Recently I installed VirtualBox 6.1 on my MacBook Air and installed Windows 10 on it (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/), but somehow the sound on my guest Win10 is not working. I managed to dig for some info and found out that I need to install (https://www.realtek.com/en/component/zoo/category/pc-audio-codecs-ac-97-audio-codecs-software) but it does not work. Could anybody help me with this one?
EDIT: I get the error when I hover over the sound icon: "no audio output device is installed"
Fixing the sound on guest windows 10 where the host is Linux / Mac
Open the settings for your Windows 10 machine inside of virtualbox
Go to Audio > Host Audio Driver, change to "ALSA Audio Driver"
Go to Audio > Audio Controller, change to "ICH AC97"
Enable Test Mode on Windows 10 and reboot machine.
Download and install the Realtek driver for Vista/Win7 (32/64 bits) Driver only (ZIP file) from here and reboot your Windows 10 machine.
Disable test mode from the link in 4th step then reboot your Windows 10 machine.
In case you still have a crackling / popping sound
In the task bar, right click on the sound icon and choose playback devices
Double click on Speakers
Select the Advanced Tab
Set the Default Format to 16 bit, 44100 Hz (CD Quality)
In the Exclusive Mode, Uncheck the Allow applications... etc
Select the Enhancement Tab
Check the Disable all sound effects
Make sure you click apply then OK
The crackling sound would immediately disappear but you could reboot just to verify.
I tried the route in the most upvoted answer but couldn't get Win10 to install the AC97 driver. For me the solution was much simpler: select Audio Controller "Intel HD Audio" in the virtual machine settings (and leave Host Audio Driver to whatever the default was, in my case "Pulse Audio"). Enable Audio Output checked of course, and it should just work like the machine has a sound card.
Crackling is still there even with the stuff about turning off enhancements and exclusivity, but I think that's not going away since I'm trying to play 1080p video and I don't think the virtual machine has quite the kind of video hardware access (and memory allocation) that it needs to play this level of content perfectly smoothly.
Install Guest Additions if you haven't already. More info here for your specific case: https://www.virtualbox.org/manual/ch04.html#additions-windows
Host Linux Mint. Guest Win10. Had 'Guest Additions' installed, 'Host Audio Driver: Pulse Audio', 'Audio Controller: Intel HD Audio'. Sound in Win10-guest, but not in Commandos 2 or Patrician 3.
Installed Realtek drivers (https://realtek-download.com/wp-content/uploads/2014/07/6305_vista_win7_pg537.zip (thank you Wil)). Still no dice.
Win10 said: "No output devices found".
Changed Host Audio Driver to ALSA Audio Driver. And it worked! Thanks everybody.
With Fedora 36 host and Windows Server 22 Standard Desktop Evaluation as guest inside VirtualBox 6.1.34 it automagically worked after enabling sound at guest via:
Mouse Right Klick at (disabled) speakers symbol in Windows taskbar
Mouse Left Klick at "Sounds" (German)
-> See Screenshot
Accepting the prompt enabled sound with all default settings in VirtualBox VM Audio Settings:
Host Driver: ALSA Audio Driver
Controller: Intel HD Audio
VirtualBox 6.1.34 Oracle VM VirtualBox Extension Pack was also already installed here.
Sound tested successfully with Firefox 100 and https://fip.fr -> Rock
I am using Oracle vm with windows as host machine and linux on VM. I had everything working, but once i used 'power off' when it took time to start. Since i am not able to start the OS on VM. I am getting errors as below.
Error relaunching VirtualBox VM process: 5
Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment RedHat_Linux_64bit_4GB --startvm 42e4c558-83d4-431c-a971-71ca9e1f4112 --no-startvm-errormsgbox "--sup-hardening-log=C:\Users\bhargav.vijay.desai\VirtualBox VMs\RedHat_Linux_64bit_4GB\Logs\VBoxHardening.log"' (rc=-104)
where: supR3HardenedWinReSpawn
what: 5
VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name.
I am able to see a file in snapshots folder which is large in size. (2016-08-16T05-57-16-295692800Z.sav). Have uploaded an image. I am on lookout for solutions.
Restart of the system helped me resolve the issue. Also the snapshot files (.sav extensions) are of no use in this case.
This ref https://forums.virtualbox.org/viewtopic.php?f=6&t=82277 fixed issue for me for VB version 5.2.x on Windows 10.
I had tried other approaches like installing earlier versions of VB but nothing else worked for me.
I had the same problem on a new HP Elitebook with Windows 10 preinstalled.
Install Virtualbox and import applience worked fine, and can be startet.
But after next restart of the System Virtualbox always shows an Error...
... supR3HardenedWinReSpawn what: 5 VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name.
I tryed 4 Days to fix the Problem inclusive deactivate preinstalled hp client security, windows defender etc.
Nothing worked until I found the Link of the latest post.
I had to reinstall Virtualbox and deactivate the VBoxdrv sevice in the registry.
After every Windows start i need to start the service manualy or over shedule...
After that Virtualbox starts correctly!
I tested a lot. Windows seems to destroy the Virtualbox installation while driver was loading on startup.
If the error occures once, one has to reinstall Virtualbox and deactivate the service... deactivate after the Error has already showen dosent work.
I was struggling with this one on HP Elite Book for some time and I found solution here.
The solution is to go to
HP Sure Sense -> Settings -> Advanced Settings
and turn off Enhanced Thread Protection.
It's not my solution, but I hope it's good to have here for someone in the future.
a) Clear AppData/Local/Temp
b) Completely uninstall any VirtualBox currently installed
c) Restart the computer
d) Install the latest version of VirtualBox
e) After install completes do not restart the computer
f) Open the registry editor. Start > Run > regedit
Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
Edit the key called Start. Change it's value from 1 to 3
g) Close the registry editor and restart your computer. After your computer restarts you should be able to use VirtualBox without any issues.
I downloaded the simulator for BB Bold 9930 (v. 7.1) at http://us.blackberry.com/sites/developers/resources/simulators.html
My Windows VM follows the system requirements at http://developer.blackberry.com/bbos/java/documentation/the_bb_smrtphn_simulator_447179_11.html, except for one thing: OpenGL 1.x compatibility, which I can't figure out how to test (see Windows 7 on Virtualbox virtual machine: is it OpenGL 1.x compatible?).
So installing this and launching C:\Program Files\Research In Motion......\9930.bat causes the following error to come up:
"An OpenGL 1.x + compatible video card with recent video drivers is required for graphics acceleration. Please try a lower graphics acceleration setting by navigating to the view menu".
Clicking on the view menu is impossible until I click OK on the modal dialog, but when I do so, the program immediately crashes with the message "BlackBerry Handheld Simulator has stopped working".
Is there any way around (through the command line, for instance?)
You should be able to force the simulator not to use the graphics acceleration at all (which hopefully would work around your problem).
See this BlackBerry forum thread here.
Basically, just include this in your simulator config file:
<?xml version="1.0" encoding="utf-8"?>
<fledge-configuration>
<BodyBuilder::opengl-acceleration>0</BodyBuilder::opengl-acceleration>
The setting of 0 turns off graphics acceleration. You can either turn it off by default in your simulators, or just in one particular simulator, by using the fledge-saved.conf file, or 9900-saved.conf file (for example, to change the setting on the 9900 simulator).
On a Windows system, these config files would be located somewhere like:
C:\Users\myname\net\rim\fledge-2\