File Copy Stuck at 99% in Windows 10 or 11? Check Drive Space, Connections and Errors

This guide covers Windows 10 and Windows 11. Start with the least disruptive checks: give the copy a little time, confirm that the destination has enough space, and test both ends of the transfer. Then use Windows drive error checking if the problem persists.

Before you cancel the copy​

A large file, a folder containing many small files, or a slow external drive can make the final stage take longer than expected. Give the operation a few minutes, particularly if the copy window still shows activity.

If it remains unchanged and you decide to cancel:

• Select Cancel in the copy window and wait for Windows to stop.
• Keep the original files. A canceled copy may leave incomplete files at the destination.
• If you were moving rather than copying files, inspect both locations before deleting anything; some items may already have moved.

Important: If a drive is repeatedly disconnecting, making unusual clicking noises, or reporting read errors, avoid repeated transfer and repair attempts. Prioritize recovering important files, and consider professional help if the data is irreplaceable.

Check available space on the destination​

The destination drive is where the copied files are supposed to land. It needs enough free space for the data being copied, with some room to spare.

1. Press Windows + E to open File Explorer.
2. Select This PC in the left pane.
3. Find the destination drive and check the free space shown beneath it.
4. For a more detailed view, right-click the drive and select Properties.
5. Right-click the source file or folder, select Properties, and compare its size with the destination’s free space.

If space is tight, remove or move files you no longer need from the destination. Review anything carefully before deleting it. For the Windows system drive, Microsoft also provides storage information under Settings > System > Storage.

A partial copy can itself occupy space. If you are sure which destination files belong to the canceled attempt—and have confirmed the originals are safe—you can remove those incomplete copies before retrying.

Bottom line: Check the actual destination drive, not just the space on C:. Free space on one drive does not help a full drive elsewhere.

Test the source and destination separately​

A small test can help narrow down where the transfer is failing. It is a clue, not a definitive diagnosis.

1. Read from the source. Try opening a file from the source location. Then copy a small, noncritical file from it to a different working location.
2. Write to the destination. Copy a different small, noncritical file from a known-working location to the destination.
3. Compare the results. If reading from the source fails but writing to the destination works, investigate the source. If the reverse happens, focus on the destination.
4. Test the connection. For an external drive, reconnect it and, where practical, try another USB port or compatible cable. Wait until any copy has stopped before disconnecting it.

A successful small-file test does not prove a drive is healthy: the trouble could involve a particular file or a larger transfer. If you are copying over a network, also check that the network connection and shared folder are accessible. A network share may require its owner or administrator to check its storage and permissions.

Check the drive for file-system errors​

Windows includes an error-checking tool in File Explorer. Microsoft documents the following route to it:

1. Open File Explorer and select This PC.
2. Right-click the local or connected drive you want to check, then select Properties.
3. Open the Tools tab.
4. Under Error checking, select Check.
5. Follow the prompts to scan the drive and, if Windows offers a repair, review the instructions before proceeding.

Check the destination first if you suspect a write problem; check the source if files cannot be read. Close files and programs using the drive beforehand. Windows may ask to schedule a repair for a restart if the drive is in use.

Back up important data before repairing a drive whenever possible. A file-system repair is not a substitute for a backup, and a clean scan does not prove the hardware is healthy. Microsoft notes that disk repairs can sometimes cause data loss, particularly when fixing damaged FAT file systems.

This check applies to drives attached to the PC. For a network share, ask the administrator to check the underlying storage on the device hosting it.

Check for a FAT32 file-size limit​

If the destination is a USB drive, open its Properties and look at File system. A drive formatted as FAT32 cannot store an individual file of 4 GiB or larger, even if the drive has plenty of free space. This is a limit on each file, not on the total size of a folder.

If that limit applies, use a suitable destination formatted with a file system that supports larger files, such as exFAT or NTFS, provided it is compatible with the devices that need to use it. Do not format a drive as a quick fix without first backing up its contents: formatting removes the files on it.

Retry and verify the result​

Once you have addressed any space, connection, or drive errors, retry the copy. For a large folder, copying smaller batches can help identify whether one particular file or group causes trouble.

After Windows reports that the copy has finished:

• Compare the source and destination file or folder sizes and item counts in Properties.
• Open several important copied files to make sure they are usable.
• Keep the originals until you are satisfied the destination copy is complete.

Matching sizes and successful spot checks are useful, though they are not a byte-for-byte verification of every file. If the transfer still fails, note the exact error message, the file involved, and whether the source or destination test failed. Those details are much more useful than the 99% progress bar when deciding what to investigate next.