Возникала ошибка при попытке инсталлировать Windows 7 64-бит в виртуальную машину VirtualBox.
VirtualBox: Windows failed to start. A recent hardware or software might be the cause
Решение оказалось простым.
Достаточно было в настройках виртуальной машины включить параметр IO APIC.
Странно, что ранее меня эта ошибка обходила стороной. Может быть потому, что для Windows XP данный параметр был не обязателен. Часто раньше именно Windows XP использовал в виртуальных машинах.
I get this error when i try to install Windows server 2008 x64 via VirtualBox.
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1) Insert your Windows installation disc and restart your computer.
2) Choose your language settings, and then click ‘Next.»
3) Click «Repair your computer.»If you do not have this disc, contact admin… bla bla bal.
File: \windows\system32\boot\winload.exe
Status: 0xc000035a
Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.
I have All Virtual settings enabled in BIOS and my CPU is an Cor i5 vPro, the host system is Windows 7 x64.
Youtube Screen casting of the error
Jawa
3,61913 gold badges32 silver badges36 bronze badges
asked Nov 1, 2013 at 23:04
2
I just had this problem myself. Turns out I was trying to install a 64 bit OS on a virtual machine that I created before I enabled virtualization in the BIOS. The solution was to delete the VM and create a new one. If virtualization is enabled, you will see Windows Server 2008 (64 bit) as an option when you create a new VM.
answered Jan 9, 2014 at 21:38
Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.
This usually means that your VirtualBox is not running in 64-bit mode. You need to enable VT-x/AMD-V, and possibly Nested Paging from your Virtual Machine config.
In my version of VirtualBox this can be done by:
- Shut down your VM
- Right click on the Virtual Machine
- Navigate to the «System» section
- Click on the «Acceleration» tab
- Check «Enable VT-x/AMD-V», and «Nested Paging»
- Click on «OK» at the bottom to save your settings.
After enabling it from within VirtualBox, if your OS and CPU configuration is correct, then you should now be able to boot Windows Server 2008
answered Nov 1, 2013 at 23:14
Someguy123Someguy123
3901 gold badge2 silver badges8 bronze badges
I realize this is a super old post, but it ranked very high in Google’s results and didn’t contain the solution that worked for us.
We exported .OVA files from ESX and tried to import them into VirtualBox, which led to this error. It turns out that during the import, the OS in the VirtualBox settings was set to «Other»; changing it to the right OS got rid of this problem and allowed us to boot up.
answered Sep 7, 2018 at 15:15
i realized i have selected wrong machine type(32bt-64bit)
my HOST is 64bit and i created 32bit machine type for 64bit guest OS
answered Oct 26, 2020 at 9:38
4
I turned Virtualization on in the BIOS. Deleted the VM I had made before I turned virtualization on. Then I made a new VM with Windows 64-bit OTHER as the option.
HopelessN00b
1,8823 gold badges21 silver badges29 bronze badges
answered Oct 10, 2014 at 14:24
You must log in to answer this question.
Not the answer you’re looking for? Browse other questions tagged
.
Not the answer you’re looking for? Browse other questions tagged
.
-
alib
- Posts: 2
- Joined: 13. Jul 2010, 10:56
- Primary OS: Mac OS X Leopard
- VBox Version: OSE other
- Guest OSses: windows server 2008 32
windows failed to start a recent hardware change
Hi,
I’m new to virtualbox, sorry if I’m asking silly questions
my problem is as follow:
I had a windows XP guest that I’ve imported as a .vhd and everything was working fine.
now the dev team created a new .vhd with windows server 2008 32bit and when I start it I get the same error:
«windows failed to start a recent hardware change»
If some one can help me with this, as I couldn’t fined anything related to this problem for windows server.
Thank you very much for your help
Ali
-
alib
- Posts: 2
- Joined: 13. Jul 2010, 10:56
- Primary OS: Mac OS X Leopard
- VBox Version: OSE other
- Guest OSses: windows server 2008 32
-
ronsfi
- Posts: 1
- Joined: 27. Aug 2010, 02:14
- Primary OS: MS Windows 7
- VBox Version: OSE other
- Guest OSses: Winxp, Server 2008
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: windows failed to start a recent hardware change
Post
by Perryg »
ronsfi wrote:How?
Look at the storage section and mess around with piix3 or piix4
Also look at the network adapter and make sure that you have the right one selected.
You can even try to start it in safe mode to see what the error might be.
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1) Insert your Windows installation disc and restart your computer.
2) Choose your language settings, and then click 'Next."
3) Click "Repair your computer."
If you do not have this disc, contact admin... bla bla bal.
File: \windows\system32\boot\winload.exe
Status: 0xc000035a
Info: Attempting to load a 64-bit application, however this CPU is not compatible with 64-bit mode.
I get this error when i try to install Windows server 2008 x64 via VirtualBox.
I have All Virtual settings enabled in BIOS and my CPU is an Cor i5 vPro, the host system is Windows 7 x64.
Youtube Screen casting of the error
asked Nov 1, 2013 at 21:49
4
I had the same issue and found a solution.
- Open up bios and make sure vt-x is enabled
- If it wasnt, you’ll need to delete the VM in virtual box and make a new one.. Now you will see an option for windows 7 and windows 7 (64bit).
It was only AFTER i delete and rebuilt the VM did it allow me through. Changing the settings in the existing VM didnt seem to do the trick.
answered Dec 13, 2013 at 16:14
PaulPaul
512 bronze badges
1
How to Repair “VirtualBox Won’t Start Windows 10 and 11” Error?
Overview: If you are one of them, who are facing the problem “VirtualBox won’t start Windows 10”. Then you are on the right page, here you will get complete and correct information about VirtualBox, and the reasons why VirtualBox not working on Windows 10 and 11. So without any future ado, let’s get start the topic.
As we all know, VirtualBox is popular and accessible virtualization software that can be installed on various operating systems, including Windows, Linux, Mac OS X, and Solaris, among others. On a single piece of hardware, it is possible to construct and use several instances of Virtual Machines, each of which may be configured to run a distinct operating system.
Reasons Why VirtualBox Not Working on Windows 10 / 11
VirtualBox won’t start Windows 10 implies you can’t operate virtual machines. This problem has persisted since Microsoft began distributing Windows 10 upgrades. Why does this happen?
- Some modules, like Hyper-V, may be deactivated after a Windows upgrade.
- Windows has strengthened its hold on driver installations, whereas VirtualBox installs virtual machine drivers separately, causing conflicts.
- Windows 10 upgrades create problems with virtual machine software. Para virtuality. Changing the settings generally fixes this.
Also Read: How to Recover Data from VDI files of Oracle VirtualBox Application?
Manual Methods to Fix VirtualBox Won’t Start Windows 10 Errors
Here we will show you 3 manual methods, which can be a reason “VirtualBox won’t start Windows 10”. All the steps and methods are mentioned below one by one:
Method 1: Install VirtualBox again
- Open the control panel from your machine.
- Now select the “Programs and Features” option.
- After that, find the virtual box section and then uninstall the application from the machine.
- Make sure that you keep all of the files that you have lately saved to fix VirtualBox won’t start Windows 10.
- Now restart the Windows 10 or 11 machine.
- Next, install the latest versions of the virtual box again.
Method 2: Use the app in Compatibility Mode
- Firstly, click right on the virtual box file.
- Select the “property” option from the appearing list and hit the “compatibility”.
- Hit the “Run similarity trouble-shooter” or you can enable the “run this program in compatibility mode for field” option to fix VirtualBox won’t start Windows 10 errors.
- It is important to remember to save any changes you make and to launch the application with administrative privileges.
- Your copy of Windows 10 should now launch VirtualBox automatically.
Method 3: Update Graphics Drivers
- Use the context menu to right-click the Windows Start button.
- To access the tool management area, click here.
- The information may be gleaned from the display adapter’s entry in the device manager.
- Press the update button after right-clicking on the graphic drivers.
- Additionally, you should understand how to repair the video driver in VirtualBox by following the procedures.
Still, if you are facing the problem, then, you should use method 4, which gives you a 100% guarantee to repair VirtualBox won’t start Windows 10 error.
Method 4: Safest Solution to Fix VirtualBox Won’t Start
One of the best and Superior Tool BitRecover VDI Recovery Utility to fix VirtualBox not working on Windows 10 and 11 errors. The software is totally rich with fruitful and advance features like the software support all types of VirtualBox files like corrupted and damaged. Also, the software compatible with all file systems. The software has powers to detect lost and deleted files and folders easily. Some of the advance capabilities and features are mentioned below to fix VirtualBox won’t start Windows 10:
Capabilities of the Tool to Repair VirtualBox on Windows 10 and 11
- The software is a standalone application, there is no need that you install any third-party utility on the device that you are using.
- Also, the tool has powers to repair corrupted, broken and crashed virtual machine in just few clicks.
- The software support both fixed and dynamic VirtualBox virtual drive images without any restrictions.
- Also, if you accidently lost and deleted your VDI data, then the software provides the option to recover lost and deleted data.
- This software can easily repair data of FAT as well as NTFS file systems, the software is compatible with FAT, FAT16, FAT32, FAT64, NTFS, HFS+, and EXTX files systems.
- There is advance search option available to search the specific data of virtual box to repair on Windows 10 and 11.
- BitRecover VDI repair software has powers to repair VirtualBox of all Windows operating system including Windows 11, 10, 8, 7, and other previous versions.
How to Repair VirtualBox Cannot Start the Virtual Device Issues?
- Download and install the software on your Windows OS to repair VirtualBox won’t start Windows 10.
- Now browse the virtual box files from the system.
- Next, 4 options will appear on the screen, and choose required option as per your need.
- After that, select the required partition or drive from the screen.
- Now the software will scan all the lost, deleted, available files and folders on the screen, and then select the required data.
- After that, browse the saving location according to your needs.
- Lastly, hit the “Save” icon to fix VirtualBox won’t start Windows 10 error.
Time to Say Goodbye
In this write-up, we detailed the approaches to solve the mistake of VirtualBox won’t starting Windows 10 and Windows 11 by utilizing manual and professional techniques. Manual techniques have several constraints, which users will confront throughout the procedure. If you want to repair VirtualBox with a 100 percent guarantee, then you need to take the aid of third-party software like BitRecover VDI recovery tool, which has outstanding characteristics. Furthermore, the software has a demo version for free. So users may use the tool and check how the product work.
Also Read: How to Recover Deleted files from VDI File of Oracle VM VirtualBox?