viap moves a Windows application by replacing its folder with a junction

Relocation without breaking the hard-coded path

The problem viap addresses is mundane and familiar. An application is installed on a small system drive, the drive fills, and moving it is awkward because Windows programs record their install location in a dozen places. Viap's answer is to make the move invisible. It is a Windows desktop application built with Tauri, React, TypeScript and Rust, and it uses NTFS directory junctions or symbolic links to redirect storage without changing application paths. The application continues to look for its files in the original location, and what it finds there is a link pointing at the new drive. That design is what makes the tool useful for legacy software, and it is also the source of most of the caveats, because anything that resolves a path to a real volume, checks the volume type, or binds a licence to a directory will see something different after the move. The audience is Windows power users and support technicians, not developers.

Copy, verify, and only then switch the path

The sequence is the most important thing in the documentation, and it is deliberately conservative. The features list says that Viap verifies the copied data before switching the original path to a junction or link, and the safety notes say the design is to keep a usable data copy until the migration switch has been verified. So the operation has three phases. First the data is copied to the target. Then the copy is checked. Only then does the original path become a link. The ordering means a failure in the middle leaves you with a copy on the new drive and an untouched original, which is the state you want. The safety notes also make the limit of that guarantee explicit: no file operation is completely safe against hardware failure or unexpected power loss, and the documentation tells you to back up important data before migrating. The copy-then-verify-then-switch ordering is the reason to trust this tool with a real system drive rather than treating it as a file mover.

Process and lock checks, and the software they cannot see

Viap checks running processes and file locks before a migration or a restore, and it tells you to close the application being migrated. The documentation is honest about the limit of that check, because some software uses services, drivers or memory-mapped files, and a running process check does not see any of those. That is the main reason the tool needs administrator privileges, since Windows requires permission to create links or to reach protected folders. The same reasoning appears in the instruction not to migrate the entire AppData, Local or Roaming directory, and to select data folders for one application at a time. Moving a whole shared profile tree is exactly the case where a service is quietly writing to a file that the tool believes it has copied. The checks are a safety net, not a guarantee, and the documentation says so in as many words.

The list of software that should not be moved

The safety notes name a specific set of exclusions, and they are more useful than the feature list. Software with licence binding, system services, kernel drivers, self-repair mechanisms or hard-coded paths may not work correctly after redirection, and for that case there is no workaround inside the tool, only the knowledge in advance. Microsoft Store, UWP and MSIX applications, system components, browser installations and GPU drivers should be handled by Windows or by their vendor tools instead. The migration targets are constrained too: use local NTFS drives, since network drives and unsupported file systems are not migration targets. One more operational rule is worth internalising, that you should not manually delete the target directory while a migration record is active, and should restore the application first where that is possible. These are the cases where a data operation that looks like a file move actually breaks a program, and they are the cases to check before you start.

Uninstalling and scanning for what the installer left behind

The reverse operation is covered too. Viap can uninstall applications and scan or clean the related leftovers, with handling for running processes, a before and after comparison report, and matching of services, drivers or scheduled tasks. The report is the interesting part, because a Windows uninstall rarely removes everything, and knowing what was removed and what remained is the difference between a clean machine and one that has accumulated a layer of orphaned services. The tool also keeps a migration history with restore, link health checks, import and export, so the record of what was moved can be moved to another machine or restored from a backup. There is also a recovery path for lost history, by scanning directory junctions, which is what you would do if the history file was lost but the links are still in place. The app also shows disk usage, application snapshots, lazy-loaded icons and background scan progress, and it detects HDD cold-start cases so you can manually load slow application data directories.

Three ways to install it, and where the data lives

Viap ships in three forms. The standard installer is an installed application with update support. The WebView2 offline installer includes the WebView2 runtime for systems that cannot download it during installation, which matters on locked down or offline machines. The portable ZIP is extracted and run without installation, with user data stored beside the application in a data folder, and portable builds cannot update themselves, although they do check for new versions and point you to a manual download from GitHub Releases or from Quark Drive. On first launch the portable build can copy missing data from an existing Viap installation, and existing installation data is not deleted. Installed builds normally use %APPDATA%\viap, and the Settings page can change the data directory, copying managed data before switching to the new location. Themes, the optional liquid-glass appearance, font size, default migration paths, the recycle-bin preference and scan settings are persisted with the user data. The interface also offers light and dark themes, font size settings and portable mode.

Verifying that the binary you are running is the one that was published

One feature stands apart from the rest, because it addresses the trust problem of a tool that runs with administrator privileges and moves system files. Open Settings and choose Verify file integrity. Viap then downloads the signature for the current release from GitHub and verifies the running executable with the official public key, and a success message appears only when the signature and the file content match exactly. The failure handling is specific rather than generic, since a signature mismatch indicates the file may have been modified, while network failures, missing signatures and malformed signatures are reported separately and are not treated as tampering. That distinction is the difference between a useful tool and one that cries wolf on a proxy. The project is MIT licensed, and it moves actively, with v1.2.2 published on 2026-09-24, v1.3.0 on 2026-10-06 and v1.3.1 on 2026-10-09, and the last push on 2026-10-09. Building from source needs Windows 10 or later, Node.js 18 or later and Rust with the Tauri prerequisites, and the development loop is:

npm install
npm run tauri dev

The build and verification steps that the project documents for a release are:

npm run build
cargo check --manifest-path src-tauri/Cargo.toml --no-default-features
git diff --check

Editorial conclusion

viap is a good fit for a Windows user with a full system drive who wants to move large applications and their data off it without reinstalling, and it fits a support technician who needs to leave a machine in a restorable state, since every migration is recorded and reversible. It is the wrong tool for Microsoft Store, UWP and MSIX applications, for licensed software that binds to an install path, for anything on a network drive, and for anyone unwilling to run it with administrator privileges. Before adopting it, read the safety notes, back up what you are about to move, and test a restore on one non-critical application first, because the junction swap is the point of no return in the sequence and the tool itself warns that no file operation is safe against power loss.

Frequently asked questions

Official sources

1. Chunyu33/viap on GitHub
2. Issues
3. License: MIT
4. README
5. Releases