Issue to setup Vagrant with VirtualBox on Windows10

[rajattrish]

Hi,

I am trying to setup Vagrant (Version-2.1.2) with VirtualBox (Version-5.2.16) on Windows10 but not able to setup. I am struggling from last 2 weeks and tried lots of solutions given over internet but no luck.

I install/Un-installed the virtualbox approx 100 times and tried with other versions as well but still same issue. It should be great if anyone can help me out to set it up. Your help will be highly appreciated.

Some information about system and what I had done before go ahead.

OS Version : Windows 10 [1709] 64Bit
RAM 8GB

Hyper-V is disabled already.
Virtualization is also enabled in BIOS.

Below are the error which I am getting while running "Vagrant UP" from Power-shell. and attached are the VBoxHardening.log logs :-

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/xenial64' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "4cd35e8c-135e-426d-b54d-ecc8b00b957c", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'devops-db_default_1534834539569_69190' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\hemraj_s\VirtualBox VMs\devops-db_default_1534834539569_69190\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine

[andyp73]

Ignoring the fact that we don't support Vagrant in these parts...

17ac.35b8: supR3HardenedWinFindAdversaries: 0x3
17ac.35b8:     FileDescription: Symantec CMC Firewall SysPlant
17ac.35b8:     FileDescription: Symantec CMC Firewall sysfer
17ac.35b8:     FileDescription: Symantec Event Library

You should uninstall all the Symantec software you have running. It is known to be a PITA and isn't needed with Windows 10.

329c.258c: supR3HardenedDllNotificationCallback: load   0000000068000000 LB 0x00058000 C:\Windows\System32\QIPCAP64.dll [fFlags=0x0]

You also appear to have Forcepoint/Triton Endpoint DLP or something similar. Again, these are known to cause problems with VirtualBox. If you can't add VirtualBox as an exception then you are going to need to uninstall them too.

-Andy.

[rajattrish]

Thanks Andy, happy to see your quick response !!!

I have raised the concern with Symantec team to check it.

Do you have any more suggestions then where I can proceed till gets the response from Symantec team. Your quick help is highly appreciated.

Thanks
Raj

[socratis]

The same setup is working fine for one of my colleague and she also have the same software installed in her system.

Even if you setup two identical systems, with the same software, side-by-side, they're going to end up different. Small differences in the update mechanism (for example), usage patterns, variations in the software installed, can result in perturbations. It's called chaos theory.

You could direct Symantec's software to ignore all VirtualBox related files, add an exception.

[rajattrish]

Hi,

I checked it with Symantec team but as per them, Symantec is not blocking the VirtualBox traffic. Please find the attached Symantec control logs and suggest what could be the issue now.

Please find the latest VboxHardening logs and do the needful.

Your help would be appreciated.

Thanks

[mpack]

Does the problem go away if Symantec is uninstalled? That is the only important fact.

[rajattrish]

Hi, Good to see your reply. Thanks

As I am doing it for organisation so its mandatory to have Symantec installed on system. Symantec team just checked the logs (attached) if it blocking the VirtualBox but it doesn't.

Please suggest how to proceed.

Thanks

[mpack]

You have already been told how to proceed. Uninstall Symantec, even temporarily. Does the problem go away or not? I see no way to proceed without this vital bit of information.

[socratis]

Symantec team just checked the logs (attached) if it blocking the VirtualBox but it doesn't.

You, and the Symantec team, seem to have gotten it backwards. It's not Symantec that's blocking VirtualBox. It's VirtualBox that refuses to run if a incorrectly/inappropriately signed application like Symantec, tries to invade VirtualBox's memory.

• Point them to the "Diagnosing VirtualBox Hardening Issues" FAQ again.
• Ask them to check their binaries with "signtool.exe", they should know where to find it.
• Put an exception in their scanning engine for all VirtualBox related apps/files.
• And most importantly: follow mpack's advice!

[mpack]

6724.32e0: More than one thread in process

Something is injecting spying code into VirtualBox, which is entitled to get upset about it, regardless of the intentions of the spy.

Spying threads are often due to "web safe filters", i.e. modules which prevent viewing porn and sports channels at work etc. There may be other apps which do it, and they don't all show up in the VirtualBox adversaries list.

[rajattrish]

Hi Team,

I am coordinating with the IT team as well as with Symantec team to fix this issue. Apart from that, trying with different versions of VBox on different OS builds of windows10. looks like the issue is not due to Symantec because it's working fine with below system configurations and VBox version.

working for :-
VirtualBox-4.3.12-93733-Win on Windows10 build-1709.
VirtualBox-5.X.XX-XXXX-Win on Windows10 build-1703.

but issue for VirtualBox-5.X.XX-XXXX-Win on Windows10 build-1709.

Not sure but looks like its OS image issue. Can it be ?
It's not possible to downgrade the OS build because build-1709 is the base image build for all the employees now. We need VirtualBox-5.X-Win on build-1709 because in lower versions, the bridged adaptor is not supportable and that is required for dynamic IP assignation.

One more thing, on Windows10 build-1703 + VirtualBox-5.X version there was no error for hardening but virtual machine was not getting created after execute my vagrant file.

Again stuck !!!

[socratis]

working for :-
VirtualBox-4.3.12-93733

You didn't really read the Hardening FAQ, did you? Please read it...