• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

VirtualBox - Cannot install Win 8.1 Pro, Error 0x000000C4


pillainp

New Member
Posts
5
#1
Hi,

Host OS: Windows 7 Ultimate x64 on SSD system disk.
PC Specs: Intel Core i7 3770K on ASRock Z77 OC Formula with 16GB DDR3, GTX470
VirtualBox version: 4.3.12 r93733 with Extension Pack 4.3.12 r93733.

I've had a Windows 8.1 Pro x64 VM running on VBox 4.3 for a few days now with no issues at all.


However, this morning, the VM refused to boot saying VT-x was not enabled.

I checked via the VM settings but the whole "Acceleration" pane was disabled and not accessible. I was not able to resolve the issue even after rebooting my PC and explicitly enabling Intel Virtualization in the PC BIOS (it was on AUTO before - I set it to ENABLE).

I have since several times removed the VM completely and attempted to reinstall.

Every time, the VM hangs on the Windows 8 logo screen on install and then crashes with the Error 0x000000C4.

As found on VirtualBox community forums and on other sites, I have tried the SETEXTRADATA command via command prompt running as administrator, and have confirmed that the .vbox file has been changed and the string ExtraDataItem name="VBoxInternal/CPUM/CMPXCHG16B" value="1"
appended in the <ExtraData> section.

However the VM still refuses to boot or reinstall. I have Ubuntu, Fedora and ZorinOS VM's all working perfectly.

The only change to my system that took place in the interim was that I installed Comodo Free Firewall last night. Seeing the problems I have been having with the VM since this morning, I uninstalled Comodo and rebooted thinking it might have something to do with my problems, but still no joy.

I am also uploading my .VBOX files before and after to show the changes that have been made by the SETEXTRADATA command.
 

Attachments

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Self-built
    CPU
    Intel Core i7 8700K
    Motherboard
    Asus Maximus X Code
    Memory
    G.Skill TridentZ RGB DDR4-4000 F4-4000C18D-16GTZR (8GBx2)
    Graphics Card(s)
    Asus STRIX-GTX960-DC2OC-4GD5
    Sound Card
    Asus SupremeFX S1220
    Monitor(s) Displays
    Dell UP2716D
    Screen Resolution
    2560x1440
    Hard Drives
    Drive #1 - Samsung SSD 840 PRO Series (238 GB)
    Drive #2 - WDC WD2003FZEX-00SRLA0 (1863 GB)
    Drive #3 - WDC WD2003FZEX-00Z4SA0 (1863 GB)
    Drive #4 - NVMe Samsung SSD 970 (232 GB)
    PSU
    Coolermaster V1000
    Case
    Corsair Obsidian 450D
    Cooling
    Corsair H115i + 2x Corsair SP140 Red; Front case fans replaced with 2x Corsair AF140 Red LED
    Keyboard
    Logitech G213
    Mouse
    Logitech G102
    Internet Speed
    BSNL claims its 100Mbps FTTH
    Browser
    Maxthon 5
    Antivirus
    Avast Free

jimbo45

New Member
VIP Member
Guru
Hafnarfjörður IS

Posts
4,373
#2
Hi there

Maybe not the answer you want but I've over a long period always found VMWARE more reliable and certain when installing and running VM's - You can convert existing VM's to vmware format simply. VMWARE PLAYER is free -- don't forget after powering up a VM for the first time after installing it to install VMWARE TOOLS (like VBOX additions).

I've no problem with running W8.1 as a VM -- I'm running W8.1 x-64 enterprise on an HP laptop - no probs.

I've also used VMWARE on a LINUX HOST and run Windows 8.1 enterprise x-64 as a GUEST too with no probs including 3-D and hardware acceleration -- in fact that's what I'm doing right now - although I'm actually posting the reply from the Linux Host (Konqueror browser). I'm using Ms Office on the Windows 8.1 VM.

Just as an afterthought though -- Have you INITIALIZED a DIsk (from the VM) before you try and install Windows -- with VMWARE the Wizard (create new Virtual machine) does it easily, but manually you might need to create aome HDD space and initialize it before Windows will boot the install media and run.

Cheers
jimbo
 

Attachments

My Computer

System One

  • OS
    Linux Centos 7, W8.1, W7, W2K3 Server W10
    Computer type
    PC/Desktop
    Monitor(s) Displays
    1 X LG 40 inch TV
    Hard Drives
    SSD's * 3 (Samsung 840 series) 250 GB
    2 X 3 TB sata
    5 X 1 TB sata
    Internet Speed
    0.12 GB/s (120Mb/s)

pillainp

New Member
Posts
5
#3
I've just given VMWare a try as well, after becoming frustrated with this issue on VBox.

Sadly, however, the same 0x000000c4 error pops ups when trying to create a VM in VMWare Workstation as well.

The error pops up in both VBox and VMWare whether I try to install from an ISO or from a DVD to which I wrote the Windows image (which by the way has been verified by hash check as having no errors).

