Installation failed on Windows 10

[gamliela]

Hello,
I'm new to VirtualBox.
I'm trying to install the latest version (5.0.6) on a Windows 10 host (build 10240), but the installer fails every time.

Here is what I did:
---------------------
1) tried to install several times Docker for windows (which includes VB). The installation was unsuccessful (only the VB part).
2) tried to install several time VirtualBox 5.0.6 - again, no luck.
3) cleaned leftovers: a) VBox ethernet adapters from "Network Connections", b) "vbox" registry entries (anything I could find).
4) tried to install VirtualBox 5.0.6 again.

Attached MSI log + driver installation logs for the last step.

Any help would be appreciated...
Thanks!

[mpack]

Did you use "Run as administrator" when running the installer?

[gamliela]

Yes I did.
I also turned off UAC.

[mpack]

Well, it seems to be gettiing errors when installing device drivers, which suggests a privilege issue. You shouldn't need to turn UAC off... in fact I didn't think that was even possible on 64bit Windows. I believe the relevant feature is called Driver Signature Enforcement, and it can be set to various levels, but not disabled. You want to avoid the level which silently discards drivers whose signature Windows doesn't like: it should at least prompt you, or give up installing freeware.

[gamliela]

I did another try with UAC enabled and "Driver Signature Enforcement" disabled (AFAIK, it has only 2 modes - disabled and enabled).
Still no luck.

Attached new log files + error message.

For some reason the MSI does not generate log file, although I followed the procedure here -//wiki/MSI_Logging .

[mpack]

Well, the only other thing I can think of is that there might be some kind of problem with your download. I would suggest checking the MD5 sum of the actual file on the target host.

[gamliela]

I successfully installed the software without the host-only and bridge adapters, so it's not a download problem (but maybe it's a packaging bug?).
Anyway I will try to work this way, I hope it will be fixed in newer versions.
Thanks

[mpack]

I would expect a packaging bug to affect more than one person.