ePublisher Silent Installation Guide (IT and Enterprise Deployment)

A guide for IT departments deploying WebWorks ePublisher Express (and ePublisher Designer and ePublisher AutoMap) silently across an organization: unattended first-time installs, upgrades, repairs, and uninstalls.

Audience: System administrators using SCCM, Intune, Group Policy, PDQ Deploy, PowerShell remoting, or an equivalent deployment tool. This guide assumes you are deploying the standard product installer downloaded from WebWorks, not a debug or source build.

The examples use ePublisher Express. ePublisher Designer and ePublisher AutoMap install with the identical mechanism and command-line switches. Substitute the product name in the installer filename and paths (ePublisher Express becomes ePublisher Designer or ePublisher AutoMap).

The installers are built with NSIS. They add two WebWorks-specific switches: /UPDATE, for one-command silent upgrade and repair (installers from ePublisher 2025.1 onward, see Updating an Existing Installation), and /NOAVEXCLUSIONS, which leaves Microsoft Defender Antivirus settings untouched (see What the Installer Excludes). Everything else is the standard NSIS built-in switch set, per the official NSIS documentation (the Command-Line Usage and Silent Installers chapters). Older installers support only the standard switches.


Installer Downloads and Filenames

Download installers from the per-version landing page:

https://webworks.com/products/epublisher/download?version=2025.1

Substitute the version value (for example, 2024.1 or 2023.1) to reach the landing page for an older release. This is the browsable entry point. Link IT staff to the landing page rather than a direct file URL.

Each landing page offers the 64-bit and 32-bit installers for every product. The actual download links resolve to a per-build path of the form …/<version.build>/<exe-filename> (there is no parent index page for the build directory), where <exe-filename> is one of the following (shown for the example release 2025.1.4678):

Product

64-bit Installer (Recommended)

32-bit Installer

Express

WebWorks ePublisher Express (64-bit).2025.1.4678.exe

WebWorks ePublisher Express (32-bit).2025.1.4678.exe

Designer

WebWorks ePublisher Designer (64-bit).2025.1.4678.exe

WebWorks ePublisher Designer (32-bit).2025.1.4678.exe

AutoMap

WebWorks ePublisher AutoMap (64-bit).2025.1.4678.exe

WebWorks ePublisher AutoMap (32-bit).2025.1.4678.exe

Legacy Formats

WebWorks ePublisher Legacy Formats (64-bit).2025.1.4678.exe

WebWorks ePublisher Legacy Formats (32-bit).2025.1.4678.exe

Use the 64-bit builds. Nearly all deployments today use 64-bit; reserve the 32-bit builds for legacy 32-bit Windows. The two differ in install location and registry view (see the appendix). The command-line switches are identical for both.

Build numbers increment between releases (…4678 here). Reference whatever file you downloaded and substitute the version and build in the examples below.


At a Glance

Task

Command (run elevated)

Silent install (default location)

"WebWorks ePublisher Express (64-bit).2025.1.4678.exe" /S

Silent install (custom location)

"WebWorks ePublisher Express (64-bit).2025.1.4678.exe" /S /D=C:\Tools\WebWorks

Silent upgrade or repair (2025.1+ installers)

"WebWorks ePublisher Express (64-bit).<version.build>.exe" /S /UPDATE

Silent install without changing Microsoft Defender settings

"WebWorks ePublisher Express (64-bit).<version.build>.exe" /S /NOAVEXCLUSIONS

Silent uninstall

"…\ePublisher Express\Uninstall.exe" /S

Licensing (activate a seat)

Manual, per machine. Entered by the user on first launch; cannot be scripted.

Free a license seat

Manual. User clicks Unregister in the License dialog before uninstalling.


Command-Line Switch Reference

Installer

Switch

Effect

Notes

/S

Runs the installer silently (no UI, no prompts)

Case-sensitive: must be uppercase /S. NSIS documents the switch in uppercase; lowercase /s is not recognized and the GUI will appear.

/D=<path>

Sets the install root directory

Per NSIS docs: must be the last argument, unquoted even if the path contains spaces (for example, /D=C:\Program Files\WebWorks), and absolute paths only.

/NCRC

Skips the installer's internal CRC integrity check

Disables the CRC check unless CRCCheck force was used in the script. Rarely needed.

/UPDATE

Silent upgrade or repair: uninstalls the installed version, then installs fresh

WebWorks-specific; ePublisher 2025.1+ installers only. Acts only when combined with /S (ignored in an interactive run). No-op when the product is not installed (behaves as a fresh install). See Section 2.1.

/NOAVEXCLUSIONS

Skips the Microsoft Defender Antivirus exclusion step

WebWorks-specific. The installer otherwise registers Defender process exclusions for the product executables (Section 6.1). With this switch it changes nothing in Defender and logs skipped (/NOAVEXCLUSIONS). Works with or without /S.

Uninstaller (Uninstall.exe)

Switch

Effect

Notes

/S

Runs the uninstaller silently

Case-sensitive uppercase.

_?=<dir>

Runs the uninstaller in place so the calling process can block until it finishes

Per NSIS docs, this stops the uninstaller from copying itself to the temporary directory, and can be used along with ExecWait to wait for the uninstaller to finish. Must be the last argument and unquoted. Point it at the folder containing Uninstall.exe. See the caveat.

/NOAVEXCLUSIONS

Leaves the Microsoft Defender process exclusions in place

WebWorks-specific. Without it, the uninstaller removes the process exclusions its installer registered (Section 6.1).

Elevation is required. The installer is marked to require administrator rights (RequestExecutionLevel admin). A silent run from a non-elevated context cannot raise a UAC prompt and will fail. Always launch from an already-elevated process or your deployment tool's SYSTEM or admin context.

Exit codes. NSIS returns 0 on success and a non-zero code on failure or cancellation. Check $LASTEXITCODE (PowerShell) or %ERRORLEVEL% (cmd) and treat non-zero as a failed deployment.


1. Installing for the First Time

1.1 Pre-Provision Prerequisites First

Do this before pushing the installer. See Section 3 for details and verification commands. In short: .NET Framework 4.7.2+ is always required and should be present on every target; Java, Ghostscript, and HTML Help Workshop are needed only for certain output and input types (see the table). The installer can auto-download .NET and Java when they are missing, but that requires internet access on each endpoint, and a machine that is missing .NET and offline can stall a silent install on a dialog.

A silent install never installs Ghostscript or HTML Help Workshop: their setup programs only run interactively, so the installer skips them. Pre-provision Ghostscript wherever users publish Word or FrameMaker documents (Section 3).

