win10 pro-64 bit problem

Discussions related to using VirtualBox on Windows hosts.
onlyzanna
Posts: 10
Joined: 12. Jun 2018, 12:18

Re: win10 pro-64 bit problem

Post by onlyzanna »

I attached the bug report. I hope that helps.
Attachments
2018-06-14-06-19-04-bugreport.tgz
(121.4 KiB) Downloaded 32 times
onlyzanna
Posts: 10
Joined: 12. Jun 2018, 12:18

Re: win10 pro-64 bit problem

Post by onlyzanna »

So, noone? Is there no way to use Virtualbox in this pc?
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: win10 pro-64 bit problem

Post by socratis »

SERVICE_NAME  : hvservice
DISPLAY_NAME  : Hypervisor/Virtual Machine Support Driver
        TYPE  : 1  KERNEL_DRIVER  
        STATE : 4  RUNNING 
                   (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
I believe it may be due to these two suspects:
SERVICE_NAME  : TPM
DISPLAY_NAME  : TPM
        TYPE  : 1  KERNEL_DRIVER  
        STATE : 4  RUNNING 
                   (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
SERVICE_NAME  : UEFI
DISPLAY_NAME  : Driver UEFI Microsoft
        TYPE  : 1  KERNEL_DRIVER  
        STATE : 4  RUNNING 
                   (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
onlyzanna
Posts: 10
Joined: 12. Jun 2018, 12:18

Re: win10 pro-64 bit problem

Post by onlyzanna »

Ok but I'm not sure that I can stop tpm or UEFI, isn't it?
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: win10 pro-64 bit problem

Post by socratis »

I honestly don't know, you got to do your own research.
I'm primarily on OSX, and my Win PC is way older than the invention of TPM... ;)
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
allsubs99
Posts: 1
Joined: 23. Jul 2018, 10:38

Re: win10 pro-64 bit problem

Post by allsubs99 »

I am also facing a similar issue. Despite disabling hyper-v, enabling virtualization in BIOS, I am still not able to install 64 bit OS in my Vbox. Until last week, it was working well i.e. I had installed a 64 bit Ubuntu in my VirtualBox and it was working well. Not sure what happened suddenly it has stopped working. Can someone please help?
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: win10 pro-64 bit problem

Post by mpack »

It's very simple. If your processor definitely supports VT-x (or AMD-v) but it isn't reaching VirtualBox, then that must be because something else is using it. Either it's being blocked by the host BIOS or else other software on your PC is already using it. We have no access to your PC, we can't tell you what the other software is - it's up to you to look and to apply some logic.

FAQ: I have a 64bit host, but can't install 64bit guests.
captainnemo
Posts: 1
Joined: 30. Jun 2018, 11:12

Re: win10 pro-64 bit problem

Post by captainnemo »

Hi guys,

I had the same issue.
I tried everything. Then I found the answer on WMware:


Disable the group policy setting that was used to enable Credential Guard.
On the host operating system, click Start > Run, type gpedit.msc, and click Ok. The Local group Policy Editor opens.
Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.
Select Disabled.

Go to Control Panel > Uninstall a Program > Turn Windows features on or off to turn off Hyper-V.
Select Do not restart.
Delete the related EFI variables by launching a command prompt on the host machine using an Administrator account and run these commands:

mountvol X: /s
copy %WINDIR%\System32\SecConfig.efi X:\EFI\Microsoft\Boot\SecConfig.efi /Y
bcdedit /create {0cb3b571-2f2e-4343-a879-d86a476d7215} /d "DebugTool" /application osloader
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} path "\EFI\Microsoft\Boot\SecConfig.efi"
bcdedit /set {bootmgr} bootsequence {0cb3b571-2f2e-4343-a879-d86a476d7215}
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} loadoptions DISABLE-LSA-ISO,DISABLE-VBS
bcdedit /set {0cb3b571-2f2e-4343-a879-d86a476d7215} device partition=X:
mountvol X: /d

Note: Ensure X is an unused drive, else change to another drive.

Restart the host.
Accept the prompt on the boot screen to disable Device Guard or Credential Guard.


I hope this help.
Post Reply