Host-only interface IP changes on Windows 10

[srats]

When using host only network interfaces on Windows 10, the interface IP address changes and the interface is not working anymore.

Reproduction (easy way)

1 - Remove any existing host-only interfaces and dhcp servers.
2 - Run the following commands:
vboxmanage.exe hostonlyif create
Check the assigned IP and netmask and reuse them in the following command:
vboxmanage.exe hostonlyif ipconfig "VirtualBox Host-Only Ethernet Adapter" --ip 192.168.56.1 --netmask 255.255.255.0
vboxmanage.exe dhcpserver remove --ifname "VirtualBox Host-Only Ethernet Adapter"
vboxmanage.exe dhcpserver add --ifname "VirtualBox Host-Only Ethernet Adapter" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable
Notice that, at this point, the host-only interface appears to be "Automatically configured" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).
3 - Open Windows 10 network settings (Control Panel\Network and Internet\Network Connections)
4 - Notice that the newly created network interfaces uses DHCP configurations instead of manually configured settings.

Reproduction (hard way)

1 - Remove any existing host-only interfaces and dhcp servers.
2 - Run the following commands:
vboxmanage.exe hostonlyif create
Check the assigned IP and netmask and reuse them in the following command:
vboxmanage.exe hostonlyif ipconfig "VirtualBox Host-Only Ethernet Adapter" --ip 192.168.56.1 --netmask 255.255.255.0
vboxmanage.exe dhcpserver remove --ifname "VirtualBox Host-Only Ethernet Adapter"
vboxmanage.exe dhcpserver add --ifname "VirtualBox Host-Only Ethernet Adapter" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable
Notice that, at this point, the host-only interface appears to be "Automatically configured" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).
3 - Create a Linux guest (such as Ubuntu 15.04), and attach it's first network adapter to the host-only interface.
4 - Run the guest (I chose to run in live mode to avoid to install the OS). It usually gets the first ip available, 192.168.56.101 in our case
5 - Ping the host interface from the guest: ping 192.168.56.1
6 - Check the host interface IP: it has changed to 192.168.56.102 and the host-only interface does not work anymore.

Tested on VirtualBox 5.0.4 and latest testing 5.0.5.
Tested with Linux guests (Android, Ubuntu).
Reproduce on Windows 10 host.
Can't reproduce on Linux (Ubuntu, Fedora, Debian), Mac OS (10.8, 10.9 and 10.10), Windows 7 and Windows 8.1 hosts.