1.2 Run the Silent Install

Default location (C:\Program Files\WebWorks for 64-bit):

# Must run elevated
& "C:\Deploy\WebWorks ePublisher Express (64-bit).2025.1.4678.exe" /S

Custom location:

& "C:\Deploy\WebWorks ePublisher Express (64-bit).2025.1.4678.exe" /S /D=D:\Apps\WebWorks

Running ePublisher applications. Before it registers or writes anything, the installer checks whether an ePublisher application is running: ePublisher Designer, ePublisher Express, the ePublisher AutoMap Administrator, or an AutoMap job. Each keeps the shared Adapters DLLs open, and an installation that tried to replace them would fail with Error opening file for writing and leave a partial installation behind. A silent install closes them, as /S /UPDATE already does, including any AutoMap job that is running, and exits with a non-zero code without changing anything if one of them cannot be closed. Schedule deployments for a window when users are not publishing, and have them save their work first. An interactive install instead names the running applications and waits for the user to close them and click Retry.

Why the scripted examples use Start-Process -Wait. NSIS installers are Windows GUI-subsystem executables, so a shell that launches one directly (for example, & "installer.exe" /S) returns immediately while the install continues on its own, and because /S shows no window, it looks like it ran off into the background. This is normal and not specific to /S. Start-Process -Wait makes PowerShell block until the installer and its child processes finish, which is also what lets you read a reliable exit code. Use the -Wait form (Section 1.4) whenever a script must wait for completion or check success; the bare & "installer.exe" /S form is fine only for ad-hoc, hands-on runs. (Elevation also detaches the process: an admin-manifested installer launched from a non-elevated shell is elevated by Windows as a separate process. Start-Process -Wait -Verb RunAs elevates and waits; in a SYSTEM or admin deployment context, drop -Verb RunAs.)

1.3 What Gets Installed, and Where

With the default 64-bit root, files land under:

C:\Program Files\WebWorks\ePublisher\2025.1\
    ePublisher Express\        <- product binaries + Uninstall.exe
    Helpers\  Adapters\  Formats\  Transit\  Rasterizer\   (shared)

(32-bit installs to C:\Program Files (x86)\WebWorks\….) Note that the version folder is the major.minor (2025.1), not the full build number.

The installer also:

  • Registers the product under the Windows Uninstall key (see the appendix).

  • Registers Microsoft Defender Antivirus process exclusions for the product executables that write the conversion workspace and the generated output. The installer registers them by full path and records one outcome line per executable in %ProgramData%\WebWorks\ePublisher\Logs\install-<product>-<ver>.log (Defender only). The exact list per product, what happens on centrally managed devices, the /NOAVEXCLUSIONS opt-out, and the optional folder exclusions are in Section 6.

  • Installs or refreshes the WebWorks Rasterizer printer (used for Word and FrameMaker image conversion) and the Transit helper. The printer setup needs the Windows Print Spooler service. When it cannot create the printer, the install still completes, and the printer setup records the reason in Rasterizer\Rasterizer_Helper.log under the version folder (see Section 3).

  • ePublisher AutoMap, interactive installs only: seeds the shared Quantum Sync Trial evaluation workspace in Public Documents (`C:UsersPublicDocumentsWebWorks ePublisher AutoMapQuantum Sync Trial`). A silent install does not seed it. A user can create or restore it later with Reset Evaluation Materials in the AutoMap Administrator Preferences. Uninstalling AutoMap leaves the workspace in place.

Licensing is not configured by the installer. A successful silent install produces a working but unlicensed product. Each user must activate a seat on first launch (see Section 4).

1.4 Example: Deployment Wrapper with Logging

$installer = "C:\Deploy\WebWorks ePublisher Express (64-bit).2025.1.4678.exe"
$log       = "C:\Deploy\Logs\epx-install-$env:COMPUTERNAME.log"

$p = Start-Process -FilePath $installer -ArgumentList '/S' -Wait -PassThru -Verb RunAs
"$(Get-Date -Format s)  exit=$($p.ExitCode)" | Out-File $log -Append

if ($p.ExitCode -ne 0) { throw "ePublisher Express install failed (exit $($p.ExitCode))" }

The installer also leaves its own record of the Microsoft Defender exclusion step on the target machine, in %ProgramData%\WebWorks\ePublisher\Logs\install-<product>-<ver>.log, one line per executable (Section 6.1). Collect it with your deployment logs when a scanner-related problem is reported.

1.5 Examining Installer Logs

The installer's details view, the scrolling list of steps on its progress page, is not saved to disk, and a silent run discards it. That includes the messages a silent install writes when it skips Ghostscript or HTML Help Workshop. When an installation needs diagnosing, use these instead:

Record

Where

What it tells you

Exit code

Your deployment tool, or the wrapper in Section 1.4

0 means success. A non-zero code means the install failed or stopped, for example because a running ePublisher application could not be closed.

Defender exclusion log

%ProgramData%\WebWorks\ePublisher\Logs\install-<product>-<ver>.log

One line per executable: added, already present, blocked, skipped, or failed at install, and removed or not present at uninstall. See Section 6.1.

Printer setup log

<version folder>\Rasterizer\Rasterizer_Helper.log

Each step of the WebWorks Rasterizer printer setup, and why it failed, for example a disabled Print Spooler.

Everything else is verified on the machine itself:

  • Product installed: the Uninstall registry key and its DisplayVersion (appendix).

  • Prerequisites: the .NET, Java, Ghostscript, and HTML Help Workshop checks in Section 3.1.

  • Printer: Get-Printer -Name 'WebWorks Rasterizer' (Section 3.1).

  • Defender exclusions: Get-MpPreference | Select-Object -ExpandProperty ExclusionProcess (Section 6.1).


2. Updating an Existing Installation (Repairs and Upgrades)

How you update depends on the version of the installer you are running (not the version being replaced; the new installer removes the prior version for you, verified for installations back to 2021.1):

New Installer Version

Recommended Method

2025.1 and later (with the /UPDATE switch)

One command: /S /UPDATE (Section 2.1)

Older installers (without /UPDATE)

Manual uninstall-then-install (Section 2.3)

2.1 Silent Upgrade or Repair with /S /UPDATE (2025.1 and Later)

Installers from ePublisher 2025.1 onward support the WebWorks-specific /UPDATE switch. Combined with /S, the installer first silently uninstalls the currently-installed version of the product, then installs fresh. This is the unattended equivalent of choosing Repair in the interactive installer, and a clean one-command upgrade:

