virtualbox.org

Hello,

there are already some posts regarding this issue which follows me since years: after an inplace upgrade of Windows 10 (independenly which versions) the VB Host-Only Adapter gets lost/corrupted/destroyed.

Current workaround is to remove the Host-Only Adapter before inplace upgrade and install it again after - but it would really be good to have a real solution for this problem.

Why does this issue basically occur ? After some further testing and log file analyzing I found following in the Windows 10 logfile - see screenshot. The VB driver of the Host-Only adapter does NOT getting migrated ! And unfortunately some information of this driver remains in the Windows registry and therefore
the same Host-Only Adapter with the same IP configuration cannot be created anymore (I also found a workaround for removing these regkeys so that the adapter can be created again).

Does anybody know why the driver does not get migrated ? Why is the driver not being supported by Windows as the logfile says ? I also tried with the latest VB version - no success.

Thanks for any information/help !

csps wrote:Why does this issue basically occur ?

There's very few here that would know why this happens, I think (certainly not me). We're all fellow Virtualbox users, not the devs.

This might be good for the Bugtracker.