virtualbox.org

I'm struggling to fix this issue "Error relaunching VirtualBox VM process 5" with no luck. Any suggestions/pointers would be really helpful.

I am using HP Zbook w/Windows 10 OS and there is no external antivirus installed.

Attached the Hardening log for reference.

--Snip from the hardening log last few lines

1640.19f4: supR3HardenedScreenImage/LdrLoadDll: cache hit (Unknown Status 22900 (0x5974)) on \Device\HarddiskVolume3\Windows\System32\midimap.dll [lacks WinVerifyTrust]
1640.19f4: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\midimap.dll (Input=midimap.dll, rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000001001:<flags> [calling]
1640.19f4: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff8365d0000 'C:\windows\System32\midimap.dll'
1640.1a4c: supR3HardenedScreenImage/LdrLoadDll: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Windows\System32\MMDevAPI.dll [lacks WinVerifyTrust]
1640.1a4c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDevApi.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000002009:<flags> [calling]
1640.1a4c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff83fe30000 'C:\windows\System32\MMDevApi.dll'

Thanks!

The log doesn't seem to end in an exit code, a guest Virtualbox window might have been open still.

Go carefully through Diagnosing VirtualBox Hardening Issues, for ideas of what to look for.

Wb-searching:
Error relaunching VirtualBox VM process 5 site:forums.virtualbox.org
reveals that extra 'web-safe-browsing' nanny software may be installed. HP's Protect Tools & IBM Trusteer Rapport are two of the top offenders that up-end Virtualbox.

If you find and uninstall anything, reinstall Virtualbox by right-clicking the installer and choosing Run As Administrator, even if you already are an administrator.

Thanks Scott for checking...My bad, Attached is the hardening log with the exit code. I am reviewing the Diagnosing VirtualBox Hardening Issues you shared.

--< Last few lines from the log

357c.328c: supR3HardenedMonitor_LdrLoadDll: pName=C:\windows\System32\MMDevApi.dll (rcNtResolve=0xc0150008) *pfFlags=0x0 pwszSearchPath=0000000000002009:<flags> [calling]
357c.328c: supR3HardenedMonitor_LdrLoadDll: returns rcNt=0x0 hMod=00007ff954410000 'C:\windows\System32\MMDevApi.dll'
3e7c.1288: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 3693 ms, the end);

No proble, thanks for the exit code. '1' does indicate the possibility of nanny software, or an 'sfc /scannow', as shown in the Dignosing tutorial.

I tried the below and still the same.

windows defender firewall is turned off
No antivirus on the machine
Ran sfc/scannow in admin mode and it is clean.

• Microsoft Windows [Version 10.0.18363.997]
  (c) 2019 Microsoft Corporation. All rights reserved.
  
  C:\windows\system32>sfc /scannow
  
  Beginning system scan. This process will take some time.
  
  Beginning verification phase of system scan.
  Verification 100% complete.
  Windows Resource Protection did not find any integrity violations.
  
  C:\windows\system32>

VBoxHardening.log file wrote:

357c.3fd0: Error -104 in supR3HardenedWinReSpawn! (enmWhat=5)
357c.3fd0: Error relaunching VirtualBox VM process: 5
Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment RAC02 --startvm 31b3e957-86ff-414e-9a65-4371451dd1df --no-startvm-errormsgbox --sup-hardening-log=E:\RAC02\Logs\VBoxHardening.log'

This error is a typical consequence of having an adversary that VirtualBox detects but doesn't recognize. I'd suggest to look at the list of all installed software to recognize it by eye ...

I tired the below, no luck

• Uinstalled latest windows updates
  uninstalled a lot of software (No AV installed on my machine),
  turned off windows firewall,
  turned off windows protection.
  Uninstalled VM box, reinstalled, downgraded to n-1 version.

I am stuck and not sure what next...

--sofware installed on my machine, Is there something that can be cornered ?