(Start-Process "C:\Deploy\WebWorks ePublisher Express (64-bit).<version.build>.exe" `
  -ArgumentList '/S /UPDATE' -Wait -PassThru -Verb RunAs).ExitCode

Check your build. The /UPDATE switch was added partway through the 2025.1 release cycle. Earlier 2025.1 builds simply ignore the switch: the run silently degrades to a plain /S in-place overwrite (no uninstall first). If in doubt, download the latest build from the version landing page.

Behavior:

  • Upgrade. Removes the currently-installed version (supported back to installations of 2021.1), then installs the new version. Files dropped between versions do not linger, unlike a plain /S overwrite. For installations older than 2021.1, play it safe: uninstall manually first via Windows Settings > Apps (Add or Remove Programs), then run a normal silent install (Section 1.2).

  • Repair. Re-running the same build with /S /UPDATE removes it and freshly reinstalls it.

  • Fresh install. On a machine with nothing installed, the uninstall step is a no-op and /S /UPDATE behaves exactly like /S. One command is therefore valid for every machine, whatever its current state, which is what makes the all-products script in Section 2.4 possible.

  • Install location. A same-version repair stays in the existing location automatically. When upgrading across versions from a custom install root, append /D=<root> (last argument, unquoted) to be explicit, since the new version cannot always discover the old version's custom root.

  • Running instances of ePublisher products are closed automatically before the uninstall begins. Have users save their work before a deployment window.

  • /UPDATE without /S is ignored. An interactive run shows the normal Repair or Uninstall chooser instead.

Licensing survives an upgrade. Activation is tied to the machine and user, not to the program files, so an upgrade does not normally require re-entering the Contract ID. If a machine ever prompts again, treat it as a first-time activation (Section 4). A full uninstall (without reinstalling) still leaves the seat consumed (see Section 5).

A new version is licensed only when the organization's contract includes it, for example through an active maintenance agreement. When it does not, the License Information window (Help > License Keys) reports Not licensed for this version, and ePublisher AutoMap reports the same problem on the command line when it starts. Reinstalling does not help; the contract has to be renewed. See Not Licensed for This Version.

2.2 In-Place Refresh with Plain /S (All Versions)

Re-running an installer silently without /UPDATE overwrites the files in place; nothing is uninstalled first:

& "C:\Deploy\WebWorks ePublisher Express (64-bit).2025.1.4678.exe" /S

This is fine for re-applying the same build, but an in-place overwrite does not remove files that were dropped from a newer version. For version upgrades, prefer /S /UPDATE (2025.1+) or the manual procedure below.

2.3 Manual Uninstall-Then-Install (Installers Without /UPDATE)

Older installers, those that predate the /UPDATE switch, have no one-command update. For a clean upgrade, silently uninstall the old version, then silently install the new one:

$uninstall = "C:\Program Files\WebWorks\ePublisher\2025.1\ePublisher Express\Uninstall.exe"
$newSetup  = "C:\Deploy\WebWorks ePublisher Express (64-bit).2025.1.4678.exe"

# 1) Remove the existing version (blocking)
$tmp = "$env:TEMP\epx-uninstall.exe"
Copy-Item $uninstall $tmp -Force
Start-Process $tmp -ArgumentList '/S', "_?=$(Split-Path $uninstall)" -Wait -Verb RunAs

# 2) Install the new version
Start-Process $newSetup -ArgumentList '/S' -Wait -Verb RunAs

2.4 One Script for All Products (Install and Update)

Because /S /UPDATE handles first-time install, upgrade, and repair with the same command, a single script can bring every ePublisher product on a machine up to date in one pass. Comment out (#) the products your organization does not use.

# =============================================================================
# WebWorks ePublisher -- silent install / upgrade, all products
# Requires installers with the /UPDATE switch (ePublisher 2025.1 and later).
# Run from an ELEVATED PowerShell prompt.
#   - Fresh machine: performs first-time installs.
#   - Machine with ePublisher installed: cleanly upgrades/repairs each product.
# =============================================================================

if (-not ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()
        ).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)) {
    throw 'Run this script from an elevated (Administrator) PowerShell prompt.'
}

$InstallerDir = 'C:\Deploy'      # folder containing the downloaded installer EXEs
$Build        = '2025.1.0000'    # <version.build> exactly as it appears in the filenames
$Arch         = '64-bit'         # or '32-bit'

# ---- Products to deploy. Comment out (#) any product you do not use. ----
# NOTE: 'Legacy Formats' requires Designer or AutoMap and must stay LAST.
$Products = @(
    'Express'
    'Designer'
    'AutoMap'
    'Legacy Formats'             # requires Designer or AutoMap above
)

foreach ($Product in $Products) {
    $exe = Join-Path $InstallerDir "WebWorks ePublisher $Product ($Arch).$Build.exe"
    if (-not (Test-Path $exe)) {
        Write-Warning "Installer not found, skipping: $exe"
        continue
    }
    Write-Host "Installing/updating $Product ..."
    $p = Start-Process -FilePath $exe -ArgumentList '/S /UPDATE' -Wait -PassThru
    if ($p.ExitCode -ne 0) {
        throw "$Product installer failed with exit code $($p.ExitCode) -- stopping."
    }
    Write-Host "  $Product OK."
}
Write-Host 'All selected products are installed and up to date.'

Notes:

  • Product order matters only for Legacy Formats. It depends on configuration owned by Designer or AutoMap, so keep it last and deploy it only alongside one of them.

  • Custom install root: change the argument string to '/S /UPDATE /D=<root>'. Keep /D last and unquoted inside the string (passing it as a single string preserves the unquoted form NSIS requires, even for paths with spaces).


3. Prerequisites to Pre-Provision

The installer checks for four components. In an interactive install it will attempt to download and install the missing ones, over the internet, and offer to run the HTML Help Workshop setup program it ships with. A silent install downloads .NET and Java the same way, but it never installs Ghostscript and never runs the HTML Help Workshop setup (see the table and the notes below). Only .NET is required for ePublisher to run at all; Java, Ghostscript, and HTML Help Workshop are required only for specific output and input types. For controlled enterprise rollouts, especially on locked-down or offline machines, pre-provision the ones your users need so endpoints never require outbound network access during deployment, and so you control the versions installed.

Component

Required For

If Missing, Installer Will...

Why Pre-Provision

.NET Framework 4.7.2 (or later)

Always, ePublisher itself

Prompt-default to Yes and silently download from microsoft.com, then install.

On a machine that is missing .NET and offline, the download-failure fallback dialog can stall a silent install (it has no silent default). Pre-provisioning eliminates this risk.

Java runtime (JDK/JRE)

PDF output, Eclipse / Oracle / Java Help output, and DITA-XML input

Silently download a JDK and install it (no dialog; the install continues even if the download fails).

Large download per endpoint; version drift. Pre-provision a standardized, org-approved JDK or JRE if users generate those outputs or consume DITA-XML input.

Ghostscript

Generating web-ready images from Microsoft Word and Adobe FrameMaker graphics that contain a vector or PostScript facet, and the print-driver based PDF output from Word and FrameMaker

Interactive install: download it and run the Ghostscript setup wizard, which the user completes. Silent install: skip it and continue without it. The Ghostscript setup program ignores /S, so it would block the install on a wizard nobody can see.

Required for silent deployments. The only way Ghostscript reaches a silently installed machine is your own distribution channel. Pin a known-good version if users publish Word or FrameMaker documents containing such graphics, or PDF from them.

HTML Help Workshop

Microsoft HTML Help (.chm) output

Interactive install: run the HTML Help Workshop setup program (shipped with the product) if it is not installed. Silent install: skip it. Its setup program has no unattended mode.

Pre-provision it only if users generate Microsoft HTML Help output; most deployments do not need it.

Unlike .NET, a missing Java does not stall a silent install: the installer logs the failure and continues. A missing Ghostscript or HTML Help Workshop is skipped outright. The affected output or input type simply will not work until that component is installed.

Print Spooler service. The WebWorks Rasterizer printer, which Word and FrameMaker image conversion prints through, can only be created while the Windows Print Spooler service (Spooler) is running. Security baselines that disable the spooler (PrintNightmare hardening) prevent the printer from being installed. The install still completes, but the printer setup records the reason in <version folder>\Rasterizer\Rasterizer_Helper.log, an interactive install shows a warning, and image conversion later warns that the printer is unavailable. The printer only prints locally, so the spooler can stay closed to remote clients (the Allow Print Spooler to accept client connections policy can remain Disabled). Once the spooler is enabled, re-run the printer setup from an elevated prompt:

"C:\Program Files\WebWorks\ePublisher\2026.1\ePublisher Express\Rasterizer_Helper.exe" /rasterizerPath="C:\Program Files\WebWorks\ePublisher\2026.1\Rasterizer\webworks.ppd"

It reports each step and exits 0 when the printer exists. Its log explains any other exit code.

Ghostscript for unattended deployments. The GPL Ghostscript setup program (gs10050w64.exe, the version the installer downloads) ignores its /S switch and always shows its setup wizard. Artifex documents no unattended-install switch for its AGPL Windows installers. A silent ePublisher install therefore neither downloads nor runs it, and simply continues. A silent run writes no log of this, so verify Ghostscript with the registry check below. To get Ghostscript onto silently installed machines, run its setup wizard on each machine (for example, through your remote-assistance tooling), or ask Artifex whether an installer suited to unattended deployment is available to your organization. Do not script clicks through the wizard. ePublisher finds Ghostscript through HKLM\SOFTWARE\GPL Ghostscript\<version>\GS_DLL (64-bit registry view for the 64-bit product), which the Ghostscript setup program writes.

HTML Help Workshop for unattended deployments. When HTML Help Workshop is not registered, the installer runs the HTML Help Workshop 1.3 setup package it ships under <version folder>\Helpers\htmlhelp, but that package's quiet switch only quiets its extraction; the setup program inside waits for its wizard. A silent ePublisher install therefore skips it and continues. Only Microsoft HTML Help (.chm) output needs the workshop; deployments that do not generate it lose nothing. To pre-provision, run htmlhelp.exe interactively once per machine (for example, through your remote-assistance tooling) and verify with the registry check below.

About graphic facets. Microsoft Word and Adobe FrameMaker can store an imported picture as several facets, alternate renditions of the same image (for example, a high-resolution vector or PostScript rendition alongside a low-resolution screen preview). To turn such a graphic into a web image, ePublisher rasterizes its vector or PostScript facet into a web-ready raster image (PNG, GIF, or JPG), and that rasterization step uses Ghostscript (via the WebWorks Rasterizer). If your source documents do not contain these graphics, Ghostscript is not needed.

Downloads need network access. The components the installer downloads (.NET, Java, and, in an interactive install, Ghostscript) require network access on each endpoint. Pre-provisioning them through your normal software-distribution channel keeps the ePublisher deployment itself fully offline-capable and deterministic.

3.1 Verification Snippets

# .NET Framework >= 4.7.2  (release >= 461808)
(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full' -Name Release).Release -ge 461808

# Java present (registry)
@('HKLM:\SOFTWARE\JavaSoft\JDK','HKLM:\SOFTWARE\JavaSoft\JRE',
  'HKLM:\SOFTWARE\JavaSoft\Java Development Kit','HKLM:\SOFTWARE\JavaSoft\Java Runtime Environment') |
  Where-Object { Test-Path $_ }

# Ghostscript present: the GS_DLL that the installer and ePublisher both look for
Get-ChildItem 'HKLM:\SOFTWARE\GPL Ghostscript' -ErrorAction SilentlyContinue |
  ForEach-Object { (Get-ItemProperty $_.PSPath).GS_DLL } | Where-Object { $_ -and (Test-Path $_) }

# WebWorks Rasterizer printer present (Word and FrameMaker image conversion); requires the Print Spooler
Get-Printer -Name 'WebWorks Rasterizer' -ErrorAction SilentlyContinue

# HTML Help Workshop present (Microsoft HTML Help .chm output only); this is the key the installer checks
Test-Path 'HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\HTML Help Workshop'

With .NET present (and Java, Ghostscript, and HTML Help Workshop present for the features your users need), the ePublisher silent install runs fully unattended with no network dependency and no dialogs.


4. Licensing (Contract IDs)

Activation cannot be silenced or scripted. It is a manual, per-machine step performed by the end user on first launch.

A successful install does not activate a license. The first time a user launches ePublisher Express (or Designer or AutoMap) on a machine, the License dialog appears and the user must enter:

  • the organization's Contract ID,

  • their email address, and

  • the machine name.

Each successful activation consumes one seat on the Contract ID. There is no command-line, registry, or file-drop mechanism to pre-activate seats during a silent deployment. Plan for users (or a technician at the machine) to complete this step interactively once per machine.

IT can still fully automate the install; only the one-time activation is manual.


5. Uninstalling and Deactivating License Seats

5.1 Deactivate the Seat Before Uninstalling

Order matters. Free the license seat first, then remove the software.

Each activation holds a seat on the Contract ID. To return that seat to the pool, the user clicks the Unregister button on the License dialog inside ePublisher Express, Designer, or AutoMap while the product is still installed. This deactivates the seat so it can be reused on another machine or user.

If ePublisher is uninstalled before the seat is deactivated, the seat remains consumed (the Unregister button is no longer reachable). In that case, WebWorks Support can deactivate the seat on request. Contact https://www.webworks.com/support with the Contract ID and the machine name(s) to release.

5.2 Silent Uninstall

The uninstaller is a standalone Uninstall.exe placed in the product folder and recorded as the Windows UninstallString:

C:\Program Files\WebWorks\ePublisher\2025.1\ePublisher Express\Uninstall.exe

Simple silent uninstall (returns quickly; the uninstaller relocates itself to %TEMP% and completes in the background):

& "C:\Program Files\WebWorks\ePublisher\2025.1\ePublisher Express\Uninstall.exe" /S

Scripted Blocking Uninstall

To make your deployment script wait for the uninstall to finish, copy the uninstaller out and run it with the _?= switch pointing at the original product folder:

$uninstall = "C:\Program Files\WebWorks\ePublisher\2025.1\ePublisher Express\Uninstall.exe"
$tmp = "$env:TEMP\epx-uninstall.exe"
Copy-Item $uninstall $tmp -Force
Start-Process $tmp -ArgumentList '/S', "_?=$(Split-Path $uninstall)" -Wait -Verb RunAs

_?= caveat: a running executable cannot delete itself, so with _?= the original Uninstall.exe (and possibly its now-empty folder) may be left behind. The uninstaller still removes all product files, shared components, and registry entries. The copy-to-temp pattern above is exactly how the product's own internal repair flow performs a blocking uninstall.

5.3 Finding the Uninstall Command from the Registry

If you do not want to hard-code the version in the path, read the recorded UninstallString (64-bit Express shown):

(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WebWorks ePublisher Express x64' `
  -Name UninstallString).UninstallString

