Govan06 wrote:I'm posting this here because it might help some people:
This was my situation : unable to install virtual box 5.x.x after upgrading to windows 10. installation used to fail and roll back everytime during the network installation.
What I did to fix my issue was to uninstall my antivirus (I have Kaspersky) and reboot. Then Installed virtual box (latest test build) and everything went smooth (I did check, all my VMs ran perfectly). After that reinstall antivirus, and now everything works correctly.
So if you had an Antivirus software prior to upgrading to windows 10, uninstall antivirus, install VB, reinstall antivirus.
Hope that helps someone !
Thank you.
Kaspersky was the cause of my problems blocking VB install on a clean windows 10 pro 64. Disabling Kaspersky wasn't enough. I had to uninstall it aswell, reboot and VB installed just fine including running VMs with build 102375. Also kaspersky blocked other installs like openvpn, pia etc. Hope that helps to anyone having similar problems.
only hope that this issue will be fixed!
anyway try the last test build 5.0.51.r102375 https://www.virtualbox.org/ticket/14437 ... um_hist=44
but in my case do not solve
in the sense that then the adapter is found..but ..then the vm do not starts
Giusi wrote:only hope that this issue will be fixed!
anyway try the last test build 5.0.51.r102375
but in my case don not solve
in the sense that then the adapter is found..but ..then the vm do not starts
5.0.3.102449 do not solve bridge network..and for me has been a backward step in the countrary direction cause
,instead of r102375,
i not able again to see my realtek adapt if i choose network bridge..
so may be the enumerating issues has come back..
a nightmare..
Nobody should be using a compatbility mode. That will only mask issues instead of fixing them: relief will most likely be temporary, and harder to diagnose from afar in the future.
Compatibility mode, if used at all, is for ancient apps which are no longer being developed. Not a kludge to hide bugs.