I've tried to reinstall virtualbox. no luck.
Anybody has the same problem? Thanks!
Host server: windows8 CHN version
vbox version: VirtualBox-6.1.26-145957-Win
log: PFA
---------------------------
VirtualBox - Error In supR3HardenedWinReSpawn
---------------------------
<html><b>Error relaunching VirtualBox VM process: 5<br>Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment ubuntu16.04 --startvm 0c854803-3238-4649-bc25-14f735b67b37 --no-startvm-errormsgbox "--sup-hardening-log=C:\Users\Ryan\VirtualBox VMs\ubuntu16.04\Logs\VBoxHardening.log"' (rc=-104)</b><br/><br/>Please try reinstalling VirtualBox.<br><br><!--EOM-->where: supR3HardenedWinReSpawn
what: 5
VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name.
</html>
---------------------------
OK
---------------------------
Failed to start virtual machine. rc=-104
Failed to start virtual machine. rc=-104
- Attachments
-
- VBoxHardening.zip
- log file
- (10.08 KiB) Downloaded 16 times
-
mpack
- Site Moderator
- Posts: 38786
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Failed to start virtual machine. rc=-104
Your host seems to be Windows 8.1 / Windows 2012, not Windows 8.0.
I don't see much, but I do see this error very early on:
I don't see much, but I do see this error very early on:
My own hardening log doesn't have this, but then again I have admin rights on my own PC. I don't see any "adversaries" mentioned in your log, i.e. no third party AV, but perhaps you have Windows own AV set particularly high. As a test I would try reduce this to minimal to see if it solves the problems: considerations as to a long term fix can wait until the main question is answered.2c08.19b4: FileVersion: 6.3.9600.18513 (winblue_ltsb.161009-0600)
2c08.19b4: FileDescription: ApiSet Schema DLL
2c08.19b4: NtOpenDirectoryObject failed on \Driver: 0xc0000022
2c08.19b4: supR3HardenedWinFindAdversaries: 0x0
Re: Failed to start virtual machine. rc=-104
Thanks mpack for your reply!
After I removed some software in my system (not sure which one is the key one but I'm sure those are not virus deny software).
VM box came back to working well.
After I removed some software in my system (not sure which one is the key one but I'm sure those are not virus deny software).
VM box came back to working well.
-
mpack
- Site Moderator
- Posts: 38786
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Failed to start virtual machine. rc=-104
I'm glad you are up and running again, although it would have been nice to know what the culprit was that VirtualBox didn't detect. The usual culprits are "internet safe" browser filters and similar.