6. Real-Time Scanning Exclusions

ePublisher writes and rewrites thousands of small files while it converts source documents and generates output. Endpoint security software that opens each file as it is written (Microsoft Defender real-time protection, third-party EDR agents), Windows Search indexing, and continuous-backup agents can hold one of those files open at the instant ePublisher renames, replaces, or deletes it. The result is intermittent and timing-dependent: a job of several hundred documents fails on a random document, and the same job succeeds when rerun. Typical log lines:

[Error] Cannot create a file when that file already exists.
[Error] Unable to create WIF document '...\Data\<target>\<group>\<document>\<document>.wif' for source document '<document>.docx'.

or The process cannot access the file because it is being used by another process and The directory is not empty.

ePublisher retries the affected steps and logs each retry as a warning, for example:

Another process is holding '<file>' open: <reason> Attempt 2 of 10 failed; retrying.

When a file stays held open, it names the file:

Unable to replace '<file>' after 10 attempts because another process kept it open. Real-time virus scanning, search indexing, or backup software can hold recently written files open; exclude the folder that contains it from real-time scanning.

6.1 What the Installer Excludes

Each installer registers a Microsoft Defender Antivirus process exclusion (Add-MpPreference -ExclusionProcess) for every product executable that writes the conversion workspace or the generated output. A process exclusion exempts every file that process opens from real-time and scheduled scanning. (Microsoft notes that it also exempts the process from attack surface reduction rules and network protection.) Each exclusion is the executable's full installed path, so it covers only that installed copy and version:

