Windows 7 USB problem

[gwilki]

I am running windows 7 64-bit on the host and windows 7 32-bit in the guest. I am running the latest version of virualbox 5.1.6.

I have installed the add on package so that I have usb 2 support.

When I plug a usb stick into the pc, I can use the virtualbox settings to add the filter for it, so it's clear that virtualbox sees the usb stick ok.

When I start windows in the vm, the host loses the connection to the usb stick, so clearly the vm is taking over the usb stick, as it should.

However, the version of windows running in the vm does not see the usb stick. I've tried different sticks and the vm sees each of them and loads the appropriate filter, but windows running in the vm does not see any of them. I can unplug and plug in the stick with no results. As soon as I close the windows vm, the host windows sees the usb stick.

Has anyone had this issue and overcome it?

[socratis]

With the USB device plugged in and the VM not running, post the output of the following commands:

    VBoxManage list usbhost
    VBoxManage showvminfo "Your_Virtual_Machine_Name"

[gwilki]

Tks for replying. Attached are screen caps of the 2 commands and the replies.

[socratis]

A couple of things:
1) As you saw in the 1st screenshot, you have made a mistake in your VM's name.
2) It's far simpler/more efficient/faster to copy-paste the text compared to a screenshot. I don't have OCR
Could you try again with the correct VM?

[gwilki]

Sorry about that.

Here are the results

Code: Select all

C:\Program Files\Oracle\VirtualBox>vboxmanage list usbhost
Host USB Devices:

UUID:               ecea8cd4-04ba-48c0-9ba3-3b38e0739f3a
VendorId:           0x0951 (0951)
ProductId:          0x1607 (1607)
Revision:           2.0 (0200)
Port:               0
USB version/speed:  2/High
Manufacturer:       Kingston
Product:            DataTraveler 2.0
SerialNumber:       89900000000000006CB02AD2
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0016
Current State:      Busy

UUID:               4c31b6ab-0eb7-49f5-8d8b-3ddf4e09ba90
VendorId:           0x046d (046D)
ProductId:          0xc52f (C52F)
Revision:           34.1 (3401)
Port:               0
USB version/speed:  2/High
Manufacturer:       Logitech
Product:            USB Receiver
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0022
Current State:      Busy

UUID:               ed4c8212-16b7-4933-a3ac-b2c550dbec00
VendorId:           0x046d (046D)
ProductId:          0xc31c (C31C)
Revision:           100.0 (10000)
Port:               0
USB version/speed:  1/Full
Manufacturer:       Logitech
Product:            USB Keyboard
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0015
Current State:      Busy

Code: Select all

