A smaller visible volume does not necessarily mean the physical USB became smaller. A boot-media layout, an unallocated area, different capacity units, or a controller problem can produce very different symptoms. Record the physical and partition sizes before attempting to restore the advertised capacity.

Compare the right numbers
Record the label’s stated capacity, File Explorer’s volume size, and Disk Management’s physical disk size. A marketed decimal capacity and a binary display differ by a predictable amount. For example, 64 GB is about 59.6 GiB before formatting, although Windows may label that binary value as GB. Formatting also consumes space. Kingston’s Flash Memory Guide explains why available capacity can be lower than the label. A much larger difference, zero capacity, or a value that changes between connections needs further investigation.
If a 64GB-class physical device contains only a small installer partition and remaining unallocated space, the layout may explain the small Explorer volume. That observation does not tell you which old bytes survived the installer writes. Do not extend, delete, or format its partitions until the old files have been addressed.
Preserve files within the current readable range
First copy files that open normally to another physical disk. Open and check the copies, particularly large files written near the time the problem appeared. A successful directory listing is not evidence that all content addresses are valid.
For missing files on readable storage, scan the correct USB disk in XRecovery and export candidates to the other disk. The scan can examine only the storage the device actually makes readable. If the controller reports only a much smaller range, a file scanner cannot simply ask for the missing advertised addresses.
Try a direct port or a different trusted computer once if the connector is intact. Compare the physical capacity again. A changed drive letter is normal; a changing physical size is an important symptom to record.
Avoid capacity tests while data still matters
Some authenticity tests write patterns across the device to check whether stored data can be read back. Such a test is unsuitable for the only copy of wanted files. A suspected counterfeit may accept writes beyond its true storage and later return wrong content; formatting cannot recreate the original files in that case. Keep the packaging, purchase record, and observed capacity for a vendor enquiry.
Once recovery is finished and verified, a disposable test or vendor-supported preparation process can help determine whether the drive is usable. Keep that decision separate from recovering its files. Do not run an unknown controller or firmware “capacity repair” tool on the original source. A drive reporting No Media, zero size, or repeated disconnects needs hardware assessment rather than a partition-size correction.