VirtualBox

Changes between Initial Version and Version 1 of Ticket #18260, comment 1


Ignore:
Timestamp:
Jan 1, 2019 8:31:24 AM (5 years ago)
Author:
Socratis

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #18260, comment 1

    initial v1  
    22> ''Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).''
    33
    4 1. You need to re-install !VirtualBox to make sure that the Bridged adapter filter is properly installed.
     41. You need to re-install !VirtualBox to make sure that the Bridged adapter filter is properly installed. You'll need to do that with every Win10 major upgrade, because the Win10 upgrade is not an upgrade, it's a re-installation of a new OS with migration from the previous install. And the migration fails. This has been discussed ''ad nauseam'' in the forums, see next.
    55
    662. It's usually better and faster, if issues get first addressed in the [https://forums.virtualbox.org/ VirtualBox forums], a lot more eyes there. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably __not a bug__ and someone from the developers has to deal with it and close it as "__Invalid__".
    7 
    8 3. You were supposed to follow these steps [https://www.virtualbox.org/newticket when you filed the bug], and provide a VBox.log:
    9 > ''__Attach a (full) log file__ ("Machine" menu/"Show Log" in the main !VirtualBox Manager window) straight away to save time for you and for us. The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run. Please __do not cut and paste it.__''

© 2023 Oracle
ContactPrivacy policyTerms of Use