Stuck at 90% complete drive test

Running a hard drive diagnostic test is an important way to check the health and reliability of an HDD or SSD. However, some users encounter a frustrating problem when a drive test reaches 90% completion and appears to stop progressing. The test may remain on the same percentage for a long time, leaving users unsure whether the drive is damaged, the diagnostic software has frozen, or the process simply needs more time.

A drive test stuck at 90% does not automatically mean that the drive has failed. Several factors, including drive capacity, connection problems, read errors, background activity, and diagnostic software behavior, can contribute to this issue.

Why Does a Drive Test Stop at 90%?

Diagnostic utilities often perform multiple checks, including reading data, examining drive health information, and scanning for problematic sectors. The final stages may involve additional verification or processing, which can take longer than earlier stages.

Large-capacity hard drives can require several hours to complete an extended test. External drives connected through USB may also run more slowly than internally connected drives.

However, if the percentage remains unchanged for an unusually long time, particularly alongside repeated errors or disconnections, further investigation may be necessary.

1. Allow Enough Time for the Test

Before interrupting the diagnostic process, check whether the software is still responding. Some tests make slow progress near the end, especially when examining large drives or encountering difficult-to-read sectors.

Allow sufficient time based on the manufacturer's recommendations and the type of test being performed. An extended diagnostic can take considerably longer than a quick health check.

Avoid assuming that the test has failed simply because it remains at 90% for several minutes.

2. Check the Drive Connection

If you are testing an external hard drive, inspect the USB cable, connector, and port. A loose connection or unstable USB interface can interrupt communication between the drive and the computer.

Connect the drive directly to the computer rather than through an unpowered USB hub. If practical, try another compatible cable or USB port.

For an internal drive, connection problems involving SATA cables or power delivery may also affect diagnostic results. Shut down the computer before checking internal connections.

3. Monitor Drive Activity

Check whether the diagnostic software or operating system is still communicating with the drive. Drive activity indicators, system monitoring tools, or the diagnostic application's status information may provide clues.

If the drive continues showing activity, the test may still be working despite the unchanged percentage. If the application is unresponsive and the drive repeatedly disconnects, the process may have stalled.

Avoid repeatedly launching additional diagnostic tests while one is already running.

4. Check Drive Health and Error Messages

If the test eventually fails, record the exact error message or diagnostic code. Use the drive manufacturer's recommended diagnostic utility when available.

SMART health information can sometimes identify warning signs such as reallocated sectors, pending sectors, or interface errors. However, a healthy-looking SMART summary does not guarantee that a drive has no problems.

If the drive contains important files, back them up before performing further intensive tests, provided the drive remains accessible. If it makes unusual clicking or grinding sounds, disconnects repeatedly, or becomes unreadable, stop testing and consider professional data recovery.

5. Restart the Diagnostic Software Carefully

If the utility is clearly frozen, consult its documentation to determine how to stop the test safely. Do not disconnect the drive while it is actively writing data or performing a firmware operation.

After safely exiting the utility, restart the computer if necessary and check whether the drive is detected normally. Then run a shorter diagnostic test before attempting another extended test.

6. Consider Software Compatibility

Outdated diagnostic utilities, operating-system compatibility problems, and USB bridge limitations can sometimes cause unusual test behavior. Check for an updated version of the manufacturer's software and review its compatibility requirements.

If the problem occurs repeatedly, compare results using another supported diagnostic method rather than repeatedly running the same test without investigating the cause.

Conclusion

A drive test stuck at 90% may simply be progressing slowly, but it can also indicate connection instability, read errors, or a diagnostic software problem. Allow adequate time, check the connection, monitor activity, and record any error messages.

Most importantly, protect important data before continuing intensive testing. If the drive shows signs of physical failure or repeatedly becomes inaccessible, stop troubleshooting and seek professional advice rather than risking further data loss.