ImageAnywhere
Changelog
ImageAnywhere installer portal

Install ImageAnywhere.

Signed ImageAnywhere installer packages for Windows, published on a regular release cadence. New machines start with the field setup ZIP. Machines already running ImageAnywhere update themselves automatically at launch.

Version 1.9.303.0 Pilot channel Published 2026-08-21 04:15 -04:00
What's new in 1.9.303.0

Nautilus Tide 2: new installs adopt C:\unified_imaging\inbox by themselves (fail-soft); Get study settings now fills the Trial subjects ID examples and names a missing shared sign-in piece; login screen names the server it tried; camera setup pack downloads from the update site and rides every field setup ZIP. Rollback predecessor: 1.9.302.5 Nautilus Ripple 2.

Start here

Which machine are you on?

Setting up a new machine?

Download one ZIP, run one installer.

One download covers the whole setup: the signed app package, the signing certificate, dependencies, the optional agent, install and verify scripts, and the camera site setup scripts — all in one extracted folder.

Download field setup ZIP

Then follow the first-run checklist below. Camera site? The double-click setup steps are in the ZIP's camera-share-scripts folder — or download just the camera setup scripts.

Already installed?

You're done — updates are automatic.

ImageAnywhere checks this portal every time the app launches and installs the current version by itself. Machines already running the app pick up version 1.9.303.0 (published 2026-08-21 04:15 -04:00) on their next launch — nothing to download.

Update now if you don't want to wait for the next launch — your browser downloads a small .appinstaller file; open it and Windows installs the update. On version 1.9.230 or later you can also click Check for updates in the app's About panel.

First-run checklist

New machine setup

  1. Download the field setup ZIP.
  2. Extract it locally.
  3. Stay signed in as the Windows user who will use ImageAnywhere, right-click INSTALL-ImageAnywhere.cmd in the extracted folder, and choose Run as administrator (choose Open/Run if Windows shows a security prompt). Keep the window open until it says Install finished. If your Windows account is not an administrator, double-click it instead; Windows will ask for one admin approval for the app certificate only.
  4. Sign in, choose Pair agent, then click Refresh agent in Connections. The agent picks up pairing on its next heartbeat, so allow 5-10 minutes and click Refresh agent again; a healthy setup shows Always-on agent / Agent healthy.
  5. Double-click VERIFY-ImageAnywhere.cmd and preserve the generated JSON.
IT / advanced

Individual artifacts.

Most installs never need these. They exist for IT-managed deployment, manual inspection, and troubleshooting.

Show advanced downloads
Optional local agent

Install the agent only when the site needs it.

The ImageAnywhere Agent is a separate opt-in field package for paired local ingest and background transfer workflows. It is not installed, started, or registered for automatic startup by the app package.

Agent setup

Field install

  1. Install and sign in to ImageAnywhere first.
  2. Download and extract the optional agent ZIP.
  3. Run scripts\Install-Agent.ps1 from the extracted folder.
  4. Start it with scripts\Start-Agent.ps1.
  5. Check it with scripts\Status-Agent.ps1.
  6. Stop or remove it with the matching scripts when testing is finished.

No separate .NET runtime install expected for this win-x64 package.

Channels

One portal, multiple release lanes.

Planned

Stable

Future Store-aligned release lane for production installs once certification and rollout gates are complete.

Current

Pilot

Version 1.9.303.0 is the current release on this portal. Every install tracks this lane and updates automatically.

Reserved

Custom builds

Future home for framework-specific, nightly, or customer-specific packages when they need a separate lane.

For IT admins

What matters for deployment.

Certificate trust

If Windows shows Publisher: Unknown or 0x800B010A, run the first-run installer or deploy the linked certificate through normal device management.

Update behavior

Installed apps check this portal at every launch and update themselves automatically. The App Installer link on this page performs the same update on demand.

Release separation

This sideload channel is separate from Microsoft Store submission. Store packages should still go through Partner Center.

Changelog

What changed in each release.

Every publish keeps a dated archive copy, so a site can stay on a known package while the current release moves forward.

Version 1.9.303.0

2026-08-21

Nautilus Tide 2: new installs adopt C:\unified_imaging\inbox by themselves (fail-soft); Get study settings now fills the Trial subjects ID examples and names a missing shared sign-in piece; login screen names the server it tried; camera setup pack downloads from the update site and rides every field setup ZIP. Rollback predecessor: 1.9.302.5 Nautilus Ripple 2.

Archived package page

Version 1.9.302.5

2026-08-14

1.9.302.5 Nautilus Ripple 2 - patient-merge stale-GUID recovery (exact-map-or-park); no agent update, feed agent stays 2.0.6.2