This leads me to suspect there may be something wrong elsewhere than just in the virtualisation software. Maybe Avast Free had an update that is causing the issue?
 

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Self-built
    CPU
    Intel Core i7 8700K
    Motherboard
    Asus Maximus X Code
    Memory
    G.Skill TridentZ RGB DDR4-4000 F4-4000C18D-16GTZR (8GBx2)
    Graphics Card(s)
    Asus STRIX-GTX960-DC2OC-4GD5
    Sound Card
    Asus SupremeFX S1220
    Monitor(s) Displays
    Dell UP2716D
    Screen Resolution
    2560x1440
    Hard Drives
    Drive #1 - Samsung SSD 840 PRO Series (238 GB)
    Drive #2 - WDC WD2003FZEX-00SRLA0 (1863 GB)
    Drive #3 - WDC WD2003FZEX-00Z4SA0 (1863 GB)
    Drive #4 - NVMe Samsung SSD 970 (232 GB)
    PSU
    Coolermaster V1000
    Case
    Corsair Obsidian 450D
    Cooling
    Corsair H115i + 2x Corsair SP140 Red; Front case fans replaced with 2x Corsair AF140 Red LED
    Keyboard
    Logitech G213
    Mouse
    Logitech G102
    Internet Speed
    BSNL claims its 100Mbps FTTH
    Browser
    Maxthon 5
    Antivirus
    Avast Free

jimbo45

New Member
VIP Member
Guru
Hafnarfjörður IS

Posts
4,373
#4
Hi there

Try this with vmware

1) uninstall avast from the HOST temporarily) -- shouldn't really make any difference but who knows.
2) Start vmware
3) Create Virtual Machine -- follow on screen prmpts and ensure that you have full access to the disk space where you will create the VM's HDD's. For example if on the host you have a directory Virtual_machines - ensure you have full READ / WRITE access to it (and CREATE if Linux Host).
4) After creating the Virtual HDD - set the Virtual machine in the Virtual BIOS to boot from ISO file or physical DVD.
5) Boot up in Recovery mode
6) Type in the following commands (dos / cmd mode)
DISKPART
SELECT DISK 0
CREATE PARTITION PRIMARY
FORMAT FS=NTFS QUICK
ACTIVE <======== set that or system won't boot and in some cases won't even install.

Now exit and do your Guest install.

Note -- Your Install might be the UEFI one -- you CAN set the UEFI ON in the Virtual BIOS even if your Physical machine doesn't have it -- you need to fiddle around with the .VMX configuration file -- I can't remember where it is but GOOGLE should help you out. AHCPI or similar might be hosing you up as well. I've never had problems with EITHER of these issues on a UEFI enabled laptop, Running Bog standard non UEFI Guest.

Cheers
jimbo
 

My Computer

System One

  • OS
    Linux Centos 7, W8.1, W7, W2K3 Server W10
    Computer type
    PC/Desktop
    Monitor(s) Displays
    1 X LG 40 inch TV
    Hard Drives
    SSD's * 3 (Samsung 840 series) 250 GB
    2 X 3 TB sata
    5 X 1 TB sata
    Internet Speed
    0.12 GB/s (120Mb/s)

pillainp

New Member
Posts
5
#5
Hi,
Thanks for the prompt advice and help.

Followed your instructions and still had the same issue. Windows refuses to boot with the same 0x000000c4 error message.

Additionally I updated VirtualBox to the latest test version 4.3.15 (purely to test it) and the issue still persists.

Curiously, the issue only affects Windows 8.1 on VMWare. Linux runs fine -- I have Fedora 19 x64 running perfectly.

VirtualBox in versions 4.3.14 and 4.3.15 refuses to run either Linux or Windows 8.1 with the error messages below:

Windows 8.1 VM:
Failed to open a session for the virtual machine WIN81x64Pro.
The virtual machine 'WIN81x64Pro' has terminated unexpectedly during startup with exit code 1.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

Fedora Linux 19 VM:
Failed to open a session for the virtual machine Fedora 19.
The virtual machine 'Fedora 19' has terminated unexpectedly during startup with exit code 1.
Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}
 

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Self-built
    CPU
    Intel Core i7 8700K
    Motherboard
    Asus Maximus X Code
    Memory
    G.Skill TridentZ RGB DDR4-4000 F4-4000C18D-16GTZR (8GBx2)
    Graphics Card(s)
    Asus STRIX-GTX960-DC2OC-4GD5
    Sound Card
    Asus SupremeFX S1220
    Monitor(s) Displays
    Dell UP2716D
    Screen Resolution
    2560x1440
    Hard Drives
    Drive #1 - Samsung SSD 840 PRO Series (238 GB)
    Drive #2 - WDC WD2003FZEX-00SRLA0 (1863 GB)
    Drive #3 - WDC WD2003FZEX-00Z4SA0 (1863 GB)
    Drive #4 - NVMe Samsung SSD 970 (232 GB)
    PSU
    Coolermaster V1000
    Case
    Corsair Obsidian 450D
    Cooling
    Corsair H115i + 2x Corsair SP140 Red; Front case fans replaced with 2x Corsair AF140 Red LED
    Keyboard
    Logitech G213
    Mouse
    Logitech G102
    Internet Speed
    BSNL claims its 100Mbps FTTH
    Browser
    Maxthon 5
    Antivirus
    Avast Free