wmic:root\cli>product get name,version
Name Version
Microsoft Office Lync Software Development Kit Runtime 15.0.4603.1000
Office 16 Click-to-Run Extensibility Component 16.0.13001.20144
Office 16 Click-to-Run Localization Component 16.0.13001.20144
Office 16 Click-to-Run Licensing Component 16.0.13001.20384
AMD Settings 2020.0204.1805.32548
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219 10.0.40219
Snagit 13 13.0.0
Intel(R) Chipset Device Software 10.1.18121.8164
Intel(R) Management Engine Driver 1.0.0.0
HP Sure Sense Installer 1.2.31.0
Paragon Hard Disk ManagerT 25 Anniversary LE 17.10.2.5049
HP Collaboration Keyboard for Skype for Business 2.0.3.1
Oracle VM VirtualBox 6.1.10 6.1.10
Intel(R) Management Engine Components 1.0.0.0
Intel(R) Icls 1.0.0.0
Intel(R) Serial IO 30.100.1915.1
Intel(R) LMS 1.0.0.0
Adobe Acrobat DC 19.012.20035
HP System Default Settings 1.4.9.2
Microsoft VC++ redistributables repacked. 12.0.0.0
EpsonNet Print 3.1.4.0
HP Collaboration Keyboard For Cisco UCC 1.0.19.1
Microsoft Visual C++ 2017 x64 Minimum Runtime - 14.14.26429 14.14.26429

Google Update Helper 1.3.35.451
Branding64 1.00.0001
Microsoft Visual C++ 2017 x64 Additional Runtime - 14.14.26429 14.14.26429
Intel(R) Management Engine Components 1.0.0.0
Epson Event Manager 3.10.0085
Epson Connect Printer Setup 1.4.2
Paragon UIM 24.65.0.487
Dynamic Application Loader Host Interface Service 1.0.0.0
HP PC Hardware Diagnostics UEFI 7.5.2.0
AMD Settings 2020.0204.1805.32548
HP Notifications 1.1.23.1
Epson Software Updater 4.5.4
Microsoft VC++ redistributables repacked. 12.0.0.0
Branding64 1.00.0002
HP MAC Address Manager 1.1.19.1
HP Collaboration Keyboard Runtime 1.0.18.1

wmic:root\cli>

Regrettably we don't know either what program might be causing your issue, as the offending program is one that:

fth0 wrote:VirtualBox detects but doesn't recognize.

Try checking if Hyper-V is active on your PC. See https://superuser.com/questions/1026651 ... ed-running
If Hyper-V is enabled, post back and we'll tell you how to turn it off.

The only other thing I can suggest is to 'nuke it from orbit'.
Get a different disk drive for you host PC. Reinstall your host OS only nothing else, then install Virtualbox and try a guest. (Note you may need to turn Hyper-V off again.) If the guest runs, install one of your other programs, reboot, and try Virtualbox again. If Virtualbox runs again, rinse and repeat, one program at a time. When you get to the point where Virtualbox doesn't run anymore, the last program installed is likely the offending party. Sometimes folks have tried this and found that all programs run together at the end without interfering with Virtualbox.

Hyper-V is disabled. The only option left is to follow the path others did ... Reimage the PC and install the applications one at a time and find the ghost

Thanks, Scott and fth0.

Good news ...

I have reinstalled the OS (Win 10) and straight away installed the Virtual box 6.1.12 and imported the appliance. Was able to launch the VM's and working as expected.

As advised, trying to install one application at a time and reboot and check if virtual box is still able to launch the VM... Tedious but it's ok rather than fighting with the unknown problem

Thank you very much Scott for the suggestion.

PS: Disabled windows update just to make sure an update won't crash the VirtualBox

Kumar1 wrote:HP Sure Sense Installer 1.2.31.0

This one is probably a candidate. As scottgus1 indicated, sometimes it suffices to install VirtualBox and the offending software in the reverse order than they were installed before.