Opened 12 years ago

Closed 8 years ago

Last modified 7 years ago

#10526 closed defect (obsolete)

USB Memory Stick (SanDisk Cruzer 16GB) not recognized if VirtualBox Manager started

Reported by: micado Owned by:
Component: VM control Version: VirtualBox 4.1.14
Keywords: USB SanDisk Cruzer Cc:
Guest type: Windows Host type: Windows


Host: Windows 64/7
Guest: no VM started
USB Stick: SanDisk Cruzer 16GB, FAT32

Description a)

  • Oracle VM VirtualBox Manager started (no VM started).
  • trying to connect USB SanDisk Cruzer 16 GB to host computer.

=> The stick is not recognized by Windows 7/64 but the connection sound appears. The volume letter is not present to the host system. The Windows Disk management utility does not show any information for minutes about any drive (tries continously to connect to the virtual disk management service). After a while the utility shows all information but the SanDisk Cruzer stated with "no Medium".

Trying to connect any other USB Memory Stick: no problem

Description b)

  • Oracle VM VirtualBox Manager not started (no VM started).
  • connect SanDisk Cruzer

=> no problem

=> no problem

It seems that the VM VirtualBox Manager disables the ability to proper connect the SanDisk Cruzer only. This happens to other VB releases too.

Attachments (1)

Disk Management.png (67.2 KB ) - added by micado 12 years ago.
Disk Management, problem with SanDisk Cruzer (Drive E:)

Download all attachments as: .zip

Change History (8)

by micado, 12 years ago

Attachment: Disk Management.png added

Disk Management, problem with SanDisk Cruzer (Drive E:)

comment:1 by Michael Blahay, 12 years ago

I am experiencing this with an older 8gb Cruzer. Other memory sticks do not have this problem.

comment:2 by jeffminton, 10 years ago

This still occurs for me with version 4.3.12 and a sandisk cruzer fit 16Gb

comment:3 by Frank Mehnert, 10 years ago

jeffminton, do you have set any USB filter?

in reply to:  3 comment:4 by pFa, 10 years ago

Host: Windows 64/7 (same as above)
Guest: no VM started (same as above)
VirtualBox Manager: 4.3.20 r96997
USB Stick: SanDisk Cruzer 32GB, FAT32 (32GB instead of 16GB as reported by micado and jeffminton)

Description A

  • Oracle VM VirtualBox Manager not started (and no VM started at all)
  • plug in the USB SanDisk Cruzer 32GB FAT32

=> no problem

  • plug in another SanDisk Cruzer 64GB exFAT

=> no problem

  • eject the SanDisk Cruzer 32GB
  • eject the SanDisk Cruzer 64GB

Description B

  • Invoke Oracle VM VirtualBox Manager without launching any VM


  • plug in the SanDisk Cruzer 32GB FAT32

=> problem. This memory stick seems to be instantly trapped by VirtualBox

Invoke mmc devmgmt.msc
The MS-Windows device manager reports an error: This device cannot start. (Code 10)

Invoke eventvwr /c:System
The system log reports

  1. A problem has occurred with one or more user-mode drivers and the hosting process has been terminated. This may temporarily interrupt your ability to access the devices.
  2. The device xxx (location (unknown)) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.

Now plug in the other SanDisk Cruzer 64GB exFAT
=> no problem

  • quit / close VirtualBox Manager
  • eject the SanDisk Cruzer 32GB
  • eject the SanDisk Cruzer 64GB
  • repeat description A (see above)

=> all works fine back again.

In short, it looks like a bug in "VirtualBox USB user-mode driver"

Version 0, edited 10 years ago by pFa (next)

comment:5 by aeichner, 8 years ago

Resolution: obsolete
Status: newclosed

Please reopen if still relevant with a recent VirtualBox release.

comment:6 by Duane Jenson, 7 years ago

I am still seeing this with a SanDisk Cruzer 64G thumb using VB 5.1 on Ubuntu with a Windows 7 guest.

comment:7 by Richard Scott, 7 years ago

I'm also getting this on Ubuntu 16.04, with VB 5.1.14 r112924. Here is the output from lsusb:

# lsusb 
Bus 001 Device 003: ID 0000:7777  

However, I can partition the disk with the Host system running VM but the superblock is corrupted so I can't mount it.

dmesg has this to say on it:

[ 3033.039708] JBD2: no valid journal superblock found
[ 3033.039717] EXT4-fs (sdc1): error loading journal

I've just mounted AND formatted the disk with EXT2, but it still won't show up in VB.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use