#9272 closed defect (duplicate)

USB device doesn't seen by virtual Box

Reported by:	ddn	Owned by:
Component:	other	Version:	VirtualBox 4.1.0
Keywords:		Cc:
Guest type:	other	Host type:	Windows

Description

in recent version (4.1) usb seems to be broken again :(

inseted eToken USB device, start VBox GUI, doesn't see device in list.

exit VBox GUI, restarted installer and ask for repair. Windows ask me to install VBox Usb driver, i choice YES. installer do work fine. Rebooted my OS after i launch VBox GUI and he still doesn't see USB device attached.

OS: Windows 7 64bit SP1.

Attachments (1)

vboxusbbug20110722.jpg (96.9 KB ) - added by ddn 13 years ago.: windows device manager and vbox gui screenshot

Download all attachments as: .zip

Change History (15)

by ddn, 13 years ago

Attachment:	vboxusbbug20110722.jpg added

windows device manager and vbox gui screenshot

comment:1 by Krzysztof, 13 years ago

Hi, The same issue at mine installation:
Win7 Professional SP1 - 64bit
Virtualbox 4.1.0 r73009
Extension Pack 4.1.0 r73009

BR,
Krzysztof

follow-up: 5 comment:2 by misha, 13 years ago

This seems as a dup of the #9299. Please try the test build mentioned in http://www.virtualbox.org/ticket/9299#comment:5 to see if it solves your issue.

comment:3 by Krzysztof, 13 years ago

Yes, I confirm: after installation of ver. 4.1.1-r73186 USB is working OK. THX, BR, Krzysztof

comment:4 by misha, 13 years ago

Resolution:	→ duplicate
Status:	new → closed

Thanks for the feedback, marking as a dup of #9299 then.

in reply to: 2 ; follow-up: 6 comment:5 by ddn, 13 years ago

Replying to misha:

This seems as a dup of the #9299. Please try the test build mentioned in http://www.virtualbox.org/ticket/9299#comment:5 to see if it solves your issue.

i confirm. USB device working normally. but in this test build Network BROKEN :(

VBox fails to start VM with: Failed to open a session for the virtual machine winxpsp3.

Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).

Result Code: E_FAIL (0x80004005) Component: Console Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}

without network attached it will start normally

in reply to: 5 ; follow-up: 7 comment:6 by misha, 13 years ago

Replying to ddn: This most likely means the bridged networking component was not installed properly for you. Please provide MSI & Setup API logs here, i.e. uninstall VBox, enable MSI & Setupapi logging and run installation again. Make sure you have Bridged Networking component selected in installer component selection dialog.

in reply to: 6 ; follow-ups: 8 9 comment:7 by ddn, 13 years ago

Replying to misha:

Replying to ddn: This most likely means the bridged networking

Misha: should i create new ticket or attach here logs ?

in reply to: 7 comment:8 by misha, 13 years ago

Replying to ddn:

Misha: should i create new ticket or attach here logs ?

Attaching them here should be sufficient.

in reply to: 7 ; follow-up: 10 comment:9 by misha, 13 years ago

Replying to ddn:

Misha: should i create new ticket or attach here logs ?

We've found the source of the VERR_SUPDRV_COMPONENT_NOT_FOUND problem you observed and are now working on solving it, the logs are not necessary, thanks a lot for pointing it out.

in reply to: 9 comment:10 by ddn, 13 years ago

Replying to misha:

Replying to ddn:

Misha: should i create new ticket or attach here logs ?

We've found the source of the VERR_SUPDRV_COMPONENT_NOT_FOUND problem you observed and are now working on solving it, the logs are not necessary, thanks a lot for pointing it out.

okay. thank you and your team for your work!