Installing Resonic

Several different types of installation packages and builds are available for Resonic. We'll show you which ones, and how to install and use them properly.

While Resonic Player and Resonic Pro are separate products they share the same foundations.

Package Types

For each flavor of Resonic there are a few types of packages available:

Make sure you always get your updates from this site, and this site only.
See also: Resonic and Virus Scanners

Setup Packages

Setup packages come in the form of digitally signed Windows Installer packages (.msi files.)

Using a setup package is recommended for most users.

Setup Installation

Double-Click the .msi package file to run setup and follow the instructions.

  • Older versions of the same flavor are upgraded.
  • Installation takes a few seconds.
  • When complete, Resonic will start.

To Repair or Uninstall the installed version use Add or remove programs in Windows Settings, or run the setup package again.

Resonic Player and Pro can co-exist on the same system.

This method installs Resonic locally, integrates into Windows Explorer, comes with several file type icons and custom icon support, and is the easiest to update and maintain, hence this is the recommended method of installation.

Setup will never alter or take over any of your existing file associations without your explicit permission.

Storage Locations in the Setup Version

Depending on your version of Resonic, your user profile is stored in Resonic in your personal Documents folder.

<userprofile>\Documents\Resonic\Player Beta
<userprofile>\Documents\Resonic\Pro Beta

For example:

C:\Users\Cannoli\Documents\Resonic\Player Beta

Release and Beta versions of both applications can be installed side by side. They use their own sets of user data and file associations.

Portable Packages

Portable packages come in the form of ZIP archives (.zip files.)

Portable versions do not integrate into Windows Explorer, do not come with file type icons, and use a different path system that setup versions. Some other features might be absent.

No data is written outside the program folder, or to the Windows registry.

Portable Installation

Unpack the .zip file to your portable drive / USB disk, or any other writable location, and run Resonic.exe from there.

The disk needs to be write-enabled while Resonic is running.

Do not put portable versions in any of your Program Files or Program Files (x86) folders as they have write-access restrictions in place, and use a setup package instead.

Storage Locations in the Portable Version

By default portable versions of Resonic are configured to use per-user profiles, and store user profiles in folders that follow this template:


For example:

D:\Resonic Portable\Portable\cannoli@pastapc

This flexible system allows you to carry a portable version of Resonic with you on an external drive and use it on different systems with completely separate configuration sets.

You don't have to worry about your home settings accidentally being overwritten when using the program on another system.


Depending on the configuration in ResonicBoot.ini Resonic creates these profiles:

  • user@machine — one profile for every user (default)
  • machine — one profile for every machine
  • user — just a single profile

Pro Licenses and Portable Versions

When you run a portable version of Resonic Pro you will be asked to enter your license first. However, if you already have a licensed version of Resonic Pro installed you won't need to to enter your license.

Unstable Builds

Unstable builds are unfinished / test / preview / pre-release versions of Resonic.

They are only available as portable versions (.zip files) and like any other portable version they can be safely run on their own without affecting any installed version of Resonic.

Unstable builds are never intended for production use.

Where to find Unstable Builds

You can find unstable builds:

Running Unstable Builds

No installation is needed.

Unpack the .zip file to a temporary and writable location, e.g., simply your Desktop, but never to any of your Program Files folders, and run Resonic.exe from there.

Pro Licenses and Unstable Builds

When you run an unstable build of Resonic Pro you will be asked to enter your license first. However, if you already have a licensed version of Resonic Pro installed you won't be asked to enter your license every time you try an unstable build.

Removing Unstable Builds

Delete the temporary folder you unpacked the .zip file to. That's it.

Unattended Installation

Installation of Resonic .msi setup packages can be automated in the following way:

Unattended Silent Installation

The following command runs a local unattended installation that is fully silent, i.e., neither dialogs nor installation progress is shown and default settings and paths are assumed:

msiexec /i "Your Resonic Setup Package.msi" /qn

Unattended Installation with Dialogs

The following command runs a local unattended installation where both dialogs and installation progress are shown and default settings and paths are assumed, but user interaction is never required:

msiexec /i "Your Resonic Setup Package.msi" /qr

To only show the most basic dialogs run the installation as follows:

msiexec /i "Your Resonic Setup Package.msi" /qb

Unattended Activation of Resonic Pro

Resonic Pro can be activated either with a Double-Click on the .rsaf file (Resonic Activation File), or by using the --install-license command-line parameter. The --quiet parameter will make sure no user interaction is required.

resonic.exe --install-license "Your Activation File.rsaf" --quiet

Resonic Pro can also be deactivated (license cleanup), but using the --remove-license parameter, again in combination with --quiet. A filename is not required.

resonic.exe --remove-license --quiet

Restart after Unattended Installation

By default setup will not restart your system after installation, but you can change that behavior by passing the /forcerestart option to msiexec, which will always restart the system after installation.

Logging during Unattended Installation

To log all installation messages to a file use the following msiexec option, using a log filename of your choice:

/log "Installation Log.txt"

Additional Options

To see a full list of options available to the msiexec program run this command:

msiexec /?