Virtual box crashes on Windows host.
-
- Volunteer
- Posts: 835
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: Virtual box crashes on Windows host.
Yes, of course
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Virtual box crashes on Windows host.
@multiOS:
Sorry. I felt that I had to correct you, to keep the OP from an unnecessary search for Fast Startup. But you can see it positively: You made me explain the reasoning for the Shift key to be held, for the benefit of future readers.
Sorry. I felt that I had to correct you, to keep the OP from an unnecessary search for Fast Startup. But you can see it positively: You made me explain the reasoning for the Shift key to be held, for the benefit of future readers.
Re: Virtual box crashes on Windows host.
This problem persists.
This article pretty much says it is not going to work since my Build in not 1803: https://us.informatiweb.net/tutorials/i ... -time.html
My only options are if I'm happy with slow or go VMWare or HyperV
This article pretty much says it is not going to work since my Build in not 1803: https://us.informatiweb.net/tutorials/i ... -time.html
Code: Select all
I can see the hypervisorlaunchtype is Off.
C:\WINDOWS\system32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
badmemoryaccess Yes
isolatedcontext Yes
default {current}
resumeobject {83b8373f-303d-11eb-a16c-9cebe8e94e61}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {83b83741-303d-11eb-a16c-9cebe8e94e61}
displaymessageoverride Recovery
recoveryenabled Yes
badmemoryaccess Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {83b8373f-303d-11eb-a16c-9cebe8e94e61}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Off
claimedtpmcounter 0x10002
but Sysinfo tells me it detects a HyperViser (even when I uninstall VirtualBox).
C:\WINDOWS\system32>systeminfo.exe
Host Name: AUD-DSXCQ13
OS Name: Microsoft Windows 10 Enterprise
OS Version: 10.0.18363 N/A Build 18363
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Workstation
OS Build Type: Multiprocessor Free
Registered Owner: NTT Ltd
Registered Organization: NTT Ltd
Product ID: 00330-80000-00000-AA534
Original Install Date: 27/11/2020, 10:30:15 AM
System Boot Time: 3/04/2021, 12:58:32 PM
System Manufacturer: Dell Inc.
System Model: Latitude 7400
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 142 Stepping 12 GenuineIntel ~1910 Mhz
BIOS Version: Dell Inc. 1.6.1, 14/11/2019
Windows Directory: C:\WINDOWS
System Directory: C:\WINDOWS\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-au;English (Australia)
Input Locale: en-us;English (United States)
Time Zone: (UTC+10:00) Canberra, Melbourne, Sydney
Total Physical Memory: 32,579 MB
Available Physical Memory: 18,605 MB
Virtual Memory: Max Size: 37,443 MB
Virtual Memory: Available: 20,396 MB
Virtual Memory: In Use: 17,047 MB
Page File Location(s): C:\pagefile.sys
Domain: au.didata.local
Logon Server: \\AUMELSVPDC01
Hotfix(s): 15 Hotfix(s) Installed.
[01]: KB4601056
[02]: KB4497165
[03]: KB4517245
[04]: KB4535680
[05]: KB4561600
[06]: KB4569073
[07]: KB4576751
[08]: KB4577586
[09]: KB4580325
[10]: KB4584642
[11]: KB4586863
[12]: KB4589211
[13]: KB4601395
[14]: KB5000908
[15]: KB5000808
Network Card(s): 3 NIC(s) Installed.
[01]: Intel(R) Wireless-AC 9560 160MHz
Connection Name: Wi-Fi
DHCP Enabled: Yes
DHCP Server: 192.168.0.1
IP address(es)
[01]: 192.168.0.54
[02]: fe80::3951:3682:c64e:70c
[02]: Bluetooth Device (Personal Area Network)
Connection Name: Bluetooth Network Connection
Status: Media disconnected
[03]: Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64
Connection Name: Ethernet 2
Status: Hardware not present
Hyper-V Requirements: A hypervisor has been detected. Features required for Hyper-V will not be displayed.
C:\WINDOWS\system32>
Last edited by mpack on 4. Apr 2021, 11:23, edited 1 time in total.
Reason: Add code brackets for readability.
Reason: Add code brackets for readability.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Virtual box crashes on Windows host.
The correct solution has already been given, repeating the question will not change that. I don't really have the time to parse third party articles.
I can assure you that VMWare's requirements will be no different. As to Hyper-v, by all means try it, perhaps it will suit you.
I can assure you that VMWare's requirements will be no different. As to Hyper-v, by all means try it, perhaps it will suit you.