Archived package page

Version 1.9.302.2

2026-08-12

Photography images can now auto-save as Unassigned when no patient match is found - site setting (Options > Save unassigned images > Include photography images) or per-camera (Config > Devices), both off by default. Waiting photography tiles now say why and name the settings. Rollback predecessor: 1.9.302.0 Nautilus.

Archived package page

Version 1.9.302.0

2026-08-09

Nautilus: every trial photo send now shows on the web TrialKit Sync page within seconds, labeled with the sending computer, the camera, and the network - and photos always file by their capture date, whatever the file is named.

Archived package page

Version 1.9.301.11

2026-08-09

Mooring Tide 10 Ripple 3: TrialKit ASPIRE fixes (out-of-window guard incl. unopened visits, send-outcome chip, connection acting-as + host suggestions, visit panel) + AutoSave failure-reason telemetry

Archived package page

Version 1.9.301.6

2026-08-07

Mooring Tide 10 Ripple 2 (1.9.301.6): patient edits show everywhere instantly; inbox-root files auto-file (JPG identity parse, PDF MRN extraction); smarter unsaved retries with honest reasons; every inbound DICOM connection logged; clinical-trial photos land in the right visit by capture date; devices-list search + filename mapping preview; seven UI clipping fixes. Rule-11 wire bundle banked (Documentation/validation/2026-08-07-tide10-ripple2-wire-1.9.301/).

Archived package page

Version 1.9.299.0

2026-08-07

Agent 2.0.6.2: app updates no longer strand the app closed - supervision relaunches after every auto-update.

Archived package page

Version 1.9.298.0

2026-08-06

Mooring Tide 10 (1.9.298.0): every received image kept (shared-UID receive fix) + quarantine restore tool + reversed-name guard (T2 on) + device profiles + MWL worklist scheduling with clarity pack. Owner-gated 2026-08-06; wire evidence bundle 2026-08-06-w6-wire-smoke. Agents unchanged.

Archived package page

Version 1.9.297.0

2026-08-05

Mooring Tide 9 (1.9.297.0): duplicate-review fixes (per-patient scope, correct keeper default, stale-pair recovery, fix-name-order), patient list cache refresh after edits and merges, unsaved-queue retry backoff with needs-attention state, gallery export fallback, OCT thumbnail retry/breaker and log-flood control.

Archived package page

Version 1.9.296.0

2026-08-01

Filtering the patient list by camera is much faster - the app now checks patients' images eight at a time instead of one by one, and the recent list fills in its details the same way. Rollback predecessor: 1.9.295.0 Mooring Tide 7.

Archived package page

Version 1.9.295.0

2026-07-29

Agent 2.0.6.1: agent updates now install silently in the background with no visible window, and the agent reliably restarts itself after reboots and updates.

Archived package page

Version 1.9.294.0

2026-07-27

Mooring Tide 7 + agent 2.0.5.0: Keep-App-Open protection no longer turns off silently when Windows misreports the app install; agent status now explains itself in telemetry

Archived package page

Version 1.9.293.0

2026-07-25

Mooring Tide 6: the already-in-ImageAnywhere notice for caught duplicates now shows on every page, and DICOM receiving got faster and reports per-step timings so speed can be diagnosed remotely

Archived package page

Version 1.9.292.0

2026-07-25

Mooring Tide 5: fixed a timing collision in DICOM receiving - duplicate checks and image processing no longer race each other, so an already-saved incoming image can neither wedge the pipeline nor slip through as a visual duplicate

Archived package page

Version 1.9.291.0

2026-07-25

Mooring Tide 4: DICOM receiving reports home - every received image, rejected connection, and caught duplicate is visible to support; duplicate catches now notify the user in-app

Archived package page

Version 1.9.290.0

2026-07-24

Mooring Tide 3: DICOM-received images save straight to the matched patient; companion presentation files kept quietly with the study

Archived package page

Version 1.9.289.0

2026-07-24

The Keep app open switch now truly keeps the app open - flip it on and the support agent brings the app back within a minute if it ever closes

Archived package page

Version 1.9.288.0

2026-07-24

Exactly-once ingestion for busy watch folders, plus remote agent visibility and honest agent status

Archived package page

Version 1.9.287.0

2026-07-24

Exactly-once ingestion for busy watch folders, plus remote agent visibility and honest agent status

Archived package page

Version 1.9.285.0

2026-07-18

The home dashboard opens much faster: cache cleanup no longer holds up the page (a 10-second wait on image-heavy machines is now under a second), and cleanup can no longer be switched off permanently by one busy file.

Archived package page

View all archived versions