[Solved] Failed to open/create the internal network error

[wilsonian]

Hello,

I've been tearing my hair out with this issue. Last night I upgraded from 4.3.12 to 4.3.20. Unfortunately that's when the problems started. When I tried to load the Host it refused, giving the following error -

Failed to open/create the internal network (VERR_INTNET_FLT_IF_NOT_FOUND)

I've tried the advice provided in the this post - ticket 7040 but it didn't resolve the issue.

So far I've tried uninstalling the software, rebooting, reinstalling 4.3.12 reboot and I still get the error message.

[mpack]

When you "tried to load the host"? I assume you mean run the guest?

It would be helpful if you provided more information, such as the network mode you're trying to use, and what host OS you have. However the usual reason for bridged networking not working, certainly on Win64 hosts, is that you didn't install the bridged networking filter drivers. Meaning, either you unticked the install option, or you didn't use "Run as administrator", or you are suffering from the "Driver Signature Enforcement" problem.

[wilsonian]

HI Sorry I meant guest, I've tried "run as admin" and followed a guide to resolve any "Driver Signature Enforcement" issues but the fault continues.

I'm running Windows 7 64bit with the latest updates and the issue only started when I upgraded to 4.3.20. If I set the device into NAT mode for the network, the guest loads fine but without the network configuration I require. I have tried many versions and I've always rebooted after an install and rebooted after uninstalling. unfortunately it doesn't resolve the issue.

When I select show hidden devices in device management I see an extra network card called the same as my standard one except with "VirtualBox Bridged Networking Driver Miniport". I assume this is normal? I haven't needed to go this fair into the setup before.

I'm currently trying to resolve this issue using 4.3.18.


Thanks.

[Perryg]

Most of the time one just needs to update the hosts NIC driver. Failing that I have read about others using the management console to remove NIC drivers and rebooting which triggers a fresh install ( not an update ) of NIC drivers.

[wilsonian]

OK so i finally figured it out. Every time I did an install I disabled Kaspersky Security. I've never had an issue with it before however this is what was causing the problem!

I had to use the their removal tool (found here - http://support.kaspersky.com/common/ser ... px?el=1464). Once removed I rebooted and reinstalled Virtual Box and it started working. I then reinstalled Kaspersky and everything was OK.

Very strange as Virtual Box was allowed complete access to the system and warnings popped up when I was launching Virtual Box.

Thanks for the replies

[NewBobo]

I get the same problem.

But I removed the Kaspersky Internet Security 2015 and Virtualbox 4.3.20 then rebooted. When I installed Virtualbox and it started working! I then installed KIS 2015 and virtualbox still working fine!!

Thanks for the replies!!!