This is how any virtualization platform does bridged networking. The NDIS6 driver is the default for most supported Windows hosts. So no, the VirtualBox driver doesn't become your exclusive network driver, although it very much does have to process all of the traffic arriving at the interface, but (and this is very important) it's acting as a virtual switch. The Oracle VM VirtualBox installation can be started in either of the following ways. When you install VirtualBox, it adds another driver to this list: VirtualBox NDIS6 Bridge Networking Driver, and Windows does some magic in the background to ensure all these drivers are working together via the NDIS protocol. The most common among these are Internet Protocol Version 4 (TCP/IPv4) and Internet Protocol Version 6 (TCP/IPv6) (there's also QoS Packet Scheduler, Microsoft LLDP Protocol Driver, etc.). You can see these when you look at the network device properties via Network Connections.
not on "Desktop", or "Documents", but to "Public/Downloads" for example. Download (if you haven't already) the latest VirtualBox and its matching ExtPack.Also, check out Device Cleanup program that helps you to remove any unused devices from your computer. Mind the installation, it comes with "offers" from 3rd parties, known as "bundleware". CCleaner is a freeware utility that could help you. Enable Virtualbox NDIS6 Bridget Networking Driver (if its disabled - if its not. You may want to clean up your registry and/or filesystem at this point. networkingvirtual machinevirtualboxvirtualizationwindows 10.