jimbo45

New Member
VIP Member
Guru
Hafnarfjörður IS

Posts
4,373
#6
Hi there.

I can then only surmise that either your HOST system is defective or the Windows version you are trying to install is not a legit version - copied from a torrent perhaps.

Almost NOBODY will have problems installing Windows as a VM from a proper legit ISO. Perhaps re-installing the HOST OS and trying again should work.

Cheers
jimbo
 

My Computer

System One

  • OS
    Linux Centos 7, W8.1, W7, W2K3 Server W10
    Computer type
    PC/Desktop
    Monitor(s) Displays
    1 X LG 40 inch TV
    Hard Drives
    SSD's * 3 (Samsung 840 series) 250 GB
    2 X 3 TB sata
    5 X 1 TB sata
    Internet Speed
    0.12 GB/s (120Mb/s)

pillainp

New Member
Posts
5
#7
The ISO is a legitimate MSDN ISO. I think something may have changed on the Host OS that I cannot figure out.

Also there is a discussion regarding this problem on the VirtualBox forums.
 

My Computer

System One

  • OS
    Windows 10 Pro x64
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Self-built
    CPU
    Intel Core i7 8700K
    Motherboard
    Asus Maximus X Code
    Memory
    G.Skill TridentZ RGB DDR4-4000 F4-4000C18D-16GTZR (8GBx2)
    Graphics Card(s)
    Asus STRIX-GTX960-DC2OC-4GD5
    Sound Card
    Asus SupremeFX S1220
    Monitor(s) Displays
    Dell UP2716D
    Screen Resolution
    2560x1440
    Hard Drives
    Drive #1 - Samsung SSD 840 PRO Series (238 GB)
    Drive #2 - WDC WD2003FZEX-00SRLA0 (1863 GB)
    Drive #3 - WDC WD2003FZEX-00Z4SA0 (1863 GB)
    Drive #4 - NVMe Samsung SSD 970 (232 GB)
    PSU
    Coolermaster V1000
    Case
    Corsair Obsidian 450D
    Cooling
    Corsair H115i + 2x Corsair SP140 Red; Front case fans replaced with 2x Corsair AF140 Red LED
    Keyboard
    Logitech G213
    Mouse
    Logitech G102
    Internet Speed
    BSNL claims its 100Mbps FTTH
    Browser
    Maxthon 5
    Antivirus
    Avast Free

Hopachi

Polyhedric Stellation
VIP Member
Pro User
Orbiting the Moon

Posts
2,975
#8
The ISO is a legitimate MSDN ISO. I think something may have changed on the Host OS that I cannot figure out.

Also there is a discussion regarding this problem on the VirtualBox forums.
Strange that VMware Player gives the same error...

Did you managed to get Vt-x working yet?
I hope you don't have Hyper-V installed on the host since it will disable Vt-x for other hypervisors.
Usually BIOS updates reset the VT-x counter too.
I can't think what other programs do that as well...

Check windows features to make sure of Hyper-V is off, use sys restore to a time when all worked (if possible).
This might not be it but one way or another, if your cpu is capable, the Vt-x should get reported in VirtualBox and VMware Player.

Cheers,
Hopachi
 

My Computer

System One

  • OS
    Windows 10 x64
    Computer type
    Laptop
    System Manufacturer/Model
    HP Envy DV6 7250
    CPU
    Intel i7-3630QM
    Motherboard
    HP, Intel HM77 Express Chipset
    Memory
    16GB
    Graphics Card(s)
    Intel HD4000 + Nvidia Geforce 630M
    Sound Card
    IDT HD Audio
    Monitor(s) Displays
    15.6' built-in + Samsung S22D300 + 17.3' LG Phillips
    Screen Resolution
    multiple resolutions
    Hard Drives
    Samsung SSD 250GB + Hitachi HDD 750GB
    PSU
    120W adapter
    Case
    small
    Cooling
    laptop cooling pad
    Keyboard
    Backlit built-in + big one in USB
    Mouse
    SteelSeries Sensei
    Internet Speed
    slow and steady
    Browser
    Chromium, Pale Moon, Firefox Developer Edition
    Antivirus
    Windows Defender
    Other Info
    That's basically it.
Posts
1
#9
've just given VMWare a try as well, after becoming frustrated with this issue on VBox.

Sadly, however, the same 0x000000c4 error pops ups when trying to create a VM in VMWare Workstation as well.

The error pops up in both VBox and VMWare whether I try to install from an ISO or from a DVD to which I wrote the Windows image (which by the way has been verified by hash check as having no errors).

Could this be caused by the antivirus or firewall settings
 

My Computer

System One

  • OS
    Windows 8.1

Users Who Are Viewing This Thread (Users: 0, Guests: 1)