I made one good Windows set up, and now I clone it at any time when I would like a recent PC

I had a modest 100 GB free on my laptop computer, with one correctly configured Windows virtual machine already occupying greater than 20 GB. Creating 5 recent PCs the same old manner would have meant sitting via Windows Setup 5 instances, updating them, personalizing them, and squandering precious onerous drive house.

Instead, I constructed one golden picture in VMware Workstation and created 5 linked clones that share its digital disk. Each clone will be spun up in seconds and solely occupies 8.0 MB of onerous disk house when initially deployed.

After configuring and customizing every one, the entire setup, together with the unique VM, solely used 32 GB. The cloning was the straightforward half, however making the dad or mum VM was something however.

I needed to make one Windows set up value cloning

Every shortcut later relied on getting the dad or mum proper first

I didn’t set up Windows once more simply to make this work. I already had a licensed Windows 11 lab VM that had been optimized however was hardly thought of “golden.” It had just a few forgotten VMware snapshots that had made its measurement balloon to 86.93 GB, a 64 GB thin-provisioned disk, and a digital TPM with partial encryption.

Since I’d lengthy forgotten what the snapshots have been supposedly saving, I deleted them each, which consolidated the folder to 39.13 GB. I then turned the present set up right into a baseline I might really be pleased to clone:

• Windows 11 25H2 constructing 26200.9457, updated with patches.
• The newest VMware Tools model 13.1.5.0.25544008
• Firefox, 7-Zip, and Notepad++
• File extensions enabled, startup apps trimmed, and annoying Windows Taskbar features removed.

That means each future machine will get a clear browser, archive utility, editor, and present driver integrations from the very first boot.

I additionally disabled hibernation with powercfg /hibernate off and removed its hiberfil.sys file, and ran DISM /Online /Cleanup-Image /StartComponentCleanup. VMware’s Compact operate then received the VM information down from 39.17 GB to a extra cheap 23.61 GB.

The annoying half got here once I went to check cloning. VMware disables the power to create linked clones when a VM is encrypted. On my golden VM, the Windows digital TPM was the rationale there was partial encryption.

My quantity was absolutely decrypted, so I safely eliminated the vTPM and VMware encryption, recreated my Windows PIN, and confirmed the VM nonetheless booted. Finally, I shut it down, created the golden snapshot, and enabled Template Mode to guard the dad or mum from me inadvertently altering it.

Five new Windows PCs appeared in seconds

Linked clones retailer my adjustments with out copying Windows 5 instances

A VMware linked clone isn’t simply one other copy of the VM. It reads unchanged blocks from the golden snapshot and writes solely its personal new knowledge to what’s referred to as a “delta disk”. That dependency is how VMware created my 5 cloned PCs, all with totally different jobs:

• SOFTWARE TEST PC for testing software program on a brand new machine.
• Clean Browser PC for testing net pages on a browser with no add-ons or cookies.
• Network Tools PC for packet inspection in a managed setting.
• Writing PC for testing world-building and mind-mapping software in isolation.
• Disposable Test PC for once I really want to interrupt Windows.

VMware gave each clone a unique digital MAC deal with and UUID robotically. Unfortunately, the Windows VM clones nonetheless inherited the dad or mum’s WIN11-GOLDEN laptop title. I renamed every visitor after its first boot with Rename-Computer -NewName “” -Restart, then repeated the method for each linked clone.

Putting the golden picture in Template Mode retains each VMware and me from unintentionally deleting the dad or mum VM. It doesn’t make the clones short-term. In reality, their purposes, information, and settings all survive a reboot, not like a VM with an Independent-Nonpersistent disk.

The solely method to return the linked clones to their unique state is to delete them and spin up a brand new linked clone.

OS

64-bit Windows and Linux

CPU

64-bit Intel and AMD x86/x86-64 PCs

The storage distinction was larger than I anticipated

Five helpful machines consumed much less house than two full copies

The clearest comparability of disk utilization got here earlier than I put in any role-specific software program on the clones:

• A brand new linked clone earlier than boot used solely 0.008 GB.
• A consultant linked clone after its first boot used 0.579 GB.
• A full clone made earlier than boot occupied the identical quantity because the golden VM at 23.603 GB.

That made the total clone about 40 instances bigger than a linked clone that had already booted as soon as, restarted, and received its new hostname. The hole narrowed as I began utilizing the machines, however to not the extent of a full clone.