Installer

Process Exclusions (under `<root>\ePublisher`)

AutoMap

<ver>\ePublisher AutoMap\WebWorks.Automap.exe (runs every job), <ver>\ePublisher AutoMap\Transformer.exe, <ver>\ePublisher AutoMap\Installer_Helper.exe

Designer

<ver>\ePublisher Designer\WebWorks.ePublisherDesigner.exe, <ver>\ePublisher Designer\Transformer.exe, <ver>\ePublisher Designer\Installer_Helper.exe

Express

<ver>\ePublisher Express\WebWorks.ePublisherExpress.exe, <ver>\ePublisher Express\Transformer.exe, <ver>\ePublisher Express\Installer_Helper.exe

Legacy Formats

Installer\InstallerHelper_FormatsLegacy.exe

<root> is C:\Program Files\WebWorks (64-bit) or C:\Program Files (x86)\WebWorks (32-bit) unless /D= relocated it, and <ver> is the major.minor version, for example 2026.1. Transformer.exe runs the XML and DITA conversions. Installer_Helper.exe and InstallerHelper_FormatsLegacy.exe unpack the shared helper, adapter, and format archives at install time and on first launch. This is the list to pre-approve with your security team.

Not excluded, by design:

  • the ePublisher AutoMap Administrator (WebWorks.Automap.Administrator.exe schedules jobs; WebWorks.Automap.exe runs them);

  • the helper programs unpacked under <ver>\Helpers`: Helpers\python\python.exe, which converts Markdown sources, Helpers\nodejs\node.exe`, and the legacy help compilers;

  • the Java runtime you provide for PDF, DITA, and Java-based outputs.

When a scanner keeps holding files written by one of those, add the folder exclusions in Section 6.2, or a process exclusion for it through your management platform.

Verified and logged. The step runs defender_exclusions.ps1 from the product folder, hidden and non-interactive, in the 64-bit Windows PowerShell. The script checks whether Microsoft Defender Antivirus is installed and active, adds the exclusions, reads them back with Get-MpPreference, and records one outcome line per executable, both in the installer's details view and in an append-only log on the machine:

%ProgramData%\WebWorks\ePublisher\Logs\install-<product>-<ver>.log

Outcome

Meaning

added, already present

The exclusion is in place and was read back.

blocked

Defender ignores or blocks local exclusion changes on this device (DisableLocalAdminMerge is set, or exclusions are tamper protected: TPExclusions = 1). Nothing was changed; deploy the list centrally instead (see below).

skipped

Microsoft Defender Antivirus is not installed, its service is disabled, or it runs in passive mode behind another antivirus product, so its exclusions do not apply. Also written as skipped (/NOAVEXCLUSIONS) when the installer was run with /NOAVEXCLUSIONS.

failed

The cmdlet reported an error, or the read-back did not show the change. The error text follows.

