Vagrant & Virtualbox in Windows 10; Error renaming connection

I tried to run a vagrant setup using the latest versions of Vagrant VirtualBox and windows 10 (latest update): Vagrant 1.8.6 VirtualBox 5.1.8 r111374 (Qt5.5.1)

If I set in my Vagrant file config.vm.network :private_network, ip: "192.168.33.10" I get this error:

Error renaming connection: 
Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

Sofar I tried installing/removing both vagrant and virtualbox, I even downgraded and upgraded.. Restarted my compuiter several times, switched off my proxy, followed every crazy hack out there but I always get that error.

I even went to regedit and deleted all the related keys there but no success!

The output of the console:

vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: E_INVALIDARG
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.1\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0038).
VBoxManage.exe: error: Please contact the product vendor!
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: "enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)" at line 71 of file VBoxManageHostonly.cpp

After some deep researching on this issue, I finally found two things that should be done:

1. I cleared existing VM machines and deleted those folders C:\Users\{user}\.VirtualBox and C:\Users\{user}\VirtualBox VMs restart the computer.
2. Whenever I changed the IP address of the machine, I run vagrant halt && vagrant reload && vagrant up --provision

This fixed the issue.