Hopover moves your whole Windows PC to a new one: apps, settings, WSL, SSH keys, env vars and files. This page covers everything you need for a move. Download Hopover.exe or go back to the product page.

What you need

  • Two PCs with Windows 10 or 11, and admin rights on both.
  • The same version of Hopover on both PCs.
  • A connection between them. A LAN cable is by far the fastest.
  • Enough free disk space on the old PC for a copy of your WSL distros, if you have any.
  • Internet on the new PC, because the apps download from their sources.
  • A backup of anything you can’t lose. Hopover is young.

Use the same user name on the new PC if you can. Hopover adjusts paths in env vars, the registry, scheduled tasks and links, but it can’t fix paths inside your own config files.

How to connect the PCs

Connection Real speed Good to know
One LAN cable, PC to PC 100 to 280 MB/s Choose Direct cable. No router needed. Keep Wi-Fi on for the app downloads.
Both PCs on one router by cable about 100 MB/s Choose Same network.
Thunderbolt or USB4 cable fast Only if both PCs have those ports. Choose Direct cable.
Same Wi-Fi often 5 to 30 MB/s Choose Same network. Works, but 500 GB can take a day or more.
Over the internet depends on your line Both PCs online. A small meeting point only swaps addresses.

A plain USB-C or USB-A cable can’t link two PCs. On a direct cable, Windows needs up to a minute before the port gets an address.

The move, step by step

On the old PC

  1. Start Hopover, accept the admin prompt and click This is the old PC. The pairing code appears right away, next to the button.
  2. Untick what stays behind. Hopover measures the folders meanwhile, and you don’t have to wait for that: the sizes only feed the progress bar.
  3. If you move certificates, choose a password. You type it again on the new PC.
  4. Click Prepare the move. This exports WSL and your Docker volumes, which can take an hour. WSL stops meanwhile, and PostgreSQL stops for a moment.

On the new PC

  1. Start Hopover and click This is the new PC.
  2. Choose how the PCs are connected and type the code. The new PC waits until the old PC is ready.
  3. If you want to review first, switch on Preview first. Hopover writes everything it would do to a text file and changes nothing.
  4. Click Start the move. The package from the old PC comes first, then the Windows features, then apps and files at the same time.

You can close Hopover at any time. Start it again, connect and it goes on where it stopped.

What moves

  • Apps: reinstalled through winget, Chocolatey and the Store, with Visual Studio workloads. A program with no package moves as a folder, with its registry keys.
  • Dev setup: WSL distros, Docker volumes, PostgreSQL, env vars and PATH, SSH keys, git and GitHub CLI logins, scheduled tasks (switched off), hosts file.
  • Windows settings: taskbar, Start pins, wallpaper, theme, desktop layout, Explorer, sounds, night light, mouse, keyboard, languages, region, power plan, notifications, privacy, Wi-Fi, Windows features.
  • App settings: all of AppData and the registry entries that go with it.
  • Files: your profile, your folders on C:\, other drives, junctions and symlinks.
  • Caches, if you want them: Gradle, npm, uv, Playwright, IDE indexes. Each one is a line in the list.

What does not move

  • Cloud folders: OneDrive, SeaDrive, Google Drive, Dropbox, Box, iCloud and others. They sync by themselves after you sign in.
  • Sign-ins: Windows ties them to the old PC, so no tool can move them. Click Sign in to your accounts at the end, and Hopover opens each one in turn, password managers first.
  • Docker images: they come back with your next pull. A running Docker disk can’t be copied.
  • Browser profiles: they sync after you sign in.
  • Epic, GOG, EA and Ubisoft games: they download again.
  • Certificates that Windows marks as not exportable. The checklist names them.
  • Default apps, display scale, lock screen picture: Windows protects those or ties them to the hardware.

Keep working on the old PC

Your old PC stays in use. Click Catch up with the old PC on the new PC as often as you like, and Hopover fetches what changed. Keep Hopover open on the old PC for that.

Situation Result
First move, file differs The old PC wins. The new PC’s file moves to C:\hopover-held.
Changed only on the old PC It updates on the new PC.
Changed only on the new PC It stays.
Changed on both PCs The new PC keeps its version. The old version goes to C:\hopover-held.
Gone on the old PC It moves to C:\hopover-held on the new PC.
Only on the new PC It stays.
Env var It updates when only the old PC changed it. The checklist names the others.
WSL Changed files come over. A newer file in the new distro stays.
Docker volume It updates when nothing used it on the new PC.
PostgreSQL The new PC keeps its data after the first restore.

Nothing gets deleted. Look through C:\hopover-held when you’re done.

Finish the move

  1. Do a last Catch up, then work only on the new PC.
  2. Click Sign in to your accounts.
  3. Work through the checklist.
  4. Sign out of Windows once, so that the taskbar and theme apply.
  5. Turn off the scheduled tasks on the old PC, then click Turn on scheduled tasks on the new PC.
  6. Click Clean up on both PCs. That deletes C:\hopover-store with its Wi-Fi passwords and tokens. Your own files stay.

When something goes wrong

Windows warns about the download. The exe isn’t signed yet. Click More info, then Run anyway.

The new PC finds nothing. Check that both PCs are on the same network, not just the same building. Compare the first three numbers of the addresses in ipconfig: 192.168.178.31 and 192.168.100.9 are two different networks. Guest networks often block PCs from seeing each other.

The cable shows no connection. Run Get-NetAdapter -Physical in PowerShell on both PCs. If Ethernet shows Disconnected, try another cable before anything else. Some cables are simply broken, and some laptops switch the port off on battery.

It stays at 0%. The percentage counts the files. The package from the old PC and the Windows features come first.

A step failed. Start Hopover again. It retries the failed steps and copies only what is missing. The logs are in C:\hopover-store\logs.

A file was not copied. A file that is locked on the old PC stays behind, and the checklist counts them. Close the app there and click Catch up.

Something else. Open a ticket on GitHub and attach the log.

Privacy

Hopover has no account and no tracking. Your files go directly from PC to PC, encrypted with a key that comes from the pairing code. Over the internet, a small meeting point swaps addresses and counts meetings per day. No server ever carries your files.

C:\hopover-store holds Wi-Fi passwords, tokens and saved logins during the move, locked to your user. Click Clean up when you’re done.