Seeing your cloning software freeze at 99 percent with the progress bar barely moving, the time remaining stuck on 00:00:00, and the drive activity light either solid or completely dark is one of the most frustrating SSD upgrade moments. In most cases the clone has copied your Windows partition and boot files successfully but is now hung on the final verification, partition resizing, or bad sector retry at the very end of the disk. The good news is this rarely means your data is lost.
How urgent is it? If the source drive is still healthy, you can safely cancel, power down, and try again without harming the original Windows installation. Do not force-shutdown repeatedly or unplug the target SSD mid-write if the activity light is still flashing rapidly, as that can corrupt the destination’s file system. As of 2026, most modern cloning tools will resume or safely abort if you use the built-in Cancel button and wait 2 to 5 minutes for disk activity to settle. The fixes below are ordered from quickest and safest to more involved, so start at the top.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Background scan locking files (antivirus, OneDrive, Windows Search) | Task Manager shows Antimalware Service Executable, OneDrive.exe, or SearchIndexer.exe with high disk usage; clone log says “cannot lock volume” or “access denied” | Easy |
| Bad sectors or file system errors on source drive | Run chkdsk – it reports “bad sectors,” “bad clusters,” or “errors found”; Event Viewer > Windows Logs > System shows disk errors with Source: disk or Ntfs | Easy |
| Target SSD too small or partition size mismatch | Disk Management shows source used space larger than target, or an EFI/System Reserved partition that won’t shrink; cloner warns “not enough space” or “failed to resize partition” | Moderate |
| Unstable USB connection or enclosure | Cloning via USB 3.0 adapter/enclosure and progress stalls at 99% with drive disconnect sound; Device Manager shows drive disappearing and reappearing | Moderate |
| Sector-by-sector clone enabled or trim/BitLocker conflict | Cloning settings show “Sector-by-sector,” “Forensic,” or “Exact copy” checked; source drive shows BitLocker padlock icon in File Explorer > This PC | Moderate |
| Outdated SSD firmware, storage driver, or BIOS | Samsung Magician, Crucial Storage Executive, or WD Dashboard shows firmware update available; BIOS version predates your motherboard’s NVMe compatibility updates | Advanced |
Fix 1: Let It Finish and Cancel Safely If Needed
What causes it
The last 1 percent is not always copying user files. Most cloners verify written data, finalize the Master Boot Record or GUID Partition Table, and expand the main partition to fill the target drive. On large drives this final step can take 10 to 30 minutes with no visible progress, which looks like a freeze.
How to check
Press Ctrl + Shift + Esc to open Task Manager, go to the Performance tab, and click Disk. If Disk Active Time for the target SSD is still 80 to 100 percent and Write speed shows activity above 0 KB/s, the clone is still working. If Disk Active Time is 0 percent for more than 15 minutes and the elapsed time counter in your cloning software has not changed, it is truly stuck.
What to do
Wait at least 20 minutes after it hits 99 percent before intervening. If it remains stuck, click Cancel or Stop inside the cloning application once and wait. Do not click End Task yet. Press Windows + R, type resmon.exe, open the Disk tab, and confirm there is no active write to the target drive letter. Then close the cloning software normally. Shut down the PC via Start > Power > Shut Down, not by holding the power button, and disconnect the target SSD for 30 seconds.
How to undo it
No change to undo. If you canceled cleanly, your source drive is untouched. Reconnect the target SSD and you can retry or apply the fixes below. If the target shows as RAW or unallocated, you will reformat it in Fix 4 before retrying.
Fix 2: Stop Programs That Lock the Source Drive
What causes it
Real-time antivirus, OneDrive sync, Steam, and Windows Search keep files open and prevent the cloner from getting an exclusive lock on the source volume. The software retries continuously at the end of the job, which presents as 99 percent stuck.
How to check
Press Ctrl + Shift + Esc and check the Processes tab. Look for Microsoft Defender Antivirus Service, Avast Antivirus, OneDrive, Dropbox, Google Drive, Steam, or Search Indexer near the top of the Disk column. Also open File Explorer > This PC and see if any file shows a blue syncing icon or if your antivirus shows an active scan notification.
What to do
1. Pause OneDrive: Click the OneDrive cloud icon in the taskbar tray > gear icon > Pause syncing > 2 hours. Repeat for Dropbox or Google Drive if installed.
2. Pause antivirus: Open Windows Security > Virus & threat protection > Manage settings > toggle off Real-time protection. For third-party antivirus, right-click its tray icon > Pause protection / Disable for 1 hour.
3. Disable search temporarily: Press Windows + R, type services.msc, find Windows Search, right-click > Stop.
4. Close all open apps, especially browsers, games, and Outlook, then retry the clone. Do not browse the source drive during cloning.
How to undo it
Re-enable Real-time protection in Windows Security > Virus & threat protection > Manage settings and set it back to On. Go to services.msc > Windows Search > right-click > Start and set Startup type back to Automatic. Unpause OneDrive by clicking the tray icon > Resume syncing.
Fix 3: Repair Source Drive File System Errors and Bad Sectors
What causes it
Logical file system corruption or a few bad sectors on the aging source HDD or SSD cause the cloner to retry reading the same blocks thousands of times. It copies 99 percent quickly, then loops on the damaged area at the end of the disk.
How to check
Press Windows + X > Terminal (Admin) or Windows PowerShell (Admin). Type chkdsk C: and press Enter without the /f flag to run a read-only scan. If it reports “Errors found” or “Bad sectors found,” the source needs repair. Also check Event Viewer: Press Windows + R, type eventvwr.msc, go to Windows Logs > System, and filter for Source: Ntfs, disk, or Disk.
What to do
1. Run a full repair: In the admin Terminal, type chkdsk C: /f /r /x and press Enter. If Windows says the volume is in use, type Y to schedule at next restart, then restart the PC and let the scan complete. This can take 30 minutes to several hours depending on drive size.
2. For health info, press Windows + R, type cmd, then type wmic diskdrive get status, model. If Status is not OK, back up immediately.
3. Delete obvious junk before retrying: Press Windows + R, type cleanmgr.exe, select C:, click Clean up system files, check Temporary files, Thumbnails, and Recycle Bin, then click OK.
4. Empty the Recycle Bin and clear the Downloads folder if it contains large incomplete files. Retry cloning after the repair finishes.
How to undo it
Chkdsk repairs are not reversible, but they are safe. If chkdsk moves corrupt files to C:\found.000, you can inspect that folder and delete it after confirming Windows boots normally. No settings need to be reverted.
Fix 4: Make Sure the Target SSD Has Usable Space
What causes it
Cloning fails at the end when the target is technically smaller, even by a few megabytes, or when unmovable system partitions like the 100 MB EFI System Partition or 500 MB Recovery Partition cannot be resized automatically to fit. A 512 GB source to 500 GB target or a drive with 460 GB used on a 480 GB target will stall during partition resizing.
How to check
Press Windows + X > Disk Management. Compare the source Disk 0 and target Disk 1 layouts. Note the total capacity in GB and the amount of Used space on C: in File Explorer > This PC. If Used space on the source exceeds 85 to 90 percent of the target’s total capacity, space is tight. Also check if Disk Management shows the target as having no Unallocated space after the clone attempt.
What to do
1. Shrink the source C: partition: In Disk Management, right-click the C: partition on Disk 0 > Shrink Volume. Enter an amount to shrink so that the total used plus 15,000 to 20,000 MB free space fits comfortably on the target. For example, shrink by 20480 MB for 20 GB of breathing room. Click Shrink.
2. Wipe the failed target: In Disk Management, right-click each partition on the target Disk 1 > Delete Volume until it shows as fully Unallocated. If Delete Volume is grayed out, open an admin Terminal and run diskpart > list disk > select disk 1 (verify the size matches the target) > clean > exit.
3. In your cloning software, choose the option “Resize partitions to fill disk” or “Fit partitions to entire disk” and ensure “Sector-by-sector” is unchecked. Then start the clone again.
How to undo it
If you shrank C: too much, return to Disk Management, right-click C: > Extend Volume > Next > Next > Finish to reclaim the unallocated space. No data is lost by shrinking unless the drive was already critically full.
Fix 5: Use a Direct Internal Connection Instead of USB
What causes it
Cheap USB-to-SATA bridges, USB hubs, and front-panel USB ports provide inconsistent power and can overheat or throttle during long writes. The drive drops for a fraction of a second, the cloner loses the write handle, and it stalls at 99 percent waiting for the drive to respond.
How to check
If the target SSD is connected via a USB enclosure, USB adapter cable, or docking station, this is a prime suspect. Open Device Manager: Press Windows + X > Device Manager > expand Disk drives and Universal Serial Bus controllers. If you see Unknown USB Device or the target drive vanishes when you wiggle the cable, the connection is unstable.
What to do
1. Power down the PC fully and switch the target SSD to an internal connection. For a 2.5-inch SATA SSD, use a direct SATA data cable to a motherboard SATA port and a direct SATA power cable from the power supply, not a splitter. For an M.2 NVMe SSD, install it in the motherboard M.2_1 or M.2_2 slot and secure it with the standoff screw, then set PCIe mode to Auto in BIOS if prompted.
2. If you must use USB, plug the enclosure directly into a rear USB port on the motherboard, not a hub or front case port. Use the cable that came with the enclosure, preferably USB 3.2 Gen 2 or Thunderbolt, and lay the enclosure on its side for airflow.
3. Enter BIOS by pressing Del or F2 during boot, go to Main or Storage Configuration, and verify both drives are detected. Save and exit, then retry the clone from within Windows or from bootable media.
How to undo it
Move the drive back to the USB enclosure after cloning and successful booting if that is your intended external use. Reconnect SATA cables as before. No software setting needs to be changed.
Fix 6: Disable Sector-by-Sector Cloning, BitLocker, and Trim
What causes it
Sector-by-sector mode copies every sector including empty space and bad blocks, which dramatically increases time and failure rate at the end of the disk. BitLocker encryption and an active Trim command queue can also block final writes to the target SSD.
How to check
Open your cloning software settings screen before starting. Look for checkboxes labeled Sector-by-sector clone, Forensic clone, Exact copy, or Copy all sectors. If any are checked, that mode is on. For BitLocker, open File Explorer > This PC and look for a padlock icon on C:. Press Windows + R, type manage-bde -status into an admin Terminal to confirm Protection Status.
What to do
1. Uncheck Sector-by-sector / Forensic mode in the cloner. Select Intelligent clone, Used sectors only, or Copy only used space.
2. Suspend BitLocker: Press Windows + S, type Manage BitLocker, open it, click Suspend protection > Yes for the C: drive. Do not decrypt fully unless instructed, suspending is enough.
3. Turn off scheduled defragmentation/optimization during the clone: Press Windows + S, type Defragment and Optimize Drives, open it, select the source drive, click Change settings > uncheck Run on a schedule > OK.
4. Retry the clone. After success, re-enable BitLocker and optimization.
How to undo it
Open Manage BitLocker > Resume protection. Open Defragment and Optimize Drives > Change settings > check Run on a schedule > set to Weekly > OK. Leave Sector-by-sector unchecked for future clones unless you need a forensic copy.
Fix 7: Update SSD Firmware and Storage Drivers
What causes it
Early firmware on many NVMe drives has known stalls when handling sustained sequential writes or when the SLC cache fills near the end of a full-disk write. Old Intel RST, AMD StoreMI, or Microsoft NVMe drivers can also hang on the final flush.
How to check
Install the maker’s toolbox: Samsung Magician, Crucial Storage Executive, WD Dashboard, SK Hynix Drive Manager, or Intel Memory and Storage Tool. Open it and check Drive Details > Firmware Version > Update. In Device Manager > Storage controllers, note the driver name and date. Press Windows + R, type msinfo32, and check System Summary > BIOS Version/Date to see if an update is available from your motherboard support page.
What to do
1. Back up important files before any firmware update.
2. In the toolbox, click Firmware Update > Update > follow the prompt and do not power off during flashing. The PC will restart automatically.
3. Update storage drivers: In Device Manager, right-click Standard NVM Express Controller or Intel Chipset SATA RAID Controller > Update driver > Search automatically for drivers. Alternatively, install the latest chipset driver from your motherboard vendor’s support site under Drivers > Chipset.
4. Retry cloning after both updates and a reboot.
How to undo it
Firmware updates cannot be rolled back and generally should not be. If you installed a new chipset driver and see instability, go to Device Manager > Storage controllers > right-click the controller > Properties > Driver tab > Roll Back Driver.
If Nothing Works
If none of the fixes above move past 99 percent, switch to an offline clone and then verify boot. Create bootable rescue media from your cloning tool: In the app, go to Tools > Create Bootable Media or Rescue Media > create a USB drive. Shut down, disconnect all extra drives except the source and target, boot from the USB by pressing F12, F8, or Esc at startup to open the Boot Menu, and run the clone outside Windows where no file locks interfere.
After an offline clone, test the target before wiping the source. Power down, disconnect the original source drive completely, leave only the cloned SSD on the primary SATA port or M.2_1 slot, and boot. If Windows starts, press Windows + R, type diskmgmt.msc, and confirm the EFI System Partition, C: partition, and Recovery Partition are present and healthy. If the clone still hangs even offline, do a clean Windows install on the target and migrate files manually: Use File History or copy C:\Users\YourName\Desktop, Documents, Pictures to an external drive, then reinstall apps. Your original drive remains untouched and bootable as a fallback.
FAQ
Can I turn off the PC when cloning is stuck at 99 percent?
Do not hold the power button while the drive activity LED is still flashing. First click Cancel in the cloning software and wait 3 to 5 minutes. Open Resource Monitor via Windows + R > resmon.exe > Disk tab to confirm zero write activity to the target disk. Then use Start > Power > Shut Down. This avoids file system corruption on the target. The source drive will still boot normally.
How long should I wait at 99 percent before I assume it is frozen?
Wait at least 20 to 30 minutes on an HDD source or 15 minutes on an SSD source. Check Task Manager > Performance > Disk for sustained activity. If write speed is 0 KB/s for 15 continuous minutes and the elapsed time in the cloner has not advanced, it is safe to treat it as frozen and cancel as described above.
Will a stuck clone corrupt the original drive?
No, cloning is read-only on the source. Even if the target clone fails or you cancel, the source Windows installation is not modified unless you ran chkdsk /f /r, which only repairs errors. You can reboot from the source drive immediately after a failed clone to confirm it still boots. Keep the source disconnected only when you are testing whether the new SSD boots on its own.
Why does cloning stick at 99 percent but a clean install works fine?
A clean install writes fresh file system structures, while a clone must copy every existing file, partition layout, and boot loader exactly, retrying on any unreadable cluster. Fragmentation, a nearly full Recovery Partition, BitLocker, or a failing sector at the end of the disk will block a clone but not a fresh install. Fixing file system errors with chkdsk, freeing 15 to 20 GB, and using Intelligent clone instead of sector-by-sector usually resolves this difference.
