VirtualBox always fails starting VM - why?

[MIRKOSOFT]

Hi!

I have new installed Windows 10.1709 x64 Pro and after installation of VirtualBox and addons Itried to start any VM - always failed.
So, I tried to create new one and start it. But always it is same error.
Here are details:
Host: ASUS Z170A, Intel Core i5, 20GB RAM, Intel integrated graphics, nVidia GeForce 210 PCIe16 card, 5,5 TB storage space
Error of Windows 7 x64 VM:

VBOX error.jpg (43.94 KiB) Viewed 3080 times

And copied message:

Failed to open a session for the virtual machine Windows 7 x64 SP2 SK.

The virtual machine 'Windows 7 x64 SP2 SK' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'L:\VirtualBox\Windows 7 x64 SP2 SK\Logs\VBoxHardening.log'.

Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}

Here's log:

VBoxHardening.log

(19.78 KiB) Downloaded 8 times

Can anybody explain me where is problem?
Thank you for all.
Miro

[socratis]

Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues.

[MIRKOSOFT]

I did these steps:

1. totally removed Hyper-V components
2. uninstalled VirtualBox by Uninstall Tool with all traces to VBOX
3. reboot
4. reinstalled VirtualBox
5. excluded VirtualBox folder from Avast tests
6. started VirtualBox
7... and at VM start it reports same problem,,,

First time I'm using Windows 10.1709 Pro on desktop, notebook has working VirtualBox with Windows 10.1709 Home

What to do more?

Miro

[socratis]

Completely uninstall Avast Antivirus.
Uninstall and re-install VirtualBox by right-clicking on the installer and selecting "Run-as-Administrator". Even if you are the Administrator.

[MIRKOSOFT]

I uninstalled Avast with all traces, to be sure that Avast self-defending services are removed, I reboot.
I uninstalled VirtualBox.
Reinstalled as admin
To be sure I was searching for network adapters and found there Hyper-V adapter, removed, also removed VBox adapters,
Now tested with same error, but I checked VBox by recommended sc.exe in error message and here's result:

vboxdrv.jpg (36.46 KiB) Viewed 3065 times

But after reinstallation I find always settings of VBox done in previous installations.

What can else work wrong?
Miro

[MIRKOSOFT]

Addon:

The fu**ed Avast auto-reinstalls itself - is it still problem?
I can go to Safe Mode and force uninstall.

But here's Q: Is Windows Defender enough in 1709? It has real-time protection, but I don't know how safe it is.

Miro

[socratis]

Avast auto-reinstalls itself - is it still problem?

Is Windows Defender enough in 1709?

I would say yes to both questions...

[MIRKOSOFT]

So, now I did these steps:
Safe mode:
- force uninstall Avast
- deleted all found Avast folders
- deleted all Avast registry entries found
After reboot:
- clean all Avast and VirtualBox folders in AppData and Program Data
- checked for entries in Program Files and Program Files (x86)
1. turned on Windows Defender real-time protection
2. Installed VirtulBox as admin - I'm anyway admin
3. First time I see default settings in VBox and it means no one entry forgotten
4. Selected one VM - 32bit - failed, 64bit - failed
Here's sc.exe output:

vboxdrv.jpg (36.23 KiB) Viewed 3062 times

Here's error message window:

VBOX error.jpg (27.14 KiB) Viewed 3062 times

Here's copied error text:

Error.txt

(377 Bytes) Downloaded 3 times

[MIRKOSOFT]

And here's hardening log:

VBoxHardening.log

(19.71 KiB) Downloaded 8 times

I'm desperate. What else to do?

Miro

[mpack]

Avast is still there in the latest log.

[MIRKOSOFT]

]I forgot to remove Avast drivers.
So, I did it manually and now in log are no any lines about Avast:

VBoxHardening.log

(11.82 KiB) Downloaded 4 times

One line of error message is mysterious:

Error opening VBoxDrvStub: STATUS_OBJECT_NAME_NOT_FOUND

What is not found?

Miro

[MIRKOSOFT]

Have anybody idea where can be problem?
I don't want reinstall Windows for VirtualBox... really I'm desperate.

Miro

[BillG]

I am still not sure that you understand what was said about installing as admin. The fact that your account is an admin account is not enough. An admin account normally runs without admin privilege. It will request admin privilege as required (if you have not tampered with UAC). If Windows asks for and is granted admin privilege during the install, everything should be OK. If you want to avoid being prompted (or if UAC is not active), manually run the install with admin privilege by right clicking the installer and selecting the Run as administrator option.

The important thing is that VirtualBox should be installed under the username of the person who wants to use it, but the installer must run with admin privilege.

[MIRKOSOFT]

ÔK, I do it tomorrow again.

Miro

[MIRKOSOFT]

Did it!
Following all your recommendations.
Result = again same failure!

Did this:
1. uninstalled VirtualBox with all traces and data files
2. reboot
3. removed Virtual Host Network Adapter in Device Manager
4. reboot
5. installed newest - today downloaded - VirtualBox
6. in Preferences I set language, other options and installed today downloaded Additions
7. reboot
8. Started VM "Windows Premiere Edition"
9. Failure
what is here a problem?
Previous version worked correctly, installed yet in Windows 10.1703
On my laptop with Windows 10.1709 (same Windows, but Home - not Pro) VirtualBox works correctly...the same version!

Here's log and command line output:

VBoxHardening.log

(11.94 KiB) Downloaded 7 times

vboxdrv.txt

(522 Bytes) Downloaded 5 times

Miro