USB drive won’t format in Windows: recover files and rebuild it safely

When Windows detects a USB flash drive but cannot format it, the correct first move depends on one question: does the drive still contain important files? If it does, stop formatting and repair attempts because every write can reduce recovery options. If the data is disposable or safely copied, inspect detection in Disk Management and reserve DiskPart for the final, destructive stage.

The documented case involves a removable drive detected by Windows 8, a failed format attempt, checks in Disk Management and with chkdsk, inspection in Device Manager, consideration of recovery software, and a final DiskPart rebuild. The observed procedure demonstrates completion of clean, create partition primary, format fs=ntfs quick and assign. This result does not demonstrate that a lost file was restored or that the flash memory remained reliable afterward.

Decide first: save data or reset the drive?

A quick format creates new file-system structures, while DiskPart clean removes partition information from the selected disk. Neither operation is a recovery technique. A drive that disconnects, reports an inconsistent capacity, becomes unusually hot, or disappears on several computers may have a hardware fault. Repeated writes are inappropriate when the data matters.

A safe five-step procedure

1. Preserve data and freeze the diagnosis

   Disconnect and reconnect the drive once through a USB port directly attached to the computer rather than a hub. Record the exact message, reported capacity, and any drive letter. If File Explorer can still read folders, immediately copy important files to another disk. Copy rather than move them, and never write recovered material back to the source drive.

   Stop here when the data is irreplaceable. A sector image produced by a recovery specialist is safer than repeated in-place repairs. The documented case begins with a failed format attempt; that approach is reasonable only when data loss has already been accepted.

   

2. Identify the flash drive precisely in Disk Management

   Open the Windows quick-access menu and choose Disk Management, or run diskmgmt.msc. Identify the removable device by its approximate capacity and by observing which disk appears when it is connected. A letter such as G: can change and is never sufficient evidence on its own. Note whether the space is healthy, unallocated, RAW, or absent.

   Microsoft documents Disk Management as the built-in tool for creating and formatting volumes and assigning drive letters. The documented example uses a removable drive of about 14.44 GiB; this value belongs only to that demonstration. Your device may be different. Do not delete a volume until the system disk and every other attached drive are unmistakably excluded.

   

3. Separate file-system corruption from device failure

   When Windows assigns a letter and can lock the volume, open an elevated Command Prompt and first run chkdsk X:, replacing X with the observed letter. Without a repair option, this reports status. chkdsk X: /f attempts to correct logical errors and changes the volume, so use it only after backup or when loss is acceptable. Microsoft notes that /f must lock the disk.

   In Device Manager, confirm that the USB storage device appears without a persistent error. Trying another direct port and another computer helps separate the drive from the local USB controller. Removing the device entry and asking Windows to detect hardware again can renew the built-in driver association, but it cannot repair failing flash memory. Avoid unofficial driver-download sites.

   

4. Recover files before rebuilding the partition

   If the volume will not mount but capacity remains stable, a recovery utility may search old structures and file signatures. Install the application on the internal disk, scan the USB source, and save results to a separate healthy destination. Never use the damaged drive as the recovery destination because new writes can overwrite recoverable material.

   The analysis includes EaseUS Data Recovery Wizard, displays scan results, visits the Recuva page, and checks an installer with VirusTotal. No verified restoration is established. These results indicate evaluation of recovery options, not successful recovery. A listed file may still be incomplete, corrupted, or unreadable. For unique or business-critical data, a recovery laboratory is safer than cycling through utilities.

   

5. Rebuild with DiskPart only as a last resort

   This stage destroys the partition structure of the selected disk. Close applications, disconnect other removable media, and open Terminal or Command Prompt as administrator. Start diskpart, then run list disk. Identify the USB device by capacity and enter select disk N. Run detail disk and recheck model, size, and volumes. If anything does not match, type exit and stop.

   diskpart
   list disk
   select disk N
   detail disk
   clean
   create partition primary
   format fs=exfat quick
   assign
   exit

   exFAT is often appropriate for a flash drive shared between Windows, macOS, and many current devices. NTFS can suit Windows-focused use, while FAT32 improves support for some older equipment but limits individual files to 4 GiB. This example uses NTFS; that is not a universal requirement. After assign, copy a few non-critical files, safely eject the drive, reconnect it, and read them back. Immediate success does not guarantee long-term flash health.

   

What each DiskPart command does

What the final result actually proves

Directly observed result

In the documented case, DiskPart confirms cleaning, partition creation, 100-percent completion of the quick format, and drive-letter assignment. File Explorer then displays the removable drive. This establishes a logical return to service during the observed procedure.

Evidence limits

The available result includes no extended full-capacity integrity test, speed measurement, or repeated write-and-read cycle. It cannot establish long-term reliability. Replace a drive that repeatedly becomes RAW, switches to read-only mode, disappears, or corrupts files even when another format succeeds.

Frequently asked questions

Why does Windows ask to format the flash drive?

Windows may detect the USB device while failing to understand its partition or file system. Possible causes include removal during a write, logical corruption, damaged partition information, or failure of the controller or flash memory.

Can clean repair defective hardware?

No. It resets partition information on the selected disk. It cannot repair worn flash cells, an unstable controller, or a damaged connector.

Can I format the drive immediately?

Only after selecting the correct partition or creating the intended one, and only after recovery is no longer required. A valid command executed against the wrong disk remains catastrophic.

Sources and traceability

• Microsoft Support — Disk Management in Windows, accessed October 18, 2026.
• Microsoft Learn — chkdsk, accessed October 18, 2026.
• Microsoft Learn — diskpart, accessed October 18, 2026.