6.0.2 win host = E_FAIL (0x80004005) + MachineWrap

[zeon66]

Hi,
I've just updated my VB 5.2.22 to 6.0.2 (windows 10 host)
For some reason, I cannot start anymore my (LINUX guest ARCH 64) virtual machine anymore :
HELP!

Failed to open a session for the virtual machine Linux 64.

The virtual machine 'Linux 64' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005). More details may be available in 'C:\Users\nameuser\VirtualBox VMs\Linux 64\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {5047460a-265d-4538-b23e-ddba5fb84976}

Code: Select all

2e4.2038: Log file opened: 6.0.2r128162 g_hStartupLog=000000000000006c g_uNtVerCombined=0xa042ee00
2e4.2038: \SystemRoot\System32\ntdll.dll:
2e4.2038:     CreationTime:    2018-12-20T07:37:37.066884800Z
2e4.2038:     LastWriteTime:   2018-12-08T08:04:53.786979100Z
2e4.2038:     ChangeTime:      2018-12-20T07:41:07.000537500Z
2e4.2038:     FileAttributes:  0x20
2e4.2038:     Size:            0x1da720
2e4.2038:     NT Headers:      0xe8
2e4.2038:     Timestamp:       0x7e614c22
2e4.2038:     Machine:         0x8664 - amd64
2e4.2038:     Timestamp:       0x7e614c22
2e4.2038:     Image Version:   10.0
2e4.2038:     SizeOfImage:     0x1e1000 (1970176)
2e4.2038:     Resource Dir:    0x174000 LB 0x6b3e8
2e4.2038:     [Version info resource found at 0xd8! (ID/Name: 0x1; SubID/SubName: 0x409)]
2e4.2038:     [Raw version resource data: 0x1740f0 LB 0x380, codepage 0x0 (reserved 0x0)]
2e4.2038:     ProductName:     Microsoft® Windows® Operating System
2e4.2038:     ProductVersion:  10.0.17134.471
2e4.2038:     FileVersion:     10.0.17134.471 (WinBuild.160101.0800)
2e4.2038:     FileDescription: NT Layer DLL
2e4.2038: \SystemRoot\System32\kernel32.dll:
2e4.2038:     CreationTime:    2018-04-11T23:34:40.510607900Z
2e4.2038:     LastWriteTime:   2018-04-11T23:34:40.510607900Z
2e4.2038:     ChangeTime:      2018-05-06T17:38:51.124954500Z
2e4.2038:     FileAttributes:  0x20
2e4.2038:     Size:            0xafef8
2e4.2038:     NT Headers:      0xe8
2e4.2038:     Timestamp:       0x5f488a51
2e4.2038:     Machine:         0x8664 - amd64
2e4.2038:     Timestamp:       0x5f488a51
2e4.2038:     Image Version:   10.0
2e4.2038:     SizeOfImage:     0xb2000 (729088)
2e4.2038:     Resource Dir:    0xb0000 LB 0x520
2e4.2038:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2e4.2038:     [Raw version resource data: 0xb00b0 LB 0x3a4, codepage 0x0 (reserved 0x0)]
2e4.2038:     ProductName:     Microsoft® Windows® Operating System
2e4.2038:     ProductVersion:  10.0.17134.1
2e4.2038:     FileVersion:     10.0.17134.1 (WinBuild.160101.0800)
2e4.2038:     FileDescription: Windows NT BASE API Client DLL
2e4.2038: \SystemRoot\System32\KernelBase.dll:
2e4.2038:     CreationTime:    2018-12-01T19:36:42.228381300Z
2e4.2038:     LastWriteTime:   2018-11-09T02:47:52.285920600Z
2e4.2038:     ChangeTime:      2018-12-20T07:38:42.067478600Z
2e4.2038:     FileAttributes:  0x20
2e4.2038:     Size:            0x273b78
2e4.2038:     NT Headers:      0xf0
2e4.2038:     Timestamp:       0x428de48c
2e4.2038:     Machine:         0x8664 - amd64
2e4.2038:     Timestamp:       0x428de48c
2e4.2038:     Image Version:   10.0
2e4.2038:     SizeOfImage:     0x273000 (2568192)
2e4.2038:     Resource Dir:    0x251000 LB 0x548
2e4.2038:     [Version info resource found at 0x90! (ID/Name: 0x1; SubID/SubName: 0x409)]
2e4.2038:     [Raw version resource data: 0x2510b0 LB 0x3bc, codepage 0x0 (reserved 0x0)]
2e4.2038:     ProductName:     Microsoft® Windows® Operating System
2e4.2038:     ProductVersion:  10.0.17134.441
2e4.2038:     FileVersion:     10.0.17134.441 (WinBuild.160101.0800)
2e4.2038:     FileDescription: Windows NT BASE API Client DLL
2e4.2038: \SystemRoot\System32\apisetschema.dll:
2e4.2038:     CreationTime:    2018-04-11T23:34:44.042150700Z
2e4.2038:     LastWriteTime:   2018-04-11T23:34:44.042150700Z
2e4.2038:     ChangeTime:      2018-05-06T17:22:45.217725300Z
2e4.2038:     FileAttributes:  0x20
2e4.2038:     Size:            0x1bd98
2e4.2038:     NT Headers:      0xd0
2e4.2038:     Timestamp:       0xd02ff418
2e4.2038:     Machine:         0x8664 - amd64
2e4.2038:     Timestamp:       0xd02ff418
2e4.2038:     Image Version:   10.0
2e4.2038:     SizeOfImage:     0x1c000 (114688)
2e4.2038:     Resource Dir:    0x1b000 LB 0x408
2e4.2038:     [Version info resource found at 0x48! (ID/Name: 0x1; SubID/SubName: 0x409)]
2e4.2038:     [Raw version resource data: 0x1b060 LB 0x3a8, codepage 0x0 (reserved 0x0)]
2e4.2038:     ProductName:     Microsoft® Windows® Operating System
2e4.2038:     ProductVersion:  10.0.17134.1
2e4.2038:     FileVersion:     10.0.17134.1 (WinBuild.160101.0800)
2e4.2038:     FileDescription: ApiSet Schema DLL
2e4.2038: NtOpenDirectoryObject failed on \Driver: 0xc0000022
2e4.2038: supR3HardenedWinFindAdversaries: 0x0
2e4.2038: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume7\ut\VirtualBox'
2e4.2038: Calling main()
2e4.2038: SUPR3HardenedMain: pszProgName=VirtualBoxVM fFlags=0x2
2e4.2038: supR3HardenedWinInitAppBin(0x2): '\Device\HarddiskVolume7\ut\VirtualBox'
2e4.2038: SUPR3HardenedMain: Respawn #1
2e4.2038: System32:  \Device\HarddiskVolume7\Windows\System32
2e4.2038: WinSxS:    \Device\HarddiskVolume7\Windows\WinSxS
2e4.2038: KnownDllPath: C:\WINDOWS\System32
2e4.2038: '\Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe' has no imports
2e4.2038: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe)
2e4.2038: supR3HardNtEnableThreadCreation:
2e4.2038: supR3HardNtDisableThreadCreation: pvLdrInitThunk=00007ffd52d04f90 pvNtTerminateThread=00007ffd52d2b3f0
2e4.2038: supR3HardenedWinDoReSpawn(1): New child 23f4.2130 [kernel32].
2e4.2038: supR3HardNtChildGatherData: PebBaseAddress=0000000000b53000 cbPeb=0x388
2e4.2038: supR3HardNtPuChFindNtdll: uNtDllParentAddr=00007ffd52c90000 uNtDllChildAddr=00007ffd52c90000
2e4.2038: supR3HardenedWinSetupChildInit: uLdrInitThunk=00007ffd52d04f90
2e4.2038: supR3HardenedWinSetupChildInit: Start child.
2e4.2038: supR3HardNtChildWaitFor: Found expected request 0 (PurifyChildAndCloseHandles) after 0 ms.
2e4.2038: supR3HardNtChildPurify: Startup delay kludge #1/0: 262 ms, 22 sleeps
2e4.2038: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
2e4.2038:  *0000000000000000-00000000009effff 0x0001/0x0000 0x0000000
2e4.2038:  *00000000009f0000-00000000009f3fff 0x0002/0x0002 0x0040000
2e4.2038:   00000000009f4000-00000000009fffff 0x0001/0x0000 0x0000000
2e4.2038:  *0000000000a00000-0000000000b52fff 0x0000/0x0004 0x0020000
2e4.2038:   0000000000b53000-0000000000b55fff 0x0004/0x0004 0x0020000
2e4.2038:   0000000000b56000-0000000000bfffff 0x0000/0x0004 0x0020000
2e4.2038:  *0000000000c00000-0000000000c1ffff 0x0004/0x0004 0x0020000
2e4.2038:  *0000000000c20000-0000000000c38fff 0x0002/0x0002 0x0040000
2e4.2038:   0000000000c39000-0000000000c3ffff 0x0001/0x0000 0x0000000
2e4.2038:  *0000000000c40000-0000000000d3afff 0x0000/0x0004 0x0020000
2e4.2038:   0000000000d3b000-0000000000d3dfff 0x0104/0x0004 0x0020000
2e4.2038:   0000000000d3e000-0000000000d3ffff 0x0004/0x0004 0x0020000
2e4.2038:  *0000000000d40000-0000000000d40fff 0x0004/0x0004 0x0020000
2e4.2038:   0000000000d41000-0000000000d4ffff 0x0001/0x0000 0x0000000
2e4.2038:  *0000000000d50000-0000000000d60fff 0x0040/0x0040 0x0020000 !!
2e4.2038: supHardNtVpFreeOrReplacePrivateExecMemory: Freeing exec mem at 0000000000d50000 (LB 0x11000, 0000000000d50000 LB 0x11000)
2e4.2038: supHardNtVpFreeOrReplacePrivateExecMemory: Free attempt #1 succeeded: 0x0 [0000000000d50000/0000000000d50000 LB 0/0x11000]
2e4.2038: supHardNtVpFreeOrReplacePrivateExecMemory: QVM after free 0: [0000000000000000]/0000000000d50000 LB 0x7f290000 s=0x10000 ap=0x0 rp=0x42342d4600000001
2e4.2038:   0000000000d61000-000000007ffdffff 0x0001/0x0000 0x0000000
2e4.2038:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
2e4.2038:   000000007ffe1000-00007ff5722fffff 0x0001/0x0000 0x0000000
2e4.2038:  *00007ff572300000-00007ff572322fff 0x0002/0x0002 0x0040000
2e4.2038:   00007ff572323000-00007ff72805ffff 0x0001/0x0000 0x0000000
2e4.2038:  *00007ff728060000-00007ff728060fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728061000-00007ff7280d3fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff7280d4000-00007ff7280d4fff 0x0080/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff7280d5000-00007ff72811bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff72811c000-00007ff72811cfff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff72811d000-00007ff72811dfff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff72811e000-00007ff728122fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728123000-00007ff728123fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728124000-00007ff728124fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728125000-00007ff728128fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728129000-00007ff728171fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728172000-00007ffd52c8ffff 0x0001/0x0000 0x0000000
2e4.2038:  *00007ffd52c90000-00007ffd52c90fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52c91000-00007ffd52d9ffff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52da0000-00007ffd52de5fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52de6000-00007ffd52df0fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52df1000-00007ffd52dfefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52dff000-00007ffd52dfffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52e00000-00007ffd52e02fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52e03000-00007ffd52e70fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52e71000-00007ffffffeffff 0x0001/0x0000 0x0000000
2e4.2038: VirtualBoxVM.exe: timestamp 0x5c3ca16b (rc=VINF_SUCCESS)
2e4.2038: '\Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe' has no imports
2e4.2038: '\Device\HarddiskVolume7\Windows\System32\ntdll.dll' has no imports
2e4.2038: supR3HardNtChildPurify: cFixes=1 g_fSupAdversaries=0x80000000
2e4.2038: supR3HardNtChildPurify: Startup delay kludge #1/1: 518 ms, 62 sleeps
2e4.2038: supHardNtVpScanVirtualMemory: enmKind=CHILD_PURIFICATION
2e4.2038:  *0000000000000000-00000000009effff 0x0001/0x0000 0x0000000
2e4.2038:  *00000000009f0000-00000000009f3fff 0x0002/0x0002 0x0040000
2e4.2038:   00000000009f4000-00000000009fffff 0x0001/0x0000 0x0000000
2e4.2038:  *0000000000a00000-0000000000b52fff 0x0000/0x0004 0x0020000
2e4.2038:   0000000000b53000-0000000000b55fff 0x0004/0x0004 0x0020000
2e4.2038:   0000000000b56000-0000000000bfffff 0x0000/0x0004 0x0020000
2e4.2038:  *0000000000c00000-0000000000c1ffff 0x0004/0x0004 0x0020000
2e4.2038:  *0000000000c20000-0000000000c38fff 0x0002/0x0002 0x0040000
2e4.2038:   0000000000c39000-0000000000c3ffff 0x0001/0x0000 0x0000000
2e4.2038:  *0000000000c40000-0000000000d3afff 0x0000/0x0004 0x0020000
2e4.2038:   0000000000d3b000-0000000000d3dfff 0x0104/0x0004 0x0020000
2e4.2038:   0000000000d3e000-0000000000d3ffff 0x0004/0x0004 0x0020000
2e4.2038:  *0000000000d40000-0000000000d40fff 0x0004/0x0004 0x0020000
2e4.2038:   0000000000d41000-000000007ffdffff 0x0001/0x0000 0x0000000
2e4.2038:  *000000007ffe0000-000000007ffe0fff 0x0002/0x0002 0x0020000
2e4.2038:   000000007ffe1000-00007ff5722fffff 0x0001/0x0000 0x0000000
2e4.2038:  *00007ff572300000-00007ff572322fff 0x0002/0x0002 0x0040000
2e4.2038:   00007ff572323000-00007ff72805ffff 0x0001/0x0000 0x0000000
2e4.2038:  *00007ff728060000-00007ff728060fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728061000-00007ff7280d3fff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff7280d4000-00007ff7280d4fff 0x0040/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff7280d5000-00007ff72811bfff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff72811c000-00007ff728128fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728129000-00007ff728171fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038:   00007ff728172000-00007ffd52c8ffff 0x0001/0x0000 0x0000000
2e4.2038:  *00007ffd52c90000-00007ffd52c90fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52c91000-00007ffd52d9ffff 0x0020/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52da0000-00007ffd52de5fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52de6000-00007ffd52de9fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52dea000-00007ffd52df0fff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52df1000-00007ffd52dfefff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52dff000-00007ffd52dfffff 0x0004/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52e00000-00007ffd52e02fff 0x0008/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52e03000-00007ffd52e70fff 0x0002/0x0080 0x1000000  \Device\HarddiskVolume7\Windows\System32\ntdll.dll
2e4.2038:   00007ffd52e71000-00007ffffffeffff 0x0001/0x0000 0x0000000
2e4.2038: supR3HardNtChildPurify: Done after 810 ms and 1 fixes (loop #1).
23f4.2130: Log file opened: 6.0.2r128162 g_hStartupLog=0000000000000004 g_uNtVerCombined=0xa042ee00
23f4.2130: supR3HardenedVmProcessInit: uNtDllAddr=00007ffd52c90000 g_uNtVerCombined=0xa042ee00
2e4.2038: supR3HardNtEnableThreadCreation:
23f4.2130: ntdll.dll: timestamp 0x7e614c22 (rc=VINF_SUCCESS)
23f4.2130: New simple heap: #1 0000000000e50000 LB 0x400000 (for 1970176 allocation)
23f4.2130: supR3HardenedWinInitAppBin(0x0): '\Device\HarddiskVolume7\ut\VirtualBox'
23f4.2130: System32:  \Device\HarddiskVolume7\Windows\System32
23f4.2130: WinSxS:    \Device\HarddiskVolume7\Windows\WinSxS
23f4.2130: KnownDllPath: C:\WINDOWS\System32
23f4.2130: supR3HardenedVmProcessInit: Opening vboxdrv stub...
23f4.2130: supR3HardenedVmProcessInit: Restoring LdrInitializeThunk...
23f4.2130: supR3HardenedVmProcessInit: Returning to LdrInitializeThunk...
23f4.2130: Registered Dll notification callback with NTDLL.
23f4.2130: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume7\Windows\System32\kernel32.dll)
23f4.2130: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume7\Windows\System32\kernel32.dll
23f4.2130: supR3HardenedMonitor_LdrLoadDll: pName=C:\WINDOWS\System32\KERNEL32.DLL (Input=KERNEL32.DLL, rcNtResolve=0xc0150008) *pfFlags=0xffffffff pwszSearchPath=0000000000004001:<flags> [calling]
23f4.2130: supR3HardenedDllNotificationCallback: load   00007ffd4f930000 LB 0x00273000 C:\WINDOWS\System32\KERNELBASE.dll [fFlags=0x0]
23f4.2130: supHardenedWinVerifyImageByHandle: -> 0 (\Device\HarddiskVolume7\Windows\System32\KernelBase.dll)
23f4.2130: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume7\Windows\System32\KernelBase.dll
23f4.2130: supR3HardenedDllNotificationCallback: load   00007ffd50920000 LB 0x000b2000 C:\WINDOWS\System32\KERNEL32.DLL [fFlags=0x0]
23f4.2130: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume7\Windows\System32\kernel32.dll [lacks WinVerifyTrust]
23f4.2130: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ffd50920000 'C:\WINDOWS\System32\KERNEL32.DLL'
23f4.2130: supR3HardenedDllNotificationCallback: load   00007ff728060000 LB 0x00112000 c:\ut\VirtualBox\VirtualBoxVM.exe [fFlags=0x0]
23f4.2130: '\Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe' has no imports
23f4.2130: supHardenedWinVerifyImageByHandle: -> 24202 (\Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe)
23f4.2130: supR3HardenedWinVerifyCacheInsert: \Device\HarddiskVolume7\ut\VirtualBox\VirtualBoxVM.exe
2e4.2038: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 57 ms, CloseEvents);