The step never stops the install and never shows a window, so it is safe in silent deployments. If PowerShell itself cannot run the step, the installer reports that the Microsoft Defender Antivirus exclusion step did not run and that the exclusions were not changed; apply them later as described below, or deploy them centrally. The uninstaller runs the same script to remove the exclusions its installer registered (removed or not present in the same log).

Centrally managed Defender. Local changes are ignored or blocked, and the log says blocked, in two cases:

  • Defender settings come from Intune, Configuration Manager, or Group Policy with local-administrator merge disabled (DisableLocalAdminMerge).

  • Exclusions are tamper protected. This applies to devices managed only by Intune or only by Configuration Manager, on Defender platform 4.18.2211.5 and later. The registry check is HKLM\SOFTWARE\Microsoft\Windows Defender\Features\TPExclusions = 1.

Deploy the process exclusions in the table above through your management platform. The installer then reports them as already present.

Opting out. Add /NOAVEXCLUSIONS when your organization does not allow installers to change antivirus settings:

& "C:\Deploy\WebWorks ePublisher AutoMap (64-bit).<version.build>.exe" /S /NOAVEXCLUSIONS

The installer changes nothing in Defender and logs skipped (/NOAVEXCLUSIONS) for each executable. The same switch on Uninstall.exe leaves existing exclusions in place.

Applying the list by hand. The script can be run later from an elevated 64-bit PowerShell, for example once the security team has approved the list:

& "$env:SystemRoot\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -File "C:\Program Files\WebWorks\ePublisher\2026.1\ePublisher AutoMap\defender_exclusions.ps1" -Action Add -Product AutoMap -Version 2026.1.<build> -Processes "WebWorks.Automap.exe|Transformer.exe|Installer_Helper.exe"

Exclusions left by earlier installers. Earlier ePublisher installers registered exclusions by file name only (WebWorks.ePublisherDesigner.exe, WebWorks.ePublisherExpress.exe, Installer_Helper.exe, InstallerHelper_FormatsLegacy.exe; none for AutoMap), and their uninstallers did not remove them. A file-name exclusion applies to any process with that name in any location. Once no earlier ePublisher version remains on a machine, list and remove them:

Get-MpPreference | Select-Object -ExpandProperty ExclusionProcess
Remove-MpPreference -ExclusionProcess "WebWorks.ePublisherDesigner.exe"

6.2 Folders to Exclude

Exclude the following folders from real-time scanning, and from search indexing and continuous backup, for every account that runs ePublisher Designer, ePublisher Express, or AutoMap jobs on the machine. They hold only files ePublisher derives from the sources and regenerates on the next build. Source documents are never modified in place and stay scanned wherever they live.

Folder

Used By

What It Holds

`%TEMP%WebWorks`

All products

The conversion workspace: per-job workspaces (ePublisher\<workspace>, relocatable with the WorkspaceDirectoryPath setting in WebWorks.Automap.exe.config), per-process scratch folders (Temp.<pid>), the Markdown and XML adapter data folders, and the output preview server.

`<Documents>WebWorks ePublisher AutoMapStaging`

AutoMap

The default staging folder (AutoMap Administrator Preferences, or the --stagingdir option), where each job's project is staged and built.

`<Documents>WebWorks ePublisher AutoMapJobs`

AutoMap

The default jobs folder: job folders with their job files and logs.

The Jobs and Staging folders of each additional AutoMap workspace

AutoMap

The same content for jobs in that workspace. AutoMap Administrator workspaces (File > Workspace) can put these folders anywhere, so list each one.

`C:UsersPublicDocumentsWebWorks ePublisher AutoMapQuantum Sync Trial`

AutoMap

The shared Quantum Sync Trial evaluation workspace that an interactive AutoMap install seeds: its jobs, staging, and output.

Data` and Output` beside each .wep or .wrp project file

Designer, Express

Conversion scratch and generated output for interactive builds.

The conversion workspace in %TEMP% is not an AutoMap Administrator workspace: an Administrator workspace is a named jobs folder, staging folder, and set of destinations.

%TEMP% resolves per account:

  • %LOCALAPPDATA%\Temp (C:\Users\<user>\AppData\Local\Temp) for an interactive user;

  • that account's own profile for a scheduled task or service account, for example C:\Windows\ServiceProfiles\LocalService\AppData\Local\Temp;

  • C:\Windows\Temp for LocalSystem.

Adjust the <Documents> paths when Documents is redirected.

Defender path syntax. Defender expands environment variables in an exclusion under the LocalSystem account, not the signed-in user's, so %TEMP% and %LOCALAPPDATA% do not reach user profiles. Use a wildcard for the profile folder instead (* matches exactly one folder level). Microsoft advises against excluding Temp folders wholesale, so keep the exclusion scoped to the WebWorks subfolder:

Add-MpPreference -ExclusionPath "$env:SystemDrive\Users\*\AppData\Local\Temp\WebWorks"
Add-MpPreference -ExclusionPath "$env:SystemDrive\Users\*\Documents\WebWorks ePublisher AutoMap"
Get-MpPreference | Select-Object -ExpandProperty ExclusionPath

The second line also covers the Quantum Sync Trial workspace, because C:\Users\Public matches the wildcard. AutoMap workspace folders outside the users' Documents folders need their own entries.

The process exclusions that the installer registers (Section 6.1) exempt every file those processes open, wherever the workspace is. Add the folder exclusions above when a helper that is not excluded (Python for Markdown sources, the Java runtime for PDF and DITA) is the process whose files the scanner holds, or when Defender is managed centrally and the installer's additions are blocked. Third-party endpoint security products have their own folder and process exclusions; consult their documentation.

6.3 Attack Surface Reduction Rules and the Word Macro Template

Attack surface reduction (ASR) rules are a separate Microsoft Defender feature from real-time scanning. They restrict what applications, Microsoft Office in particular, are allowed to do, and organizations deploy them in block mode through Intune, Configuration Manager, or Group Policy. One of them breaks ePublisher's Word conversion outright:

Block Win32 API calls from Office macros, GUID 92E97FA1-2EDF-4476-BDD6-9DD0B4DDDC7B

ePublisher converts Word documents by loading its macro template wwdoc.dotm into Microsoft Word and running its macros, which declare Win32 API calls. With this rule in block mode, Word refuses to run them. Windows shows the notification "Action blocked. Your administrator caused Windows Security to block this action.", and the generation log records:

[ERROR] Adapter "Word" failed in method "DuplicateDocumentAndApplySettings" at step "3: Word.BeginPreProcessPhase".
[WARN] Cannot duplicate document '<source>.docx' to '<workspace>\...' and apply settings.

