ET Ducky changelog, October 15, 2026

These changes cover offline Windows Update for hosts without Internet access, a more detailed installed-app inventory, the Deploy dialog in Patch Management, the Distribution Hub, and the blog index. Items marked with an agent version reach a machine when it runs that agent release or a later one.

New

• Windows agents in a tag you choose can scan against Microsoft's offline catalog and install update files from your Distribution Hub without reaching Microsoft Update. The agent checks each file's SHA-256 before it hands the file to Windows Update. This needs agent 2.8.2.0 (see Offline Windows Update from the distribution hub and the Patch Management documentation).
• The installed-app inventory records each application's install path and the user who installed it, and lists apps installed for one Windows user and Microsoft Store (MSIX) packages. You can refresh a host's inventory on demand. The agent side ships in agent 2.8.1.0 (see Installed-app inventory now shows install paths, per-user apps, and Microsoft Store apps).
• When you tick one agent on the Agents page, the Inventory button in the bar opens that host's inventory drawer. With several agents ticked, the button points to the fleet view under Systems, Patch Management, Agents, By app (see the Agent Management documentation).

Improved

• Deploy on a pending update in Patch Management opens a dialog in the page that asks how to handle a reboot the install needs. You can wait for the maintenance window or reboot right away.
• When the host already has an open job for the update, the Deploy dialog names the job and its state. While that job is still waiting, the dialog offers to run it now.
• The hub picker and connection list under Integrations, Distribution Servers show each hub's name and whether its listener is reporting, with reporting hubs listed first.
• Offline Windows Update uses only hubs that reported in the last 15 minutes, and its card says when no hub has.
• The dialog for mapping a Distribution Hub as a drive offers the hub's computer name as the address and explains Windows error 1244 (see Map a drive).
• The maintenance window setting in Patch Management is labelled as each agent's local time.
• The blog index has search, tag filters, four sort orders, and a choice of 12, 24, or 48 posts per page.
• The offline Windows Update steps in the documentation now cover hub setup, the exact catalog download address, a signature check for the catalog, download size, and when agents scan. The Distribution Servers page explains how to map a drive again after Windows error 1397.

Fixed

• Offline Windows Update scans no longer fail partway through with error 0x80240031 (agent 2.8.3.0).
• The hub creates a new certificate when its LAN address changes, so Windows can map the hub drive by address again (agent 2.8.3.0).
• A folder named in a hub access rule shows on the mapped drive before it holds a file (agent 2.8.3.0).
• An agent waiting for its maintenance window to reboot writes one log entry for each wait and no longer repeats entries on every check (agent 2.8.3.0).
• The Deploy dialog shows the version change only when the host reported an installed version, so Windows updates no longer show a question mark in its place.
• Select fields show their dropdown arrow again in both themes.
• Clicking inside the Offline Windows Update card no longer reloads the card over the result of a save.