Be a Freelance Blogger

Make REAL money blogging for hire.

To get your Alcor Micro unknown FA00 F/W FA04 device to work, you generally need to address a firmware identification error or a driver conflict. This specific combination of identifiers (FA00 controller with FA04 firmware) often appears when a USB flash drive or card reader is in a "stalled" state, showing 0 bytes or "No Media" in Windows. Understanding the Error

The "FA00" identifier is often a generic placeholder for Alcor controllers like the AU6989SN-TA or AU6989SNCS-TA

when the system cannot properly read the Flash ID (FID). "FA04" typically refers to the specific firmware version loaded onto that controller. When these appear together as an "unknown device," it usually means the hardware is functional, but the software communication has broken down. Step-by-Step Fixes to Get It Working 1. Reinstall the Driver via Device Manager

Before attempting complex firmware flashes, try a clean driver reset: Open Device Manager (Win + X). Expand Universal Serial Bus controllers or Memory technology devices. Right-click the Alcorlink USB 2.0 Card Reader or the "Unknown Device" and select Uninstall device.

Check the box to Delete the driver software for this device if available.

Restart your computer. Windows will attempt to reinstall a fresh generic driver upon reboot. 2. Use Manufacturer-Specific Drivers

Generic Windows updates can sometimes cause Alcor devices to stall. If you are on a laptop, download the official OEM driver:

HP Users: Visit the HP Software and Driver Downloads page. Search for "Alcorlink Card Reader" under the Storage or Chipset category for your specific model.

Dell Users: Use the Dell Support site to identify your system and download the "Memory Card Reader" driver under the Chipset section. 3. Firmware Restoration (For USB Flash Drives)

