Usb Device Id Vid 058f Pid 1234 !!exclusive!! Full -
0 MB on a 32GB USB stick - Storage Devices - Linus Tech Tips
Extremely inexpensive; often given away for free as promotional items.
Do not use generic "driver updater" tools. Instead, get the official driver:
You may need to manually disassemble the physical drive and short-circuit the memory pins (typically data lines 29 and 30) using a needle during plug-in to force the controller into hardware test mode. usb device id vid 058f pid 1234 full
While 1234 is the official Product ID assigned to this hardware, it is worth noting that in software development and testing, 1234 is often used as a placeholder ID. However, in the context of Alcor Micro (VID 058F ), this is a legitimate hardware identifier for their card reader controllers.
Download a specialized hardware diagnostic tool such as or ChipGenius from specialized repositories like USBDev . Insert your drive and run the tool to obtain an analysis report like this:
When a device with these IDs is connected, it generally reports the following hardware profile: Vendor ID (VID): (Alcor Micro Corp.) Product ID (PID): Manufacturer: Product Model: USB Flash Disk / Mass Storage Device Common Controllers: Alcor Micro AU6986, AU6988, or AU6989SN series USB Version: USB 2.0 (High Speed) Common Use Cases and Problems 0 MB on a 32GB USB stick -
: Often appears as "Generic" or "Mass Storage Device" in system reports.
To safely diagnose and attempt to fix a device registered under this specific ID, follow these technical verification steps:
Sometimes the kernel will report [sdb] Media removed, stopped polling or Buffer I/O error on dev sdb, logical block 0 . These messages indicate that the controller cannot read the NAND flash parameters properly. In such cases, low‑level tools like hdparm , sg_format , or are required, because standard Linux partition tools ( fdisk , gparted ) cannot communicate directly with a uninitialized Alcor controller. While 1234 is the official Product ID assigned
If your computer detects the drive but cannot access it, the following steps are commonly used by the tech community: Driver Reinstallation: Windows Device Manager to uninstall the "USB Mass Storage Device" entry under Universal Serial Bus controllers
These symptoms are often accompanied by system log entries such as:
