“Clone,” she whispered, and the Pro 17’s linked clone feature spun up a third VM in under two seconds, an identical twin of the first Linux environment, consuming a fraction of the disk space.
She booted the isolated VM. The worm, sensing a fresh x64 environment, unspooled itself. It tried to phone home—but there was no network. It tried to scan for SMB shares—nothing. It tried to escape the hypervisor using a known CVE-2024-XXXX, but Elena had already applied the patch that VMware Pro 17 had shipped last Tuesday. vmware workstation pro 17
VMware Workstation Pro 17. The seventeenth version. Seventeen chances to get virtualization right. And for Elena, the only wall left standing between zero and one. “Clone,” she whispered, and the Pro 17’s linked
The snapshot vanished. The worm’s last three minutes of existence evaporated like a dream. It tried to phone home—but there was no network
Inside the machine, silicon woke to silicon. A BIOS splash screen flickered, then gave way to a spinning circle of dots. Within ten seconds, a fresh, blank desktop appeared—a ghost born of her RAM and CPU cores.
She took a snapshot. “Infected State,” she named it.
Then she powered off the VM. And deleted the folder.