Client Application

EchoMark Screen provides a desktop client application. It places a transparent watermark over every connected display and updates the overlays when displays are added, removed, or reconfigured. Depending on the assigned policy, the watermark can include visible text identifying the current user and device, or both.

Requirements and dependencies

• A managed 64-bit PC running Windows 11 or later. Windows on Arm and 32-bit Windows are not supported by the current software.
• An interactive Windows desktop session and Windows' built-in Desktop Window Manager, Direct2D, and DXGI graphics components.
• Network access to the configured EchoMark key server for activation and policy or watermark updates. An EchoMark Account Key is required for server-managed operation.
• The standard release is self-contained and includes the .NET 8 runtime and its application libraries, including Vortice Direct2D/DXGI, YamlDotNet, and System.IO.Hashing. No separate .NET installation is required. A bespoke minimal build is an exception (available upon request from EchoMark) and requires the 64-bit .NET 8 Desktop Runtime to be installed separately.

Administrator privileges

Administrator privileges are required to install, upgrade, repair, or remove the MSI because it installs the client for the whole machine under C:\Program Files\EchoMark Screen (or user’s chosen path) and stores configuration and installation details under HKEY_LOCAL_MACHINE. They are also required to create or remove the supervisor service that manages instances of the program for each user, AlphamarkSvc . Additionally if it does not already exist, the install will register the programs event source in the Windows Application event log.

EchoMark Screen's signed executable must remain in a trusted location - “Program Files” or “Program Files (x86) for Windows to grant the UI-access capability used to display the watermark above elevated application windows.

EchoMark Screen Installer

Installing using the Interactive wizard

If you are installing EchoMark Screen via the interactive installation wizard, follow the steps on the wizard.

1. Read and accept the terms & conditions
2. Select the path and name to install EchoMark Screen on the client
3. Set your account key that your Customer Success Manager will have shared with you during onboarding
4. If you are connecting to the EU datacenter, change the server URL from the current default of app.echomark.com to app.eu.echomark.com
5. complete the installation

Installing using Power Shell or Command Line

echomark.msi installs per-machine (requires admin) and accepts a few properties on the command line to configure the install without going through the interactive wizard. This doc covers those properties plus the
msiexec flags you'll typically combine them with. 

Properties

All of these are plain NAME=value pairs on the msiexec command line (no special quoting needed unless the value itself contains spaces).

ACCOUNTID and KEYSERVERURL are written to the registry at HKLM\Software\EchoMark\EchoMark Screen (AccountSecret and EchomarkKeyServerURL respectively) so you can confirm what actually got set after the fact.

Interactive vs. silent

• Interactive (msiexec /i echomark.msi, no /qn): the wizard prompts for the Account Key and Key Server URL on its own dialog, pre-filled with the defaults above. You can leave everything blank/default and click through.
• Silent (/qn or /quiet): there's no dialog to type an Account Key into, so ACCOUNTID must be passed on the command line — the install fails fast with an explicit error ("An Account ID is required...") if it's missing.

Examples

Interactive install, prompts for everything:

msiexec /i echomark.msi

Silent install with your real account key:

msiexec /i echomark.msi /qn ACCOUNTID=ABC-123-456-7890

Silent install pointed at a key server:

msiexec /i echomark.msi /qn ACCOUNTID=ABC-123-456-7890 KEYSERVERURL=screen.app.echomark.com

Silent install to a custom directory (quote the path if it has spaces):

msiexec /i echomark.msi /qn ACCOUNTID=ABC-123-456-7890 INSTALLSUBFOLDER="FinanceCompayITOverlay"

Silent install with a specific marking policy:

msiexec /i echomark.msi /qn ACCOUNTID=ABC-123-456-7890 MARKINGPOLICYGUID=8f14e45f-ceea-467e-9752-1e6b3b5c1234

Silent, unattended demo install (no real account yet) — note this will
not auto-launch the app, since silent installs skip the wizard dialogs
that trigger it:

