Upgraded to 5.04 for Windows 10, now having issues

[joehatescoffee]

I have a webui for a service running on the guest PC that is Windows XP.

After upgrading the VirtualBox to 5.04, the guest started perfectly. A first since upgrading to Windows 10 on the host.

However, now I cannot access the webui on the guest from the host. (Fixed IP address)

I am using the bridge adapter.

The guest has access to the internet.

The guest used to use a script to map a drive automatically to a host folder. After the upgrade, that started failing. So, I switched to using the shared folders option on VirtualBox to auto-mount the folder. (This worked).

I would like to be able to access the webui from any device on the network, but can't figure out what has changed.

[noteirak]

Try switching to NDIS5 driver.

The user is able to choose between NDIS5 and NDIS6 host network filters drivers during the installation. This is realized via a command line parameter NETWORKTYPE. The NDIS6 driver is default for Windows Vista and later. For older Windows versions, the installer will automatically select the NDIS5 driver and this cannot be changed. For Windows Vista and later the user can force to install the (legacy) NDIS5 host network filter driver using NETWORKTYPE=NDIS5. For example, to install the NDIS5 driver on Windows 7, do

VirtualBox.exe -msiparams NETWORKTYPE=NDIS5

[joehatescoffee]

I found open ticket #14457 discussing this.
The NDI5 switch does not work on Windows 10. (Documented in the ticket.)