Whenever i try to create or import a machine, i get the error below.
Failed to open a session for the virtual machine windows.
The virtual machine 'windows' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Hs\VirtualBox VMs\windows\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
I tried to turn off the windows hyper v features but still the error persists.
i have attatched VM logs files
Virtual Box can not start session for windows machine
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box can not start session for windows machine
Looks like the log did not attach. Please zip the logs then post the zip using the forum's Upload Attachment tab.
Re: Virtual Box can not start session for windows machine
Here is the log file
- Attachments
-
- VBoxHardening.rar
- (11.7 KiB) Downloaded 11 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Virtual Box can not start session for windows machine
The hardening file doesn't like 'opengl32.dll (which I am not sure if it comes from Microsoft or your video drivers):
And though the log does not report any 3rd-party AV installed, there is an AVG file left active that may be interfering:920.964: Error (rc=0):
920.964: supR3HardenedScreenImage/NtCreateSection: cached rc=Unknown Status -22900 (0xffffa68c) fImage=1 fProtect=0x10 fAccess=0xd cHits=3 \Device\HarddiskVolume3\Windows\System32\opengl32.dll
Finally, something is hacking Windows' vital file ntdll.dll:1738.2320: *00007ff91b8a0000-00007ff91b8a0fff 0x0002/0x0080 0x1000000 \Device\HarddiskVolume3\Program Files\AVG\Antivirus\aswhook.dll
Diagnosing VirtualBox Hardening Issues, posts 3 & 4 apply to exit code 1. Look for and purge any web-safe-browsing software, 3rd-party AV (but do let built-in MS Windows Defender run by itself as a test)."1738.2320: ntdll.dll: Differences in section #1 (.text) between file and memory: