Data Recovery Case File · Formatted & Logical Faults · A Small Problem Made Real
The Original Problem Was Almost Certainly Ownership
His enquiry describes a sequence in which the remedy is the only genuine fault. Connecting an old drive to a new computer, he could not find his desktop files, tried the usual suggestions, and "therefore launched a scan, but during the process a blue screen error occurred. Now my computer cannot detect it anymore. Under disk management, the drive is unallocated." The files were never missing — and the scan that was meant to find them is what left the drive without a partition table.
| Media | Internal hard drive from a previous machine connected to a replacement — user profile content inaccessible; partition structure lost following a system crash during a scan |
| Reported situation | Drive from a previous computer connected to a new machine · desktop content not visible · hidden file display and other suggestions attempted · scanning software launched · system stop error occurring during the scan · drive no longer detected · partition reported as unallocated |
| Fault class | Partition structure damage from an interrupted scan — original inaccessibility attributable to profile ownership rather than any fault; content intact |
| Equipment used | Original inaccessibility identified as a permissions condition rather than data loss · post-crash write extent measured against capacity · imaged write-blocked before any reconstruction · partition and filesystem structures located from surviving copies · files validated by opening |
The decode: what was wrong at the start, and what the scan did
Why his desktop files appeared to be gone: they were not. Content in a user's profile is owned by that user account, and an account exists on the machine that created it. Connect the drive elsewhere and the new machine sees folders belonging to a user it has never heard of — so it declines access, and the folder appears empty or refuses to open.
Why that is so convincing: nothing says "you lack permission" in terms most people recognise. The folder is simply empty or inaccessible, which reads exactly like data loss.
What the actual fix was, and it costs nothing: taking ownership of the folder, which is a few clicks in the folder's properties. It is non-destructive, it takes a minute, and it makes the files appear — because they were there throughout.
Why the advice he found instead was unhelpful: showing hidden files is the commonest suggestion and it addresses a different problem entirely. His files were not hidden; they were not his, as far as the new machine was concerned.
What the scan then did: recovery and repair scanners read intensively and many write as they work. A system crash partway through leaves whatever was being written half-finished — and a scan operating on partition and filesystem structures that is interrupted mid-write can leave them incoherent.
Why the drive now reports as unallocated: the partition table describes where volumes begin and end, and it is small. Damaged, it means the system finds a drive with no volumes on it — which is what unallocated means, and it is a statement about a few sectors rather than about the contents.
Why the position remains good: the partition table is a small structure and it is reconstructable. Filesystems keep backup copies of their key structures elsewhere, and the content was never visited by any of this. What is required now is a proper reconstruction rather than another scan.
What must not happen: no further scanning, and no acceptance of any offer to initialise. The system will now offer to prepare a drive it sees as empty, and that writes over the region a reconstruction reads.
On the bench
The original inaccessibility was identified as a permissions condition rather than data loss — profile content being owned by an account that exists only on the originating machine, so a replacement declines access and the folder presents as empty. Post-crash write extent was measured against capacity, scanning utilities writing as they work and a system stop leaving structures half-modified. The drive was imaged write-blocked before any reconstruction, with structures located from surviving copies.
The outcome
The original condition identified as ownership rather than loss, the post-crash extent measured, and structures recovered from surviving copies. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: your files were never missing. Profile folders are owned by the account that made them, so another machine refuses access and the folder looks empty — taking ownership would have shown them in a minute.
Old drive whose folders look empty on a new machine
Take ownership of the folder before running anything — that's the fix, it's a few clicks in the folder's properties, it's non-destructive and it takes a minute. Profile content is owned by the account that created it, and that account exists only on the original machine, so a new computer sees folders belonging to a user it has never heard of and declines access. The folder then appears empty, which reads exactly like data loss. Showing hidden files is the usual suggestion and addresses a different problem. Don't launch a repair or recovery scan: those write as they work, and a crash partway through damages structures that were fine.
Don't scan again — call Oxford Data Recovery on 01865 593000; original condition identified before assessment, write extent measured against capacity, partition and filesystem structures recovered from surviving copies.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.