Opened 2 years ago
Closed 2 years ago
#21031 closed defect (worksforme)
After upgrade to 6.1.36 on Windows 10, can't launch RHEL guest
Reported by: | Clowers | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 6.1.36 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description
I upgraded VB on my Windows 10 host to release 6.1.36, and now when I try to launch my RHEL guest, there is an error, and the guest won't run. The host is running Windows 10 Version 21H2 (OS Build 19044.1826) on a Dell XPS 8930 tower. The error message that is copied to the clipboard when I click "Copy" on the window that comes up when it fails, is: ===== Failed to open a session for the virtual machine RHEL first. The virtual machine 'RHEL first' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\paulc\VirtualBox VMs\RHEL first\Logs\VBoxHardening.log'. Result Code: E_FAIL (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} ===== The file VBoxHardening.log suggests to run a command, the output of that command is:
C:\Users\paulc\VirtualBox VMs\RHEL first\Logs>sc.exe query vboxdrv [SC] EnumQueryServicesStatus:OpenService FAILED 1060:
The specified service does not exist as an installed service.
I don't see a way to attach files to this web interface, I'll see if I can attach them after posting
Attachments (6)
Change History (10)
by , 2 years ago
Attachment: | VBoxHardening.log added |
---|
comment:3 by , 2 years ago
Most probably (*) Can't launch VM after upgrading to VB 6.1.36.
(*) The VBoxHardening.log files are from different runs, but the paths from which the "wrong" sc.exe command was executed were identical. ;)
comment:4 by , 2 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Log file