Installation

In this section you will learn how to download, verify and run Mugnsoft Pulse on Windows or Linux.

Pulse is portable: you extract an archive and run the application from the extracted folder. Nothing is installed and no administrator rights are needed.

Requirements

  • Windows 10 or 11, 64-bit, or a 64-bit Linux desktop
  • An internet connection to activate the license

Download

Pick Pulse, the version and your operating system on the Mugnsoft download page, which also gives the commands below for the version you select. The archives are:

System Archive
Windows mugnsoft-pulse-1.2.0.windows-amd64.zip
Linux mugnsoft-pulse-1.2.0.linux-amd64.tar.gz

Pulse 1.0.0 and 1.1.0 were released for Windows only.

Verify the download

Each archive is signed with Mugnsoft’s release signing key. With GnuPG installed, download the signature and the public key, then verify the archive.

Windows (PowerShell)


curl.exe -O https://mugnsoft.com/bin/mugnsoft-pulse/mugnsoft-pulse-1.2.0.windows-amd64.zip
curl.exe -O https://mugnsoft.com/bin/mugnsoft-pulse/mugnsoft-pulse-1.2.0.windows-amd64.zip.sig
curl.exe -O https://dl.mugnsoft.com/keys/Mugnsoft_public.key
gpg --import Mugnsoft_public.key
gpg --verify mugnsoft-pulse-1.2.0.windows-amd64.zip.sig mugnsoft-pulse-1.2.0.windows-amd64.zip

Linux


curl -O https://mugnsoft.com/bin/mugnsoft-pulse/mugnsoft-pulse-1.2.0.linux-amd64.tar.gz
curl -O https://mugnsoft.com/bin/mugnsoft-pulse/mugnsoft-pulse-1.2.0.linux-amd64.tar.gz.sig
curl -O https://dl.mugnsoft.com/keys/Mugnsoft_public.key
gpg --import Mugnsoft_public.key
gpg --verify mugnsoft-pulse-1.2.0.linux-amd64.tar.gz.sig mugnsoft-pulse-1.2.0.linux-amd64.tar.gz

The result must contain Good signature from "Mugnsoft (release signing key) <info@mugnsoft.com>" and the key fingerprint 65F8 B880 F8CC 9DCF D2C8 4887 8FEE 1578 1BEF 9B7A. GnuPG also warns that the key is not certified with a trusted signature: this is expected until you have certified the key yourself.

Note:

If the signature is not good, do not use the archive. Delete it, download it again, and contact support if the check still fails.

Windows

Extract

Extract the archive into a folder with a short path, such as C:\Mugnsoft. The archive contains deeply nested files, and extraction fails with path too long when the destination path is long, which can happen in a Downloads folder synchronized with OneDrive.

From PowerShell, in the folder where you downloaded the archive:


Unblock-File .\mugnsoft-pulse-1.2.0.windows-amd64.zip
Expand-Archive .\mugnsoft-pulse-1.2.0.windows-amd64.zip -DestinationPath C:\Mugnsoft

Or from File Explorer: right-click the archive, choose Properties, tick Unblock and click OK, then right-click it again and choose Extract All.

Note:

Unblocking the archive before extracting it prevents the Windows protected your PC warning when Pulse starts. Files extracted by File Explorer from an archive downloaded with a browser inherit its “downloaded from the internet” mark.

Start Pulse

Run C:\Mugnsoft\mugnsoft-pulse-1.2.0\Mugnsoft Pulse.exe. On first launch Pulse asks you to activate a license: see License activation.

To start Pulse from the desktop, right-click Mugnsoft Pulse.exe and choose Send to → Desktop (create shortcut) (on Windows 11, Send to is under Show more options).

Linux

Extract and start Pulse

Extract the archive, for example into your home folder, and start the mugnsoft-pulse program it contains:


tar -xzf mugnsoft-pulse-1.2.0.linux-amd64.tar.gz -C ~
~/mugnsoft-pulse-1.2.0/mugnsoft-pulse

The programs in the archive are already executable: there is no chmod to run. On first launch Pulse asks you to activate a license: see License activation.

If Pulse does not start and reports a problem with the SUID sandbox helper, see Troubleshooting.

Update or remove

  • Update: close Pulse, extract the new version next to the old one, start it from the new folder, then delete the old folder.
  • Remove: close Pulse and delete the mugnsoft-pulse-<version> folder.

Your projects are the .side files you saved, wherever you saved them. Your settings, test history and license are stored in your user profile — under %APPDATA% on Windows, ~/.config on Linux — not in the application folder, so they are kept across updates.

See also

Translations