Look at the source’s condition and the operation’s behavior before deciding that a scan has frozen. There is no fixed scan time: a long scan on stable storage can be normal; repeated read errors or disconnections need a different response. Preserve useful results and the source rather than repeatedly restarting the same scan without knowing what changed.
Describe the symptom precisely
Record the source type and capacity, connection, application version, current stage, approximate elapsed time, and what appears unchanged. A displayed percentage that has not moved is different from an unresponsive whole computer or a device that disappears from Windows.
Also note whether new results continue to appear and whether the device remains connected. These observations help distinguish slow work from a lost source or a broader system problem. A large result set or a difficult region can produce uneven progress; a time estimate is not a guarantee of completion.
Consider the work being performed
Disk capacity, the amount searched, file-system condition, number of files, source read speed, and connection performance can all influence the task. The size of the one document you want does not tell you how much storage must be examined to find it.
Avoid competing heavy access to the same source. Copying unrelated data from it, running other scans, or repeatedly opening it in other utilities can make behavior harder to interpret. On the working computer, excessive memory or CPU load from unrelated applications can also affect responsiveness.
Do not use a fixed “minutes per gigabyte” rule to decide that your result is wrong. Different tasks on the same capacity disk can require very different work.
Wait when the source is stable and work is continuing
If the disk remains stably identified, no abnormal hardware symptoms appear, and the application continues working, allow time for the operation. Record a comparison point rather than interrupting it every few minutes.
Use result filters to inspect what has already been found without assuming that the currently visible list is the entire final result. Previewing and recovering are distinct tasks; a visible entry does not mean all relevant source data has already been processed.
Stop when continued reading is the wrong choice
Abnormal clicking, repeated disconnects, unexpected capacity changes, overheating, or persistent system stalls are reasons to stop ordinary repeated scanning and assess the source. A recovery application cannot repair a failing read head, connector, or controller by searching harder.
Use the application’s normal pause or stop controls when it remains responsive. Do not unplug a device during active access as the normal way to stop. If the computer itself is unresponsive, prioritize the source’s condition and seek help appropriate to the hardware rather than repeatedly cycling power.
For valuable data on unstable storage, an appropriate imaging or specialist strategy may be more important than choosing a longer scan. Imaging itself also reads the device and needs a plan suited to its condition; it is not automatically harmless.
Preserve work before another attempt
Save scan results when that operation is available and safe to complete. Retain the corresponding source or image: the result file is not a backup of all discovered file contents. Keep already exported usable files on the independent destination.
Before retrying, state what has changed: a verified cable, a different compatible connection, reduced unrelated workload, or an image-based source. Repeating the identical operation on the same failing device does not help identify the cause.
Send useful evidence for assessment
Provide the exact error, source capacity and connection, elapsed time, last observed progress, application/Windows versions, and whether Windows still identifies the device. Include a redacted screenshot and only the diagnostic files requested through the official support route.
Do not include a license key, encryption password, or an entire disk image in ordinary support correspondence. A clear description of the stage and read behavior is usually the right starting point for deciding whether the next action is waiting, changing the access path, or stopping software work.