RAW drive after connecting it to another computer: what may have changed?
You move an external drive from one laptop to another - perhaps between a home computer and a Warsaw office workstation - and suddenly Windows shows RAW instead of folders. The second computer probably did not erase the data. It exposed a file-system or device problem that normal access can no longer handle.
The mistake is to test the drive on five more machines. Different ports, hubs, cables and USB controllers can change the symptoms, but they can also keep stressing an unstable device.
One controlled cable/port check is reasonable. A chain of laptops, repair prompts and scanners is not.
Why a drive can show RAW after reconnecting
The earlier computer may have cached writes, disconnected the drive during activity or tolerated weak reads that the next system refuses to mount. A different USB bridge, lower power delivery or a damaged cable can also reveal a problem that was already developing.
- Improper removal while files were open.
- Weak USB power through a hub or docking station.
- Different Windows/macOS handling of an already damaged file system.
- Read errors near the MFT, partition table or boot sector.
If the drive had already been slow, disconnecting during copying or showing CRC errors, the computer swap may be only the moment when the failure became visible.
What not to do in this situation
Do not format, initialise, run CHKDSK or install recovery software onto the same drive. Do not keep trying every available laptop in the office. Each mount attempt can trigger more reads, writes or repair suggestions.
If Windows offers "scan and fix", decline it when the data matters. That function is designed for volume repair, not for preserving maximum recovery evidence.
When it is time for specialist help
Escalate when the drive freezes the system, disappears after a few seconds, clicks, reports the wrong capacity or behaves differently on every connection. Those symptoms suggest more than a simple driver mismatch.
For external USB drives, diagnosis should consider the disk, enclosure electronics, USB-SATA bridge, cable and power. For internal HDD/SSD removed from another machine, note whether encryption such as BitLocker or FileVault was active.
What to do when RAW appears after moving the drive
Keep the attempt count low. Use one known-good cable and a stable port directly on the computer, not a chain of hubs. If the RAW message returns, stop testing and document the sequence.
Write down the previous computer, the new computer, operating systems, cable/enclosure used, exact message, capacity shown and any tools already launched. This is more useful than another scan.
How to check whether the problem is the system or the device
A system-specific issue usually stays limited to one machine. A device issue follows the drive: the same RAW message, freeze or disconnect appears on another computer. Still, do not keep repeating this test once the pattern is clear.
Passive checks are enough: model, capacity, connection sound, disconnect timing and whether the original computer still mounts the volume. Stop before any operation that writes to the drive.
When RAW after reconnecting means something more serious
RAW combined with slow access, I/O errors, clicking, repeated disconnects or changing capacity can mean surface degradation, controller trouble or enclosure failure. In that case, logical repair tools may make the later lab process harder.
Compare RAW drive - do not format, external drive disconnects during copying and computer does not see an external drive.
How to hand over the case for diagnosis
Send a short, factual description rather than a long list of guesses. Include which computer last opened the files, what changed before the RAW message, whether the drive was removed from an enclosure and whether any repair tool wrote to it.
Use case submission for a Warsaw diagnosis path, or choose external USB drive recovery, HDD data recovery or SSD/NVMe data recovery by device type.