The failed step can also read 3: Word.WriteBuiltInStyleNames. ePublisher also logs a warning naming this rule:

The ePublisher conversion macros did not run in Microsoft Word. Security policy may be blocking the macro template 'wwdoc.dotm', for example the Microsoft Defender attack surface reduction rule "Block Win32 API calls from Office macros". Ask your IT team to check Microsoft Defender block events for wwdoc.dotm, and see the attack surface reduction section of the ePublisher Silent Installation Guide.

and an error for each document that could not be converted:

[ERROR] Document '<source>.docx' could not be converted. The output for this document is missing.

Those documents are left out of the output. With that error, AutoMap skips deployment, leaves the deploy destination unchanged, and ends with a non-zero exit code, so a blocked conversion does not replace a published deployment.

The process exclusions in Section 6.1 do not cover this. The blocked process is Word itself (WINWORD.EXE), which ePublisher does not exclude. Excluding Word from ASR would exempt every Word macro, not just ePublisher's. The scoped fix is a per-rule exclusion for the macro template files, which leaves the rule active for everything else. Per-rule exclusions can only be deployed through Group Policy or Intune endpoint security policies. Exclude every installed copy, because each product loads its own:

Product

File to Exclude (under `<root>\ePublisher<ver>`)

AutoMap

ePublisher AutoMap\wwdoc.dotm

Designer

ePublisher Designer\wwdoc.dotm

Express

ePublisher Express\wwdoc.dotm

The paths are versioned, so update the exclusions when you upgrade to a new ePublisher release. The installation also ships <ver>\Transit\transit.dotm; include it if your block events name it. Where per-rule exclusions are not available, the local fallback is a global ASR-only exclusion, subject to the same central-management caveats as Section 6.1:

Add-MpPreference -AttackSurfaceReductionOnlyExclusions "C:\Program Files\WebWorks\ePublisher\<ver>\ePublisher AutoMap\wwdoc.dotm"

Finding the block events.

  • Locally: in Event Viewer under Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational, event 1121 (blocked) or 1122 (audit), and in the Defender protection history. The event names the rule GUID and the blocked file.

  • In a Defender for Endpoint tenant: the DeviceEvents advanced-hunting table, action types AsrOfficeMacroWin32ApiCallsBlocked and AsrOfficeMacroWin32ApiCallsAudited.

An event naming wwdoc.dotm confirms that this section applies.

6.4 Word Dialogs During Conversions and the Field Security Notice

ePublisher runs Microsoft Word hidden, so nobody can answer a dialog that Word opens during a conversion, such as a security notice about fields, Save As when a save fails, or "The last time you opened … it caused a serious error". When such a dialog has been waiting for an answer for 30 seconds while Word is idle, ePublisher closes Word and does not convert the document. A dialog that Word shows while it works, such as printing, does not count. The generation log records a warning that names the document and the dialog, and quotes what the dialog says when ePublisher can read it, followed by an error for the document:

[WARN] Microsoft Word showed the dialog "<title>" while applying the project's settings to the document '<source>.docx'. ePublisher runs Word hidden, so nobody can answer the dialog; ePublisher closed Word after 30 seconds and did not convert the document. The dialog said: "<message>"
[ERROR] Document '<source>.docx' could not be converted. The output for this document is missing.

The document is left out of the output, and AutoMap skips deployment, as in Section 6.3.

Fields that refer to other files or websites. ePublisher converts such fields (INCLUDETEXT, INCLUDEPICTURE, LINK, and the like), linked pictures, and linked objects from the results stored in the document, the last version its author saw, and never asks Word to fetch them. So by default Word does not show its field security notice during a conversion, and no Word setting is needed.

The notice and the registry value below matter only when a project turns on the Microsoft Word adapter setting Update external references (Project Settings, Input Configurations tab), which refreshes these references from their sources. Microsoft 365 Word asks before it updates fields that bring in content from other files:

Microsoft Word Security Notice: Microsoft Office has identified a potential security concern. This document contains fields that can share data with external files and websites. It is important that this file is from a trustworthy source.

With the setting on, ePublisher refreshes these fields only when Word will update them without asking. Otherwise it uses the results stored in the document and logs a warning that names the document:

The project's setting Update external references is on, but the fields and linked pictures in the document '<source>.docx' that refer to other files or websites were not updated: Microsoft Word asks before it updates them, and ePublisher runs Word hidden. The results stored in the document were used. An administrator can let Word update them without asking with the Word setting DisableWarningOnIncludeFieldsUpdate; see the ePublisher Silent Installation Guide.

ePublisher never changes Word's security settings. If your organization accepts these field updates for the accounts that run ePublisher, turn the notice off with this Word registry value for each such account, including the account that an AutoMap scheduled task or service runs as:

Key

Value

Type

Data

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Security

DisableWarningOnIncludeFieldsUpdate

DWORD

1

Word then updates the fields without asking, which gives the same output as answering Yes. 16.0 covers Word 2016, 2019, 2021, 2024, and Microsoft 365. The same value set by Group Policy, through the Office policy "Don't ask permission before updating IncludePicture and IncludeText fields in Word" (under HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Word\Security or HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\16.0\Word\Security), takes precedence over the user's own value, in Word and in ePublisher's check.

6.5 Signed Word Macros and Trusting Quadralay Corporation as a Publisher

This section applies where Microsoft Word is set to Disable all macros except digitally signed macros (File > Options > Trust Center > Trust Center Settings > Macro Settings, or an Office policy that sets it).

Signed templates. ePublisher's two Word macro templates are digitally signed by Quadralay Corporation. Each carries the legacy, agile, and V3 VBA project signatures, all timestamped:

Template

Used By

File (under `<root>\ePublisher<ver>`)

wwdoc.dotm

Word conversions in Designer, Express, and AutoMap

ePublisher AutoMap\wwdoc.dotm, ePublisher Designer\wwdoc.dotm, ePublisher Express\wwdoc.dotm

transit.dotm

The WebWorks Transit menu in Word

Transit\transit.dotm

The WebWorks Transit menu. Word loads transit.dotm from its startup folder when it starts, like any other add-in, so the Trust Center macro setting applies to it. Word shows a security alert when it starts ("The digital signature is valid, but the signature is from a publisher whom you have not yet chosen to trust") until the user chooses Trust all documents from this publisher. Each user makes this choice once, and again after a certificate renewal (see below). The user procedure is in Running Transit Menu in Secure Environments.

