Download SmartCom Revisited

Version 1.7.0, released 2026-09-10. Free, and no account needed.

Every build is 64-bit x86. Upgrading keeps your settings, saved connections and buttons. What changed in 1.7.0.

The 1.7.0 files are built, but this server does not have them

Every file below is real — the sizes and checksums are of the exact builds — but none of them is in place here, and nothing is guessed at, so no download button appears until there is a file behind it. You can still check any copy you were given by hand against the SHA-256 printed with it.

These builds are not code-signed

Signing certificates cost money that is not being spent on this yet. The binaries are fine; your operating system just has no way to confirm that, so it will say so. Here is exactly what you will see:

Windows: SmartScreen shows “Windows protected your PC”. Click More info, then Run anyway. Your antivirus may also quarantine the first run of an unsigned installer.
Linux: Packages are unsigned, so apt or dnf may warn about the missing signature when installing the file directly. The AppImage needs the execute bit set.

Every download below lists its SHA-256. Until the builds are signed that checksum is the only integrity check available, so it is worth actually running:

Windows   certutil -hashfile <file> SHA256
Linux     sha256sum <file>

Windows

Windows 10 or 11, 64-bit.

Installer .exe · x86-64

Standard NSIS installer. Installs for the current user only, so it needs no administrator rights, and adds a Start menu entry and file associations.

No download link yet · 84 MB

File: SmartcomRevisited-1.8.0-setup.exe

Updates itself: the app offers the next version and installs it for you.

SHA-256 fcb16d2dd76e4fce014b7aa75be9aabf8be7f003bdbf8e32b455e93df93f53e6
Portable .exe · x86-64

Single executable, no installer, no registry writes. Runs from a USB stick on a customer site.

No download link yet · 83 MB

File: SmartcomRevisited-1.8.0-portable.exe

Does not update itself — see how updates work, below.

SHA-256 622b393ab0b15d15e826b627741d067fed59c3b4f28cdbdc4a1111b9407f0aa3

The installer puts the app in your own user profile, so it needs no administrator rights.
Serial ports are used through the OS driver — no extra driver is bundled. If your USB-to-serial adapter works in Device Manager, it works here.

macOS

macOS 12 Monterey or later. Apple silicon and Intel are separate downloads.

Apple silicon .dmg · arm64

M1 and later. The disk image opens and you drag the app to Applications.

No download link yet · 102 MB

File: SmartcomRevisited-1.8.0-arm64.dmg

Does not update itself — see how updates work, below.

SHA-256 307c487567711333226d2236a58966eba1f5cbe4be603d626ee604b5e04cff8d
Intel .dmg · x86-64

Intel Macs. Not a universal binary — the Apple silicon build above is a separate download.

No download link yet · 107 MB

File: SmartcomRevisited-1.8.0-x64.dmg

Does not update itself — see how updates work, below.

SHA-256 25a1e1e4b55016af04444793a36a0a15cbdb6c3f5dd7fe7f7b57bfcdffe17b4e

The builds are not notarised, so the first launch is refused: open System Settings, Privacy & Security, and choose "Open Anyway" beside the warning. Control-clicking the app and choosing Open works too.
Take the build that matches the Mac. Apple silicon runs the Intel one under Rosetta, but slower and with no benefit.
A USB-to-serial adapter needs its vendor driver (Prolific, FTDI, Silicon Labs) as it does for any other terminal.

Linux

A glibc-based 64-bit distribution — Debian 11+, Ubuntu 22.04+, RHEL 9+ or equivalent.

Debian package .deb · amd64

Debian, Ubuntu, Mint. Installs to /opt and adds a desktop entry.

No download link yet · 86 MB
File: SmartcomRevisited-1.8.0-amd64.deb
```
sudo apt install ./SmartcomRevisited-1.8.0-amd64.deb
```
Does not update itself — see how updates work, below.
SHA-256 79270ff74a6c7102e3c9894623d630b3f5378e193cd36df566d8025e03898fd2
RPM package .rpm · x86_64

Fedora, RHEL, Rocky, openSUSE.

No download link yet · 77 MB
File: SmartcomRevisited-1.8.0-x86_64.rpm
```
sudo dnf install ./SmartcomRevisited-1.8.0-x86_64.rpm
```
Does not update itself — see how updates work, below.
SHA-256 1e002234b2bc95203756cf8183c3ea76d8043942c44e5eb147e974c56ea85ce3
AppImage .AppImage · x86_64

Runs anywhere without installing. chmod +x it and go.

No download link yet · 111 MB
File: SmartcomRevisited-1.8.0-x86_64.AppImage
```
chmod +x SmartcomRevisited-1.8.0-x86_64.AppImage && ./SmartcomRevisited-1.8.0-x86_64.AppImage
```
Updates itself: the app offers the next version and installs it for you.
SHA-256 e78bd0163202246f508beff274e45c62741a9c1136cd7091e00b6a1cfc0cbefe

The .deb and .rpm declare libnss3 and libasound2, which Electron needs. A desktop install already has them; a minimal or server install pulls them in with the package.
Your user needs to be in the "dialout" group (Debian/Ubuntu) or "uucp" group (Fedora/Arch) to open serial ports: sudo usermod -aG dialout $USER, then log out and back in.
The AppImage needs the execute bit: chmod +x SmartcomRevisited-*.AppImage

How you get the next version

It depends on how you installed this one, and the app itself enforces the difference — the built-in updater will not touch an install a package manager owns.

Installed as	Updates itself?	What happens
Windows installer (NSIS)	Yes, in-app	Checks on start and downloads the update; you run the installer to finish, from the "Show the installer" button in the update panel. The build is unsigned, so SmartScreen warns when you do.
AppImage	Yes, in-app	Replaces the AppImage file in place.
.deb / .rpm	No	Your package manager owns these files. Download the new package and install it the same way you installed this one.
Windows portable	No	There is nothing to update in place — download the new .exe and replace the old one.
macOS	No	Not while the builds are unsigned — macOS refuses to replace an unsigned app in place. The app tells you a new version exists; download the .dmg and drag it over.

However you do it, upgrading keeps your settings, saved connections and buttons.

A note for AppImage users

From 1.7.0 the AppImage carries standard update information, and a .zsync file is published beside it. That is the metadata AppImage update tools read; before this release the AppImage could only be updated by the app itself and was invisible to anything else.

What has been checked is that the metadata is correct and the AppImage still runs. Whether a given third-party AppImage manager picks it up has not been tested against a published release yet, so there is no compatibility claim here to rely on — if you use one, treat it as untested and check this page for the next version.