Clone WSL Distro: Installing Ubuntu on WSL2 in Windows 11

To clone an existing Ubuntu distribution on WSL2 in Windows 11, you must export the current instance to a tar file using wsl --export, unregister the original distro with wsl --unregister to free resources, and then import the archive into a new name using wsl --import. This process creates an independent copy of your Linux environment without affecting the original data if done correctly.

Understanding the Cloning Mechanism

WSL (Windows Subsystem for Linux) does not have a native "clone" command. Instead, it relies on exporting the virtual hard disk state to a portable format and re-importing it under a different instance name. This method is officially supported by Microsoft and ensures that your files, configurations, and installed packages are preserved exactly as they were at the time of export. The core challenge users face is understanding that wsl --unregister destroys the instance definition but leaves the exported data intact only if you have saved it elsewhere. A common misconception is that unregistering deletes all data permanently; however, since we export first, the data remains safe in the .tar file. It is crucial to verify your installation location before starting, as discussed in our guide on Ubuntu WSL Install Location: Where to Find It?. Knowing where your WSL data resides helps you manage storage space effectively during the export process.

Step-by-Step Cloning Process

Follow these steps carefully to ensure a successful clone. Open PowerShell or Command Prompt with administrator privileges to avoid permission errors during the import phase.

1. Export the Existing Distribution

First, list your currently running distributions to identify the exact name of the Ubuntu instance you wish to clone. Run the following command:

wsl -l -v

Note the name of your Ubuntu version (e.g., Ubuntu-20.04). Then, execute the export command. Replace MyClone.tar with your desired filename and path.

wsl --export Ubuntu-20.04 C:\Users\YourName\MyClone.tar

This command creates a compressed tarball of your entire Linux filesystem. Depending on the size of your installation, this may take several minutes. Do not interrupt this process. If you encounter issues with large files or network drives, consider storing the tar file on a local NTFS partition like C: or D: rather than a USB drive, as performance can vary significantly. For more details on moving installations, see Fixing WSL Not Working After Moving Ubuntu from C to D.

2. Unregister the Original Instance

To prevent naming conflicts, you must remove the old instance definition from WSL's registry. This step deletes the instance entry but does not delete the tar file you just created.

wsl --unregister Ubuntu-20.04

After running this, verify that the distro no longer appears in wsl -l -v. The system will no longer recognize Ubuntu-20.04 as a valid instance until you re-import it.

3. Import as a New Name

Now, create a new instance by importing the tar file. Choose a new name for your cloned distro, such as Ubuntu-Clone. You must also specify the installation directory. This directory will store the virtual hard disk files (.vhdx) for the new instance.

wsl --import Ubuntu-Clone C:\WSL\UbuntuClone C:\Users\YourName\MyClone.tar

This command extracts the tar file into a new VHDX file located in C:\WSL\UbuntuClone. Once completed, you can start the new instance using:

wsl -d Ubuntu-Clone

Verifying the Clone

After launching the new instance, verify that your data has been transferred correctly. Check your home directory for personal files and run whoami to confirm user identity. Note that the default user might be root initially. To set a default user, you can edit the configuration file or use the --user flag when starting WSL. Be aware that cloning preserves the internal state of the Linux system, including package caches and temporary files. If you need a cleaner slate, consider reinstalling rather than cloning. Additionally, ensure that your Windows 11 system meets the minimum requirements for WSL2, including Hyper-V support and adequate RAM allocation. For troubleshooting connectivity issues after setup, refer to WSL: No Internet Connection (Ubuntu, Windows 11).

Managing Multiple Instances

With multiple clones, managing resource usage becomes important. Each WSL instance consumes RAM and CPU cycles even when idle. Use wsl --shutdown to stop all instances and release resources. You can also configure memory limits in the .wslconfig file located in your Windows user profile directory. Regularly clean up unused tar files to save disk space. The exported tar files can be quite large, so delete them after successful import if you do not need backup copies. Keep in mind that transferring WSL installations to external media, such as USB drives, requires specific handling to maintain permissions and bootability, as outlined in Can I Transfer My WSL Ubuntu Installation to a USB and Run It from There?.

Frequently Asked Questions

Does unregistering delete my data?

No, unregistering only removes the instance definition from WSL's registry. Your actual data remains in the .tar file you exported, provided you did not delete that file manually. Always export before unregistering to ensure data safety.

Can I clone a WSL1 distribution?

Yes, but you should convert it to WSL2 first for better performance and compatibility. Use wsl --set-version Ubuntu-20.04 2 before exporting. Cloning a WSL1 instance directly may lead to inconsistencies if you intend to use the clone in a WSL2 environment.

Why is my cloned instance slow?

Slow performance often results from storing the VHDX file on a network drive or an external USB device with high latency. Ensure the installation directory specified in wsl --import is on a fast local SSD or HDD. Antivirus software scanning the VHDX file can also cause delays.

How do I change the default user in the clone?

By default, the imported instance starts as root. To set a specific user, add --user username to your startup command or configure the /etc/wsl.conf file inside the Linux environment to specify the default user upon launch.

Is there a risk of corrupting the original distro?

There is no risk to the original distro if you follow the correct order: export, then unregister. However, if you unregister before exporting, you lose the ability to access the original instance unless you have another backup. Always double-check your commands before execution.