Conversions in Designer, Express, and AutoMap. ePublisher starts Word through automation, and Word enables macros for automation by default, so the Trust Center macro setting does not apply to wwdoc.dotm and conversions need no trust decision. The exception is the Office policy Automation Security set to Use application macro security level:

Key

Value

Type

Data

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\Common\Security

AutomationSecurity

DWORD

2

With that policy, conversions need Quadralay Corporation trusted as a publisher. Without that trust, they fail with the warning "The ePublisher conversion macros did not run in Microsoft Word" shown in Section 6.3, and the document is left out of the output. Accounts that run AutoMap jobs, such as the account of a scheduled task or service, never see a prompt in which to choose that trust.

Trusting the publisher centrally. The installers do not add the certificate to any certificate store. To deploy it yourself:

  1. Export the certificate from any installed ePublisher executable. The executables are signed with the same certificate as the templates:

    $sig = Get-AuthenticodeSignature "C:\Program Files\WebWorks\ePublisher\<ver>\ePublisher AutoMap\WebWorks.Automap.exe"
    $sig.Status                     # Valid
    $sig.SignerCertificate.Subject  # CN=Quadralay Corporation, O=Quadralay Corporation, ...
    $sig.SignerCertificate | Export-Certificate -FilePath quadralay.cer
  2. Deploy quadralay.cer to the Trusted Publishers store:

    • Group Policy: Computer Configuration > Policies > Windows Settings > Security Settings > Public Key Policies > Trusted Publishers, then Import.

    • One machine: from an elevated prompt, certutil -addstore TrustedPublisher quadralay.cer.

  3. Test on one machine before you roll it out. Word's own Trust all documents from this publisher choice records the certificate in that user's Trusted Publishers store, not the machine's. Sign in with an account that has not made that choice, start Word, and check that the WebWorks Transit menu loads without the security alert. Where the Automation Security policy applies, also run a conversion under the account that runs AutoMap jobs. If Word still shows the alert or the conversion fails, each user trusts the publisher as described above, and an account that runs AutoMap jobs is better left out of the Automation Security policy, so that its conversions need no trust decision.

Scope of the trust. A certificate in Trusted Publishers is trusted for everything signed with it, not only Office macros. For example, PowerShell's AllSigned execution policy then runs scripts signed with it without asking. Deploy it only to the machines that run ePublisher.

Certificate renewal. Office trusts the specific certificate, not the publisher name. The current certificate expires on November 29, 2026. Signatures made with it stay valid after that date because they are timestamped, so installed templates keep working. Templates signed after the renewal carry the new certificate: users see the WebWorks Transit security alert once more, and centrally deployed trust needs the new certificate, exported in the same way from an executable of the ePublisher build that ships it.


Appendix: Paths, Filenames, and Registry Keys

<ver> is the major.minor version (for example, 2025.1). For a custom /D= root, substitute accordingly.

64-Bit vs 32-Bit Differences

 

64-bit Build (recommended)

32-bit Build

Installer filename

WebWorks ePublisher Express (64-bit).<build>.exe

WebWorks ePublisher Express (32-bit).<build>.exe

Default install root

C:\Program Files\WebWorks

C:\Program Files (x86)\WebWorks

Registry view

64-bit (native)

32-bit (under WOW6432Node when read from a 64-bit process)

Uninstall key suffix

x64 (for example, …\WebWorks ePublisher Express x64)

(no suffix) (for example, …\WebWorks ePublisher Express)

Product Folders

Product

Product Folder (under the install root + `\ePublisher<ver>`)

Uninstaller

Express

`ePublisher Express`

ePublisher Express\Uninstall.exe

Designer

`ePublisher Designer`

ePublisher Designer\Uninstall.exe

AutoMap

`ePublisher AutoMap`

ePublisher AutoMap\Uninstall.exe

Registry Keys (HKLM)

Paths shown for the 64-bit Express build. For 32-bit, drop the x64 suffix and look under WOW6432Node. For Designer or AutoMap, replace Express with the product name.

Purpose

Key

Uninstall info

Software\Microsoft\Windows\CurrentVersion\Uninstall\WebWorks ePublisher Express x64 -> UninstallString, DisplayVersion

Install root / working dir

Software\WebWorks\ePublisher\<ver> -> TargetDir, workingDirectory

Product exe path

Software\WebWorks\ePublisher Express\<ver> -> ExePath, Path, Version

Quick Checklist for a Clean Enterprise Rollout

  1. Pre-provision .NET 4.7.2+ (always); add Java if users generate PDF / Eclipse / Oracle / Java Help output or consume DITA-XML input, and Ghostscript if users publish Word or FrameMaker documents containing vector or PostScript graphic facets, or PDF from them. A silent install never installs Ghostscript or HTML Help Workshop (needed only for Microsoft HTML Help output) (Section 3).

  2. Push the 64-bit installer elevated with /S (plus /D= if relocating) (Section 1).

  3. Verify exit code 0.

  4. Have each user complete one-time activation with the Contract ID, email, and machine name (Section 4).

  5. For upgrades: /S /UPDATE with 2025.1+ installers (Section 2.1), or uninstall then install with older installers (Section 2.3). The all-products script in Section 2.4 covers both install and upgrade.

  6. Before decommissioning, have users Unregister to free seats before uninstalling, or ask WebWorks Support to release seats if already uninstalled (Section 5).

  7. Pre-approve the Microsoft Defender process exclusions that the installer registers, deploy them centrally where Defender is managed, or pass /NOAVEXCLUSIONS to leave Defender alone. On machines that publish large document sets, also exclude ePublisher's working folders from real-time scanning, indexing, and continuous backup (Section 6).

  8. Where attack surface reduction rules are enforced and users publish Word documents, deploy the per-rule exclusion for wwdoc.dotm (all three product copies) for the rule "Block Win32 API calls from Office macros" (Section 6.3).

  9. Only where a project turns on Update external references for Word documents that include other files through fields (INCLUDETEXT, INCLUDEPICTURE) with Microsoft 365 Word: decide whether the accounts that run ePublisher may update such fields, and if so set DisableWarningOnIncludeFieldsUpdate for them, checking that no Office policy overrides it (Section 6.4).

  10. Where Word is set to Disable all macros except digitally signed macros: have users of the WebWorks Transit menu trust Quadralay Corporation once. Where the Office policy Automation Security is also set to Use application macro security level, conversions need that trust too; test central trust in Trusted Publishers on one machine before you deploy it, and deploy the new certificate after a renewal (Section 6.5).


References

Last modified date: 2026-10-20