Their remaining delta disks solely mirrored what was really put in. Clean Browser PC, for instance, reached 0.749 GB, and the Writing PC grew to 4.778 GB after Obsidian, LibreOffice, and my favorite writing tools have been put in.

Linked clones gained’t keep tiny without end. They do develop after every replace, utility set up, and adjusted disk block that belongs to that clone will increase its delta file. Even so, the ~24 GB dad or mum and 5 customized PCs nonetheless occupied solely 32.327 GB mixed. If I had merely made full clones, then the onerous disk house required for all of them would have exceeded 118 GB.

The linked clones subsequently saved round 85 GB, or 73%. Since the custom-made full clones would have grown too, the longer-term disk space-saving is probably a lot increased than that.

Each clone grew to become a genuinely totally different PC

The shared basis didn’t drive them to remain similar

At first look, it does look as if each one of many clones is simply the identical PC copied 5 instances. That’s true, however solely on the level of creation. Each inherited updated Windows, VMware Tools, my most popular settings, and put in software program, however then diverged as quickly as I used it:

• Software Test PC received Process Explorer and Autoruns.
• Clean Browser PC received Brave and Opera browsers.
• Network Tools PC had Wireshark and Nmap put in.
• Writing PC received Obsidian, LibreOffice, Scrivener, and its one check vault.

Everything added after that remained inside that clone’s delta disk. My Obsidian vault didn’t seem on Network Tools PC, and Wireshark by no means reached the Writing PC or the golden VM. The shared baseline was frequent to all 5, however the machines’ purposes and information have been unbiased.

There was, after all, nonetheless an apparent {hardware} restrict. My laptop computer, with only 16 GB of RAM, may retailer all 5 VMs comfortably, however every VM had 6 GB of RAM assigned. I may run them independently, however not concurrently. Just as a result of linked clones save disk house doesn’t imply they share or enhance reminiscence or CPU.

Deleting a damaged PC was simpler than repairing it

The clear alternative arrived earlier than I may troubleshoot the previous one

The Disposable Test PC gave me the most effective causes to maintain this setup. To check it, I intentionally spoiled its fairly desktop wallpaper with a stable purple colour, put in VLC and Power Toys, eliminated the browsers and Notepad++, and created 20 junk information on the desktop. After this, its delta file grew to roughly 3.5 GB.

I may have uninstalled the brand new purposes, restored the lacking ones, deleted the litter, and reversed the modified settings. But why? As it seems, it’s a lot simpler to close down the ruined VM, delete that linked clone, and spin up a brand new one in below a second.

After doing simply that, the alternative occupied solely 0.650 GB. The ugly purple wallpaper was gone, together with junk information and VLC. Firefox and Notepad++ had additionally returned as they have been put in on the golden dad or mum picture.

Anything that’s saved contained in the deleted clone disappears together with it, so it goes with out saying that disposable PCs shouldn’t maintain irreplaceable work. The profit, although, is having the liberty to experiment. When I’ve destroyed a linked clone VM past the purpose of no return, I can change it immediately with out having to both fix it or reinstall Windows.

The golden picture can be the only level of failure

Linked clones are glorious lab machines, however poor unbiased backups

The weak point is that none of those linked clones is an unbiased PC. Each requires the dad or mum VM, its golden snapshot, and shared base disk to stay intact. Try to maneuver it, delete it, or re-encrypt it, and all 5 linked clones will fail.

Maintenance can be an issue. Existing clones gained’t inherit updates or purposes added to the dad or mum later. I would wish to replace the golden picture, take a brand new snapshot, and rebuild the clones that wanted these adjustments.

Encryption was, for me, essentially the most uncomfortable compromise. Since VMware refuses to create linked clones except I take away the encrypted TPM, the Windows 11 lab picture is left with out certainly one of Microsoft’s regular {hardware} necessities. The dad or mum additionally passes alongside any accounts, credentials, or private information.

In concept, the linked clone VMs shouldn’t have acquired Windows licensing activation, however they did. In time, they’ll probably lose it, though after a number of weeks of utilizing this setup, it’s but to occur.

I might select full clones for any everlasting, security-sensitive, or moveable machines. For disposable labs, browser testing, and software program experiments, the dependency on the dad or mum VM is affordable sufficient.

Finally, despite the fact that my good Windows set up did take hours to organize, each recent PC took seconds to deploy. When mixed with the disk house saved from utilizing the clones, the compromises are undoubtedly value it for my workflows.