C:\Program Files\Oracle\VirtualBox>vboxmanage showvminfo "Windows 7-32 bit"
Name:            Windows 7-32 bit
Groups:          /
Guest OS:        Windows 7 (32-bit)
UUID:            fea1ca67-3914-465d-9bea-fa5a4036d271
Config file:     C:\Users\Grant\VirtualBox VMs\Windows 7-32 bit\Windows 7-32 bit.vbox
Snapshot folder: C:\Users\Grant\VirtualBox VMs\Windows 7-32 bit\Snapshots
Log folder:      C:\Users\Grant\VirtualBox VMs\Windows 7-32 bit\Logs
Hardware UUID:   fea1ca67-3914-465d-9bea-fa5a4036d271
Memory size:     2048MB
Page Fusion:     off
VRAM size:       24MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       off
Triple Fault Reset: off
APIC:            on
X2APIC:          off
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          off
BIOS APIC mode:  APIC
Time offset:     0ms
RTC:             local time
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: HyperV
State:           powered off (since 2016-10-11T17:34:32.000000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
SATA (0, 0): F:\Windows 7-32 bit.vdi (UUID: f6939fa2-dc24-4b8a-90f7-41a3e4f99cb7
)
SATA (1, 0): D: (UUID: 00445644-0000-0000-0000-00000000443a)
NIC 1:           MAC: 0800270451E2, Attachment: Bridged Interface 'Realtek PCIe
GBE Family Controller', Cable connected: on, Trace: off (file: none), Type: 8254
0EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth g
roup: none
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
UART 3:          disabled
UART 4:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           enabled (Driver: DSOUND, Controller: HDA, Codec: STAC9221)
Clipboard Mode:  disabled
Drag and drop Mode: disabled
VRDE:            disabled
USB:             enabled
EHCI:            enabled
XHCI:            disabled

USB Device Filters:

Index:            0
Active:           yes
Name:             Kingston DataTraveler 2.0 [0200]
VendorId:         0951
ProductId:        1607
Revision:         0200
Manufacturer:     Kingston
Product:          DataTraveler 2.0
Remote:           0
Serial Number:    89900000000000006CB02AD2

Bandwidth groups:  <none>

Shared folders:  <none>

Video capturing:    not active
Capture screens:    0
Capture file:       C:\Users\Grant\VirtualBox VMs\Windows 7-32 bit\Windows 7-32
bit.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB

[socratis]

A couple of things:

1. Delete all values except Name, VendorID and ProductID from your filter. The first can be anything you want. The latter two have to match exactly (which they do).
2. If that doesn't fix it, unplug the USB, launch the VM and then plug the USB.
3. At the bottom-right corner there is a USB icon. Clicking on it should show you the USB with a checkmark next to it.

PS. I enclosed the info in the "code" tag for better readability. Should have mentioned it...

[gwilki]

Thank you for all your help so far. I truly appreciate it. I'm new to the VM game, as is obvious.

I'm confused by your last reply, Socratis. The vendor id and the product id are not the same right now. The vendor id is 0951 and the product id is 1607. Should I make them the same? If so, which of the 2 should I use?

[socratis]

OK, I meant make them match to the output of the "VBoxManage list usbinfo". Sorry for the mixup. So, yes, keep VendorID=0951 and ProductID=1607. Delete the rest of the values from the filter and put anything you want for the "Name". One of mine is named "TDK BigOne Black-Green" for example just to make it easier to distinguish.

[gwilki]

I tried that, Socratis, with both the Kingston stick and a different manufacturer's stick. No joy. The windows vm could not see either of them, even though virtualbox did.

One thing - maybe not relevant - I just noticed that in Device Manager, under "other devices", there is a "base system device" showing an error. The error is that there are no drivers loaded for it. Could this be relevant to the USB problem?

Isn't it the wee hours of the morning where you are?

[socratis]

Starting from the last one, yes, it 05:20 over here. Smart observation I had too much coffee and I had to catch up on some movies. Then, insomnia kicked in...

I'll give you the full blown list of step to do. Don't get scared from its length. It tries to cover everything possible, and you've already done most of the steps already. Actually due to <1> below (keep reading) I should amend the list, and you should do this before anything else:

1. Uninstall VirtualBox. Your VMs will be safe.
2. Right-click on the VirtualBox installer and select "Run as Administrator". Choose NOT to run VirtualBox at the end of the installation.
3. Launch VirtualBox as you would normally.

Follow the steps below. If there is a failure, please state which step failed:

1. Make sure that the Extension Pack is installed on the host. The same version as VirtualBox. You can double-check with "VBoxManage --version" for VirtualBox and "VBoxManage list extpacks" for the ExtPack.
2. Make sure that at least USB 2.0 is enabled in your VM settings.
3. Create a USB filter in your guest settings while the device is plugged in the host. Delete all values except Name, VendorID and ProductID. Check also http://www.linux-usb.org/usb.ids to make sure that you have the numbers correct.
4. Unplug the device.
5. Start your guest (the one that you applied the filter to). Let it start completely. Log in if you have to.
6. Plug your device. The filter should capture it and pass control to your guest. You might get a "New hardware found" wizard on the guest, that's normal.
7. If the device shows up in your host and is not captured by the filter, either the filter is incorrect, or there might be a problem with your filter installation.
8. If the device shows up, but as unavailable, "eject" it from your host (if you can), but leave it plugged in. It should show up as available.
9. Are you by any chance using a USB 3.0 port?
10. Is the VirtualBox USB Driver installed in your host? Make sure your host didn't silently reject non-MS drivers (Google for Driver Signature Enforcement). <1>
11. If on a Linux host, are you a member of the 'vboxusers' group? If not, add yourself with "sudo usermod -a -G vboxusers <your_username>", then reboot.
12. If on a Linux host, run "sudo update-usbids".
13. Check out these Windows-specific ways to troubleshoot potential driver installation issues:
    1. USB not working
    2. SOLVED: Failed to access the USB subsystem on Windows 7 host
    3. Remove Driver Filters to Resolve Device Manager Errors on Windows 7
14. With the USB device plugged in and the VM not running, post the output of the following commands:

        VBoxManage list usbhost
        VBoxManage showvminfo "Your_Virtual_Machine_Name"

[gwilki]

I'll follow your instructions in the morning and get back to you. My shift starts in an hour.

[socratis]

1) Have a good shift. I'm going in the office in about three hours.
2) Fix that error in the device manager. Or at least look for the device IDs so you'll know exactly what it is that it fails.
We'll continue later...

[gwilki]

I'm back, Socratis

Here are the results. Still no joy.

There were no failures when re-installing virtualbox. All went well. I installed the pack. It is the same number as the VB itself.

USB 2.0 is enabled.

I created a new filter for the USB stick. I deleted all values except the 3. I went to the site you linked to.There are many Kingston Data Traveller settings, so I tried them all. None made things better. All except the ones that were originally installed by VB resulted in the stick being seen by the Host even when the Guest was running, leading me to conclude that that ones that the VB sees automatically are the correct ones.

The port is 2.0

When I first plugged the stick into the port after the re-install, and with the VM running, the host returned a message saying that it was installing the Virtualbox USB driver, and that the device was ready to use. I don't know where to look on the host to see if that worked. I read the articles about windows rejecting uncertified drivers, but that does not seem to have happened. Where can I look to see if they are really loaded?

I have not yet found the solution to the "base system device" driver not loaded issue. Still looking.

So, there we are. I am going to read the links that you posted at the end of your last message, and proceed from there. I'll let you know my results.

Grant

[gwilki]

Socratis

Success!!!

In the first of your 3 links, a post by nayasis contained instructions to delete an entry in the host registry for "upperfilters". I deleted it (saving the registry entry first), restarted the host, opened virtualbox and the VM, inserted the usb stick and the guest saw it and presto, all is well. I tried with 3 different usb sticks. In each case, first the host reports loading a virtualbox driver, then the guest sees it (after I install the filter) and loads the appropriate drivers.

I want to thank you very much for the time you put into this and for your patience.

For me, this whole exercise is to be able to run a couple of pieces of older hardware that only have 32 bit drivers available. I didn't want to take my host back to 32 bit and thought that a VM would be the way to go. Each of these hardware items are USB devices, so I figured that I would start "simple" with a USB stick. It clearly was far from simple, but I am now confident that I can move on to the hardware devices.

Take care, Socratis.

[socratis]

Hey, glad you figured it out! As I said, the list is long, but I've sort of expanding it throughout the years to cover pretty much everything, even the rare cases.