[andyp73]

Please don't post great swathes of text from the log file in the body of a message. Zip the .log file and attach it instead as it makes it easier for people to process.

2e4.2038: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0xc0000005 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 57 ms, CloseEvents);

The hardening checks seem to have changed in v6.0.x but this shows that you do have a hardening issue. Have a read of Diagnosing VirtualBox Hardening Issues and follow the guidance it contains.

-Andy.

[zeon66]

Nice try but nothing worked.
YES I have carefully followed the recommendations of "Diagnosing VirtualBox Hardening Issues".

Now I'm back to 5.2.24 and guess what?
My 2 virtual machines guests are working again (Linux Arch 64 guest & Windows 10 64 guest)

Conclusion: The problem is 6.0.2

[mpack]

None of which contradicts the reply you got.

p.s. I deleted your cross post in "Windows Guests". It is obviously the same (host) problem and therefore did not need two topics to discuss it.

[andyp73]

Conclusion: The problem is 6.0.2

Not necessarily. v6.0.2 may be performing more checks and performing them more correctly than v5.2.24. It may be something else on your system that is causing the problem. Without the VBoxHardening.log and VBox.log files zipped together and posted properly so we can take a look we can't say.

-Andy.

[zeon66]

I have 2 virtual machines that work perfectly well with 5.2.24, one is a Linux ARCH 64 + latest online updates, the other one is a WIN10 PRO + latest online updates
If I upgrade to 6.0.2, they don't work anymore.
Then if I downgrade to 5.2.24, they work again.

