Virtualbox on Windows 10 without 64 bit guests
Virtualbox on Windows 10 without 64 bit guests
Hello,
I have following hardware/software configuration:
-Dell Precision 3520 with Intel E3-1505M v6 processor (on Intel site stays that this processor has VT support)
-Windows 10 64 bit
-Virtualbox 5.2.12
-Hyper-V in Windows Features is DISABLED
-Virtualization Technology in BIOS is ENABLED.
The problem is that there is no possibility to select 64 bit in virtualbox during creation of virtual machine.
I have following hardware/software configuration:
-Dell Precision 3520 with Intel E3-1505M v6 processor (on Intel site stays that this processor has VT support)
-Windows 10 64 bit
-Virtualbox 5.2.12
-Hyper-V in Windows Features is DISABLED
-Virtualization Technology in BIOS is ENABLED.
The problem is that there is no possibility to select 64 bit in virtualbox during creation of virtual machine.
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Virtualbox on Windows 10 without 64 bit guests
Have you checked the FAQ: I have a 64bit host, but can't install 64bit guests for guidance?
-Andy.
Depending which build of Windows 10 you have, disabling Hyper-V in Windows Features isn't enough. You also need to run the following commands in an elevated Command Prompt (right-click, Run-as-Administrator):ArturK wrote:Hyper-V in Windows Features is DISABLED
dism /Online /Disable-Feature:Microsoft-Hyper-V bcdedit /set hypervisorlaunchtype off
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Re: Virtualbox on Windows 10 without 64 bit guests
I run commands given by you as a administrator, then restart, reinstall virtualbox, restart.
After running Virtualbox, under Path c:\users\myusername\.VirtualBox following log file "VBOXSVC.log" is created with following content:
After running Virtualbox, under Path c:\users\myusername\.VirtualBox following log file "VBOXSVC.log" is created with following content:
Any other log files weren't created.Code: Select all
VirtualBox COM Server 5.2.12 r122591 win.amd64 (May 9 2018 10:42:46) release log 00:00:00.015574 main Log opened 2018-05-14T09:34:23.276090300Z 00:00:00.015574 main Build Type: release 00:00:00.015574 main OS Product: Windows 10 00:00:00.015574 main OS Release: 10.0.15063 00:00:00.015574 main OS Service Pack: 00:00:00.015574 main DMI Product Name: Precision 3520 00:00:00.031199 main DMI Product Version: 00:00:00.031199 main Host RAM: 16261MB (15.8GB) total, 11780MB (11.5GB) available 00:00:00.031199 main Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe 00:00:00.031199 main Process ID: 9924 00:00:00.031199 main Package type: WINDOWS_64BITS_GENERIC 00:00:00.031199 VirtualBox: object creation starts 00:00:00.031199 Home directory: 'C:\Users\USERNAME\.VirtualBox' 00:00:00.031199 Installed Drivers: 00:00:00.031199 C:\windows\system32\DRIVERS\VBoxNetLwf.sys (Version: 5.2.12.22591) 00:00:00.031199 C:\windows\system32\DRIVERS\VBoxUSBMon.sys (Version: 5.2.12.22591) 00:00:00.031199 C:\windows\system32\DRIVERS\VBoxDrv.sys (Version: 5.2.12.22591) 00:00:00.046824 Loading settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:00:00.078248 Getting USB descriptor failed with error 31 00:00:00.078248 Getting USB descriptor failed with error 31 00:00:00.093730 USB: Unknown USB device detected (idVendor: 0x0c45, idProduct: 0x6717) 00:00:00.093730 USB: Unknown USB device detected (idVendor: 0x8087, idProduct: 0x0a2b) 00:00:00.156281 HostDnsMonitor: old information 00:00:00.156281 no server entries 00:00:00.156281 no domain set 00:00:00.156281 no search string entries 00:00:00.156281 HostDnsMonitor: new information 00:00:00.156281 HostDnsMonitorProxy::notify 00:00:00.156281 VD: VDInit finished with VINF_SUCCESS 00:00:00.156281 VirtualBox: object created 00:00:22.510981 main VirtualBox: object deletion starts 00:00:22.510981 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0 00:00:22.510981 main VirtualBox: object deleted
Last edited by socratis on 14. May 2018, 15:09, edited 1 time in total.
Reason: Enclosed the information in [code] tag for better readability
Reason: Enclosed the information in [code] tag for better readability
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Virtualbox on Windows 10 without 64 bit guests
I'm not sure of the exact cause of this. A quick search of the internet brings up several possibilities including not having proper permissions accessing the registry key or remnants of a VMWare installation getting in the way. Someone more knowledgable may be past shortly and can advise but you are the only one sat in front of your computer so you will need to tell us if there are other things installed that might be of interest to us.ArturK wrote:00:00:22.510981 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0
These get created when you start a guest. Create a test virtual machine using the 32bit template of the operating system you want to install. Just boot it, wait for the "no boot media" message and power it off. The log files I asked for will be in the directory of the guest.ArturK wrote:Any other log files weren't created.
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Re: Virtualbox on Windows 10 without 64 bit guests
Starting VM fails, window with error message appears:
Logfile content:Code: Select all
Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT). Kod wyniku (RC): E_FAIL (0x80004005) Komponent: ConsoleWrap Interfejs: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Code: Select all
00:00:00.140680 HostDnsMonitorProxy::notify 00:00:00.140680 VD: VDInit finished with VINF_SUCCESS 00:00:00.140680 VirtualBox: object created 00:00:01.500032 Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:00:01.515637 Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:03:20.008940 Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:03:20.008940 Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:03:20.024561 Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:03:21.837304 Import settings with version "1.16-windows" 00:03:21.837304 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={Could not find a registered machine named 'GM1'}, preserve=false aResultDetail=0 00:03:21.837304 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Could not find file for the medium 'C:\Users\username\VirtualBox VMs\GM1\GM1-disk001.vmdk' (VERR_PATH_NOT_FOUND)}, preserve=false aResultDetail=0 00:05:50.980293 ApplImp Saving settings file "C:\Users\username\VirtualBox VMs\GM1\GM1.vbox" with version "1.16-windows" 00:05:50.994292 ApplImp Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:05:51.569830 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={MachineWrap} aText={This machine does not have any snapshots}, preserve=false aResultDetail=0 00:05:57.829638 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={edba9d10-45d8-b440-1712-46ac0c9bc4c5} aComponent={ExtPackManagerWrap} aText={No extension pack by the name 'Oracle VM VirtualBox Extension Pack' was found}, preserve=false aResultDetail=0 00:05:58.056220 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={85cd948e-a71f-4289-281e-0ca7ad48cd89} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0 00:05:58.760074 Saving settings file "C:\Users\username\VirtualBox VMs\GM1\GM1.vbox" with version "1.16-windows" 00:05:59.315950 Saving settings file "C:\Users\username\VirtualBox VMs\GM1\GM1.vbox" with version "1.16-windows" 00:08:03.457591 Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:08:03.473258 Saving settings file "C:\Users\username\.VirtualBox\VirtualBox.xml" with version "1.12-windows" 00:08:09.030729 main VirtualBox: object deletion starts 00:08:09.030729 main ERROR [COM]: aRC=VBOX_E_OBJECT_IN_USE (0x80bb000c) aIID={4afe423b-43e0-e9d0-82e8-ceb307940dda} aComponent={MediumWrap} aText={Medium 'C:\Users\username\VirtualBox VMs\GM1\GM1-disk001.vmdk' cannot be closed because it is still attached to 1 virtual machines}, preserve=false aResultDetail=0 00:08:09.030729 Watcher ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={9570b9d5-f1a1-448a-10c5-e12f5285adad} aComponent={VirtualBoxWrap} aText={The object is not ready}, preserve=false aResultDetail=0 00:08:09.030729 main VirtualBox: object deleted
Last edited by socratis on 14. May 2018, 15:11, edited 1 time in total.
Reason: Enclosed the information in [code] tag for better readability
Reason: Enclosed the information in [code] tag for better readability
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Virtualbox on Windows 10 without 64 bit guests
That isn't the log file that I asked you to post but...
-Andy.
This tells me that Hyper-V isn't disabled and that something else is using it. As far as Windows 10 is concerned, this could be DeviceGuard or CredentialGuard and there may be even more with the April 2018 release (Windows 10 v1803).ArturK wrote:Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
-
- Posts: 2
- Joined: 21. May 2018, 14:02
Re: Virtualbox on Windows 10 without 64 bit guests
Hi ...I am having the similar issue my 64 bit windows 10 is not able to detect the 64 bit option for Linux distribution. I have hyper V disables and there is no error log mentioning hyper V related error. Can someone help.
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Virtualbox on Windows 10 without 64 bit guests
You probably need to start by looking at I have a 64bit host, but can't install 64bit guests and treating it as guidance rather than a definitive set of instructions. There have been reports with the latest Windows 10 release (1803) that more things require Hyper-V even if you set it to disabled.QuakerCitizen wrote:Can someone help.
We will be able to give you a more definitive answer when we can see the VBox.log file from a guest. If needs be, create a guest using a 32bit template, start it up, wait for the "no boot media" message and then power it off. Post the log file (zipped of course).
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
-
- Posts: 2
- Joined: 21. May 2018, 14:02
Re: Virtualbox on Windows 10 without 64 bit guests
here is the log from the 32 bit host
[ pasted VBoxSVC log deleted. Post logs as zip attachments ].
[ pasted VBoxSVC log deleted. Post logs as zip attachments ].
Last edited by mpack on 22. May 2018, 14:47, edited 2 times in total.
Reason: Delete pasted log.
Reason: Delete pasted log.
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: Virtualbox on Windows 10 without 64 bit guests
Logs quoted verbatim into posts aren't great. It is better if they are zipped and added as an attachment.
That wasn't the log file I asked for. That is the VBoxSvc.log whereas I want the VBox.log for the guest in question. In the VirtualBox manager, right click on the guest and choose "Show log". Save only the first log file and post it here.
-Andy.
That wasn't the log file I asked for. That is the VBoxSvc.log whereas I want the VBox.log for the guest in question. In the VirtualBox manager, right click on the guest and choose "Show log". Save only the first log file and post it here.
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.