Bridge Adapters not showing any network names
Re: Bridge Adapters not showing any network names
To Scott the admin and the other volunteer helper, i uninstalled virtualbox. I went into my windows settings and turned off windows virus protection and my firewall was completely disabled. I installed again and everything looks just like how its supposed to but when i look at my bridged adapters NO NAMES POP UP! To the admin, im very open to teamviewing and allowing you to control my pc to try and figure this out because it is very stressful that this is not working at all please somebody help me
Re: Bridge Adapters not showing any network names
This is inside the file that is supposed to install the associated driver. Tell me if something looks wrong cause i dont know why my pc wont install it.
Code: Select all
; $Id: VBoxNetLwf.inf 135976 2020-02-04 10:35:17Z bird $
; @file
; VBoxNetLwf.inf - VirtualBox Bridged Networking Driver inf file
;
;
; Copyright (C) 2014-2020 Oracle Corporation
;
; This file is part of VirtualBox Open Source Edition (OSE), as
; available from http://www.virtualbox.org. This file is free software;
; you can redistribute it and/or modify it under the terms of the GNU
; General Public License (GPL) as published by the Free Software
; Foundation, in version 2 as it comes in the "COPYING" file of the
; VirtualBox OSE distribution. VirtualBox OSE is distributed in the
; hope that it will be useful, but WITHOUT ANY WARRANTY of any kind.
;
; The contents of this file may alternatively be used under the terms
; of the Common Development and Distribution License Version 1.0
; (CDDL) only, as it comes in the "COPYING.CDDL" file of the
; VirtualBox OSE distribution, in which case the provisions of the
; CDDL are applicable instead of those of the GPL.
;
; You may elect to license modified versions of this file under the
; terms and conditions of either the GPL or the CDDL or both.
;
[Version]
Signature = "$Windows NT$"
CatalogFile = VBoxNetLwf.cat
Class = NetService
ClassGUID = {4D36E974-E325-11CE-BFC1-08002BE10318}
Provider = %Provider%
DriverVer = 09/01/2022,6.1.38.3438 ; r153438
[Manufacturer]
%Provider% = VBox,NTx86,NTamd64
[ControlFlags]
[VBox]
%VBoxNetLwf_Desc% = VBoxNetLwf.ndi, oracle_VBoxNetLwf
[VBox.NTx86]
%VBoxNetLwf_Desc% = VBoxNetLwf.ndi, oracle_VBoxNetLwf
[VBox.NTamd64]
%VBoxNetLwf_Desc% = VBoxNetLwf.ndi, oracle_VBoxNetLwf
[VBoxNetLwf.ndi]
AddReg = VBoxNetLwf.ndi.AddReg, VBoxNetLwf.AddReg
Characteristics = 0x40000 ; NCF_LW_FILTER
CopyFiles = VBoxNetLwf.Files.Sys
NetCfgInstanceId = "{7af6b074-048d-4444-bfce-1ecc8bc5cb76}"
[VBoxNetLwf.ndi.Remove.Services]
DelService = VBoxNetLwf,0x200 ; Stop the service before uninstalling
[VBoxNetLwf.ndi.Services]
AddService = VBoxNetLwf,, VBoxNetLwf.AddService, VBoxNetLwf.AddEventLog
[VBoxNetLwf.AddService]
DisplayName = %VBoxNetLwfService_Desc%
ServiceType = 1 ;SERVICE_KERNEL_DRIVER
StartType = 1 ;SERVICE_SYSTEM_START
ErrorControl = 1 ;SERVICE_ERROR_NORMAL
ServiceBinary = %12%\VBoxNetLwf.sys
LoadOrderGroup = NDIS
AddReg = VBoxNetLwf.AddService.AddReg
[VBoxNetLwf.AddService.AddReg]
[VBoxNetLwf.AddEventLog]
AddReg = VBoxNetLwf.AddEventLog.AddReg
[VBoxNetLwf.AddEventLog.AddReg]
HKR,,EventMessageFile,0x00020000,"%%SystemRoot%%\System32\IoLogMsg.dll"
HKR,,TypesSupported,0x00010001,7
[SourceDisksNames]
1=%DiskDescription%,"",,
[SourceDisksFiles]
VBoxNetLwf.sys=1
[DestinationDirs]
DefaultDestDir = 12
VBoxNetLwf.Files.Sys = 12 ; %windir%\System32\drivers
[VBoxNetLwf.Files.Sys]
VBoxNetLwf.sys,,,2
[VBoxNetLwf.ndi.AddReg]
HKR, Ndi, HelpText, , %VBoxNetLwf_HELP%
;HKR, Ndi, ClsID, 0, {f374d1a0-bf08-4bdc-9cb2-c15ddaeef955}
;HKR, Ndi, ComponentDll, , VBoxNetLwfNobj.dll
HKR, Ndi, FilterClass, , compression
HKR, Ndi, FilterType, 0x10001, 0x2
HKR, Ndi, FilterRunType,0x10001, 2 ; OPTIONAL, to prevent unbinding of protocol drivers
HKR, Ndi, Service, , VBoxNetLwf
HKR, Ndi, CoServices, 0x10000, VBoxNetLwf
HKR, Ndi\Interfaces, UpperRange, , noupper
HKR, Ndi\Interfaces, LowerRange, , nolower
HKR, Ndi\Interfaces, FilterMediaTypes, , ethernet
[VBoxNetLwf.AddReg]
;HKR, Parameters, Param1, 0, 4
[Strings]
Provider = "Oracle Corporation"
DiskDescription = "VirtualBox NDIS6 Bridged Networking Driver"
VBoxNetLwf_Desc = "VirtualBox NDIS6 Bridged Networking Driver"
VBoxNetLwf_HELP = "VirtualBox NDIS6 Bridged Networking Driver"
VBoxNetLwfService_Desc = "VirtualBox NDIS6 Bridged Networking Service"
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Bridge Adapters not showing any network names
Please provide the C:\Windows\INF\setupapi.dev.log file from within the host OS, and a (zipped) VBoxHardening.log file from any VM run.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Bridge Adapters not showing any network names
I got your PM, Steezy. Unfortunately, I'm not sure what else to do. There's something very unusually wrong with the host OS on your PC. This kind of problem is extremely rare and as I've seen always comes down to a damaged host OS or some other software that is interfering. I'd strongly suspect that if you did a complete fresh reinstall of your host OS only, then installed Virtualbox, Bridged would install correctly.
In addition to fth0's suggestions, look through all your other installed apps for anything that even in a slight hint of a way might touch the host network: Wireshark-like scanners, banking/web-safe nanny software, malware scanners, network-quality-of-service apps, games, other hypervisors, etc.
In addition to fth0's suggestions, look through all your other installed apps for anything that even in a slight hint of a way might touch the host network: Wireshark-like scanners, banking/web-safe nanny software, malware scanners, network-quality-of-service apps, games, other hypervisors, etc.
Re: Bridge Adapters not showing any network names
attached is the setupapi log file im not sure where to find the other one you requestedfth0 wrote:Please provide the C:\Windows\INF\setupapi.dev.log file from within the host OS, and a (zipped) VBoxHardening.log file from any VM run.
- Attachments
-
- setupapi.dev.log
- (25.09 KiB) Downloaded 6 times
Last edited by steezy on 14. Dec 2022, 15:54, edited 1 time in total.
Re: Bridge Adapters not showing any network names
going through my whole installed programs list theres literal;ly nothing that stands out that would be interfering. Im at a complete loss and this is far beyond my reach of pc knowledgescottgus1 wrote:I got your PM, Steezy. Unfortunately, I'm not sure what else to do. There's something very unusually wrong with the host OS on your PC. This kind of problem is extremely rare and as I've seen always comes down to a damaged host OS or some other software that is interfering. I'd strongly suspect that if you did a complete fresh reinstall of your host OS only, then installed Virtualbox, Bridged would install correctly.
In addition to fth0's suggestions, look through all your other installed apps for anything that even in a slight hint of a way might touch the host network: Wireshark-like scanners, banking/web-safe nanny software, malware scanners, network-quality-of-service apps, games, other hypervisors, etc.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Bridge Adapters not showing any network names
Right-click any VM, choose Show In Explorer. In the folder window that appears, go into the Logs subfolder, get the VboxHardening.log, zip and post it.steezy wrote:im not sure where to find the other one you requestedfth0 wrote:and a (zipped) VBoxHardening.log file from any VM run.
Re: Bridge Adapters not showing any network names
here you goscottgus1 wrote:Right-click any VM, choose Show In Explorer. In the folder window that appears, go into the Logs subfolder, get the VboxHardening.log, zip and post it.steezy wrote:im not sure where to find the other one you requestedfth0 wrote:and a (zipped) VBoxHardening.log file from any VM run.
- Attachments
-
- VBoxHardening.zip
- (17.44 KiB) Downloaded 7 times
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Bridge Adapters not showing any network names
The VBoxHardening.log file doesn't reveal any problem to me, but the setupapi.dev.log file shows that you've installed NordVPN:
For a test, I'd suggest to uninstall NordVPN and VirtualBox, reboot the host, re-install VirtualBox and try if the issue persists. If the problem is solved, re-install NordVPN and see if the issue returns or not. Please report what you discover.setupapi.dev.log file wrote:>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - tapnordvpn] >>> Section start 2022/12/13 22:44:08.844 [...] >>> [Install network driver - VirtualBox] >>> Section start 2022/12/13 23:31:12.121 dvi: {Select Best Driver} ! dvi: Selecting driver failed(0xe0000228) [...] >>> [Install network driver - VBoxNetLwf.inf] >>> Section start 2022/12/13 23:32:13.869 dvi: {Select Best Driver} ! dvi: Selecting driver failed(0xe0000228)