The problem CLEARLY is 6.0.2, any idiot would have find this logic conclusion, no BS, thanks

[mpack]

Can you please point out where anyone has denied that 6.0.2 does things differently? Because I missed where that happened.

Differently does not mean wrongly. Obviously if new hardening checks are implemented then the whole point is to intercept more risks.

Finally, this is a user to user self help forum. We do not work for Oracle and anyway a free download does not make you an Oracle customer. If your tone is going to continue along the path of accusing helpers - who owe you nothing - of being idiots and talking BS then I'm afraid as moderator I will not tolerate that for long. So please try to be reasonable and consider what is suggested.

[socratis]

6.0.x tightened the security checks, that much is true. Anyone (idiot or not) could find out that, if they simply asked before jumping to hasty, inaccurate, speculative conclusions...

That said, a properly installed system has no problem with 6.0.2. Or three of them, like my Win* host. Or the tens of thousands of users running 6.0.x.

Moving this to "Windows Hosts", not a "Linux Guests" issue...

[zeon66]

You know what?
I think that virtual machines that were created with a version <= 5.2.4 have incompatibility problems with the version >= 6.0.
Oracle prefers to deny it and discredit the people who point it out (rather than finding a real solution) by forcing people to completely reinstall their OS into new virtual machines.
They don't care about all the time you spent customizing your previous virtual machines.
The most likely reason is that version >= 6.0 is very different from the previous ones in its design, just look at the size of the executable to realize it....
Too much work to make old virtual machines 100% compatible....

