virtualbox.org

Hello everyone.
I use, with satisfaction, a multifunction printer (MFP) Epson Stylus SX410 (since year 2009) linked to my PC through a network device MFP Server wifi (Edimax PS-1208MFG (E5) Epson edition), connected to the same wifi router of my home network .
In reality, my Windows 10 (in Printer properties) sees the printer connected to the USB001 virtual port, which is evidently redirected to the network thanks to the software (MFP Manager) supplied with the printer and the MFP server.
In other words, the MFP Manager software seems to manage and redirect all traffic to and from the multifunction printer, logically connected to the virtual usb USB001, on the network (where it is “physically” connected via wifi by the router).
Although the MFP Server device management software is a version for Windows Vista or 7, everything works correctly the same but, until VirtualBox is installed (try various versions).
In fact, as soon as the installation of VirtualBox begins, the MFP Server Manager loses the connection with the MFP Server device (and consequently with the printer / scanner connected to it) and can no longer find it on the network (wifi) despite being regularly connected with an assigned IP address, as always.
Also, from the “devices and printers” of my Windows 10 PC, I no longer see the printer, it disappears.
What could be the problem?
Is there anything to set after installing VirtualBox?

Virtualbox installs a network driver so it can Bridge guests to the PC's network card.

You could try disconnecting the Bridged binding from the Wi-fi adapter.
Open the Control Panel, Network and Sharing Center. On the left side, click 'Change adapter settings', the network adapters will appear in a new window.
Right-click the Wi-fi adapter, choose Properties. Give an administrator password if necessary.
This box will appear:


Uncheck 'Virtualbox NDIS6 Bridged Networking Driver', just like the picture above. Click OK.

This should remove Bridged from the Wi-fi adapter. Reboot the PC and see if the printer software connects.

If it does not, you can uninstall Virtualbox and reinstall with the Bridged driver disabled, see what that does.

Perfect. Thanks to your suggestion, now everything seems to be working.
At the time, I reinstalled VirtualBox excluding all networking drivers because
the simple disconnect of the Bridged binding from the Wi-Fi adapter was not enough.
Later, I will try to exclude only the "Bridge" support and communicate the result.
Good bye.