msiexec /i echomark.msi /qn ACCOUNTID=DEMO

Verbose log file, useful for debugging a failed install:

msiexec /i echomark.msi /qn ACCOUNTID=ABC-123-456-7890 /l*v install.log

Repair an existing install:

msiexec /fa echomark.msi

Uninstall silently:

msiexec /x echomark.msi /qn

Demo behavior

If you run the installer interactively and leave the Account Key at itsdefault value of DEMO, EchoMark Screen launches automatically the momentyou click Finish on the wizard's last page. This only fires on a fresh install (not on repair/modify) and only from the interactive wizard — there'sno dialog to click Finish on during a silent (/qn) install, so it nevertriggers there regardless of ACCOUNTID.

Verify an EchoMark Screen installation

Confirm that Alphamark.exe exists in the selected installation folder. The default location is:

C:\Program Files\EchoMark Screen\Alphamark.exe

You can verify the installed MSI version in Settings > Apps > Installed apps by finding EchoMark Screen, or read the version recorded by the installer with PowerShell:

Get-ItemPropertyValue `
  -Path "HKLM:\Software\EchoMark\EchoMark Screen" `
  -Name "Version"

Registry values

The 64-bit MSI stores its machine-wide settings under:

HKEY_LOCAL_MACHINE\Software\EchoMark\EchoMark Screen

To display all recorded values, run:

Get-ItemProperty -Path "HKLM:\Software\EchoMark\EchoMark Screen"

The key can contain:

The registry path and executable path should exist, AlphamarkExePath should point to the installed executable, and Version should match the release you intended to deploy. Reading these values normally does not require administrator privileges.

Uninstalling and upgrading EchoMark Screen

Before upgrading

Check the currently installed release as described in Verify an EchoMark Screen installation:

$installed = Get-ItemProperty "HKLM:\Software\EchoMark\EchoMark Screen"
$installed.Version
$installed.ProductCode

EchoMark Screen uses Windows Installer major-upgrade handling. This means any package with a higher major.minor.build version replaces the existing installation, whether the change is normally described as a major, minor, or patch release. For example, 1.4.2 upgrades 1.4.1, and 2.0.0 upgrades 1.4.2. Downgrades are blocked, and rebuilding or reinstalling the same version is not a reliable way to replace files. Windows Installer ignores a fourth version field when comparing releases, so every released upgrade must increase one of the first three fields.

Upgrade

Run the newer MSI as an administrator and supply the appropriate EchoMark Account Key and any deployment-specific properties:

msiexec /i "echomark.msi" ACCOUNTID="<account-key>"

For an unattended upgrade:

msiexec /i "echomark.msi" /qn ACCOUNTID="<account-key>"

Afterward, check the registry again and confirm that Version is the intended newer version and AlphamarkExePath points to an existing file. If Windows reports that a newer version is already installed, the proposed MSI has a lower major.minor.build value; uninstall the newer release first only if a downgrade is intentional.

Uninstall

Use Settings > Apps > Installed apps > EchoMark Screen > Uninstall, or use the recorded MSI product code from an elevated PowerShell session:

$productCode = Get-ItemPropertyValue `
  -Path "HKLM:\Software\EchoMark\EchoMark Screen" `
  -Name "ProductCode"

Start-Process msiexec.exe `
  -ArgumentList "/x $productCode" `
  -Verb RunAs `
  -Wait

For a silent uninstall, run msiexec /x <ProductCode> /qn through an elevated deployment tool. The uninstall removes the application files and machine-wide registry values. It also removes EchoMark tile and policy caches for the user account running the uninstall; caches belonging to other Windows profiles may remain.

If your organization manually registered the optional watchdog scheduled task, remove it before uninstalling, while the helper script is still present:

& "C:\Program Files\EchoMark Screen\create-scheduled-task.ps1" -Uninstall