[mpack]

Oracle is not involved in this conversation. This is a user to user forum, as you have already been told.

[socratis]

Oracle prefers to deny it and discredit the people who point it out (rather than find a real solution) by encouraging them to completely reinstall their OS.

As mpack told you a couple of times, we're not Oracle, unless it says so on the right side of the reply. We (the other users) are not trying to discredit you, we're trying to educate you so that you can address your issue.

I'll make you a bet; install a fresh Win* supported host, and if you have a problem, I'll buy you the computer of your choice. If you lose, I prefer MacBookPros, fully loaded. How about it? As they say, "Put your money where your is!"...

As I said, I have 3 hosts running ≥ Win7. The Win7 one actually is from 2012 (VirtualBox 3.x to 4.x era) and has seen its share of updates, hardware changes, software installations. No problem... It's not the host OS, it's not the VirtualBox version, it's not the VM version...

The problem CLEARLY is zeon66's system, any idiot would have find this logic conclusion, no BS, thanks

[zeon66]

I'll make you a bet; install a fresh Win* supported host

Who said that installing a Windows 10 guest in 6.0.2 host doesn't work??? NOT ME.

That's not the point. Read again my previous message.

Thanks

[andyp73]

I think that virtual machines that were created with a version <= 5.2.4 have incompatibility problems with the version >= 6.0.

I have guests that were created under VirtualBox 4.something on a Windows XP host. They have followed me without problems through 5.x.x and now 6.0.x versions of VirtualBox, across host upgrades to Windows 7 and then 10 and now onto a macOS host.

If your host is stable and isn't throwing any harderning errors then guests just seem to keep on working.

-Andy

[zeon66]

AMEN

[AKR]

Here is the same problem.
viewtopic.php?f=6&t=91313&p=439397#p439397