If the device is a flash drive showing 0 bytes, you may need a Mass Production (MP) tool to "re-stitch" the firmware: Identify the exact controller using a tool like ChipGenius. Download the corresponding version of AlcorMP (e.g., AlcorMP 16.11.01.MD

In the tool settings, try setting Scan Mode to "Low Level Format" and MP Mode to "Capacity Optimize". Warning: This process will erase all data on the device. 4. Disable USB Selective Suspend

Power management settings can sometimes prevent Alcor readers from "waking up" properly: Go to Control Panel > Power Options > Change plan settings. Click Change advanced power settings.

Expand USB settings > USB selective suspend setting and set it to Disabled. Quick Troubleshooting Checklist Potential Solution 0 MB / No Media Use AlcorMP tool to reflash firmware. Yellow Warning ! Uninstall driver and restart. Not Detected Try a different USB port (preferably USB 2.0). Code 47 Physically unplug the device and plug it back in.

0 MB on a 32GB USB stick - Storage Devices - Linus Tech Tips

Troubleshooting Alcor Micro Unknown FA00 F/W FA04: A Comprehensive Guide

If you’ve connected your USB flash drive only to be met with a generic "Mass Storage Device" label and a technical report identifying the controller as Alcor Micro Unknown [FA00] with F/W FA04, you are likely dealing with a firmware corruption or a "fake" drive recovery scenario. This specific identifier—FA00 with firmware FA04—is a common signature for certain Alcor AU6989 series controllers, often seen in 16GB or 32GB drives.

This guide breaks down what these codes mean and the exact steps to restore your drive using the AlcorMP Mass Production Tool. Understanding the "Unknown FA00" Error

When diagnostics software like ChipGenius or Flash Drive Information Extractor returns these values, it indicates the system cannot properly communicate with the flash controller's logic:

Unknown [FA00]: This is a placeholder ID used when the specific sub-variant of the Alcor controller (likely an AU6989SN-TA or AU6989SNCS-TA) isn't fully recognized by the driver or software version being used.

F/W FA04: This represents the version of the firmware currently active (or corrupted) on the controller chip.

VID 058F / PID 1234: These are the default "recovery mode" IDs for Alcor Micro chips. If you see these, your drive is in a "raw" state and requires a firmware re-flash. Essential Preparation

Before attempting a repair, keep these technical requirements in mind:

Use a 32-bit Windows OS: AlcorMP tools are notorious for stability issues on 64-bit systems. If possible, use Windows 7 32-bit for the highest success rate.

Run as Administrator: The software needs direct low-level access to USB ports.

The "Order" Rule: Always launch the AlcorMP software first, wait for it to load completely, and then insert your flash drive. Step-by-Step Recovery Process 1. Identify the Flash ID (FID)

Open a diagnostic tool to find your Flash ID code. For FA00/FA04 drives, you might see codes like EC3A94C3A4CA (Samsung MLC). This ID is critical for choosing the right version of AlcorMP. 2. Download the Correct AlcorMP Version

General Alcor recovery tools often fail with "Unknown [FA00]" errors. Look for versions released after 2016, such as AlcorMP v16.11.01.MD or later. Users at forums like USBDev.ru and FlashBoot.ru frequently share specific versions that include support for newer FA00 firmware signatures. 3. Configure the Setup (S)

Once the tool detects your drive (often showing a colored box), click Setup (S). If prompted for a password, leave it blank or try "0000".

Flash Type Tab: Set this to "Auto" unless you have the specific datasheet for your Samsung or Micron memory.

Mode Tab: Choose Product Mode for a standard repair. Use Sort Mode if the drive has many bad blocks.

Scan Level: For FA00 controllers, Full Scan4 (AutoECC) is often the most reliable for bypassing firmware "Unknown" errors. 4. Execute the Flash

Click Start (A). The process can take anywhere from 10 minutes to over an hour depending on the "Scan Level" chosen.

Success: The box turns green, and your drive will reappear in File Explorer with its real capacity.

Failure (Error 50400/92700): This often means "Too many bad blocks." Try changing the "Scan Mode" to Low Level Format - Half Capacity Check to recover a smaller, stable portion of the drive. Common Issues & Fixes

AlcorMP (Последняя версия ALCOR U2 MP v23.08.07.00.H)

Based on the specific terminology used, this request relates to a common scenario in electronics repair and forensic data recovery involving Alcor Micro USB flash controllers.

Here is a technical write-up regarding the "Alcor Micro Unknown FA00/FA04" issue, what it means, and the work required to resolve it.

A. Lenovo (for fingerprint readers)

  • Search "Lenovo Alcor Micro Fingerprint Driver" – model T440, X250, T450.
  • The driver file name often is alcor_micro_fingerprint_xxxxx.exe. Extract it using 7-Zip – inside, locate the FA04 folder and alcorusb.inf.

Step 3: Source the Exact Driver – The "FA04" Variant

Searching for "Alcor FA04 driver" yields rubbish. Instead, use the following validated sources:

Part 2: Why Isn't It Working? The Driver Void

Windows Update usually handles standard drivers, but the "FA00/FA04" family falls into a grey area. Here is why it remains "unknown":

  1. OEM Customization: HP, Dell, and Fujitsu often buy these chips and customize the firmware. They do not submit drivers to Microsoft's generic catalog.
  2. Legacy Status: This chipset is from the late 2000s / early 2010s. If you are on Windows 10 or 11, the original Vista/7 drivers are present but not automatically assigned.
  3. Confusion with Biometrics: The FA04 variant is sometimes a fingerprint swipe sensor. Windows might try to force a generic Smart Card driver, which fails.

Method 1: Windows Update (The "Hidden" Trick)

Sometimes the driver is there, but Windows doesn't think you need it.

  1. Open Settings > Update & Security > Windows Update.
  2. Don't just click "Check for Updates." Look for the link that says "View optional updates".
  3. Click on Driver updates.
  4. Look for "Alcor Micro" or "Card Reader" in the list. Check the box and install.

The interesting trick:

If the device enumerates as FA00 but not FA04, you can sometimes force FA04 to appear without replugging the hardware by:

  1. Sending a reset command to the FA00 interface (via ioctl on Linux or DevIoControl on Windows).
  2. Triggering a logical re-enumeration – which reinitializes the second LUN without physically removing the USB plug.

This is useful when:

  • The card reader is detected but shows no media slots.
  • After a card removal, the second LUN (FA04) disappears and doesn’t return.