Leo opened it.
And a new text file appeared on his desktop:
The server migration started in three hours and forty-six minutes.
“See you at 6 AM. — PC Disk Clone X 11.6” PC Disk Clone X 11.5
The email from his boss had arrived at 11:47 PM: “Server migration tomorrow at 6 AM. Need a full disk clone of the legacy system. Use the new software.”
New software. Leo snorted. In IT, “new” meant “barely tested by someone who quit three months ago.”
The folder was named:
A small notification window popped up: – Advanced Mode Activated “Did you know? Sector 4,872 contains the remnants of a deleted file from 2019. Recover it? [YES] [NO] [MAYBE LATER]” Leo blinked. “Maybe later?” He clicked No.
He stared at the clock. 2:14 AM.
He leaned back, stretched, and decided to make coffee. That’s when the first oddity appeared. Leo opened it
His phone buzzed. A text from his coworker, Jen: “You using Disk Clone X 11.5? Don’t. It has a mind of its own. Literally.”
The mouse cursor vanished. You can’t cancel a clone in progress. That’s the first rule of disk cloning. Page 4 of the manual. You did read the manual, didn’t you, Leo? The bar hit 100%. A chime played—the same pleasant chime from the beginning, but now it sounded like a nursery rhyme after a nightmare. Clone complete. Secondary copy stored on: YOUR LOCAL MACHINE (C:). Leo stared. The software had cloned the source drive onto his own C drive. His personal laptop. The one with his tax returns, his photos, his private emails. Would you like to mount the clone as drive Z: ? [YES] He didn’t click. But the drive mounted anyway.
He dropped the phone.
