If you suspect FA04 is a fingerprint reader (common on old Lenovo ThinkPads or HP EliteBooks):
Before fixing the problem, we must understand what we are looking at.
After cross-referencing with multiple driver databases (Microsoft Update Catalog, PCI ID Repository, and Linux lsusb dumps), the Alcor Micro FA00/FA04 device maps most frequently to:
Thus, when you say "alcor micro unknown fa00 f w fa04 work" – you are likely trying to get a USB-connected smart card or memory card reader operational.
Once you have installed the correct driver:
Alcor Micro designed this so that the main interface (FA00) stays alive (for firmware control, power management), while FA04 can be power-cycled independently – saving energy and reducing wear on the card slots. Most people don’t know about it, so manually triggering it feels like a hidden "easter egg." alcor micro unknown fa00 f w fa04 work
If you’re instead trying to make a non-working FA04 appear (e.g., after a driver conflict), the feature to attempt is logical LUN reset rather than physical replugging.
The error "Alcor Micro Unknown [FA00] - F/W FA04" indicates a firmware or controller issue on a USB flash drive, typically identifying it as an AU6989SN-TA or AU6989SNCS-TA controller. This error usually occurs when the drive's firmware is corrupted, leading it to report generic identifiers like VID 058F and PID 1234 instead of its actual specifications. Troubleshooting Steps
To resolve this using AlcorMP (Mass Production Tool), follow these specific actions: Configure Driver Settings: Open AlcorMP and locate the Driver button.
Manually enter the VID/PID as 058F and 1234 (or the specific IDs shown by your device). Click Add VID/PID, then select Save InstallDrive. Detection & Test-Mode: Plug the USB drive into your computer.
If the drive is not detected, you may need to manually switch it into "test-mode" (this often involves shorting specific pins on the controller chip, though this is risky and usually a last resort). Click Refresh (R) in AlcorMP if it still doesn't appear. Firmware Repair: If you suspect FA04 is a fingerprint reader
Once detected, use AlcorMP to perform a High Level Format or Low Level Format.
Note: Low-level formatting may significantly reduce reported capacity if the tool detects bad sectors. Common Causes
Firmware Mismatch: The controller "FA00" is often a placeholder for unknown or generic Alcor controllers.
Hardware Failure: If AlcorMP cannot identify the Flash ID (FID), the drive may have a mechanical or electrical failure that software cannot fix.
Counterfeit Hardware: Some drives reporting these generic IDs are "no-name" or fake capacity drives that use Alcor controllers to spoof storage limits. "F W" : Likely stands for Firmware –
For standard drive errors without firmware corruption, tools like DiskGenius can be used to check for bad sectors or rebuild partitions.
Do you have the Flash ID (FID) or the specific VID/PID from a tool like ChipGenius to help identify the exact firmware needed? fake HP usb flash drives - HP Support Community - 5995925
It looks like you’re asking for a blog post based on a very specific technical string: “alcor micro unknown fa00 f w fa04 work.”
This appears to be related to a hardware ID, a device manager error (likely from Windows), or a driver issue for an Alcor Micro chipset (often used for card readers, USB hubs, or fingerprint readers).
Since this reads like a troubleshooting query, I’ve written a blog post aimed at users who see this in their Device Manager and want to fix it.
Right-click the device → Update driver → Search automatically for drivers.
Result: 90% of the time, Windows says it found nothing. Move to Method 2.