microsoft · jschick04 · Jun 21, 2026 · Jun 21, 2026 · Jun 21, 2026 · Jun 21, 2026
diff --git a/README.md b/README.md
@@ -2,7 +2,7 @@
 
 A Windows Event Log viewer for tech support and IT professionals.
 
-![Screenshot showing a filtered combined view of three event logs](docs/.images/EventLogExpert-CombinedView.png)
+![EventLogExpert dashboard: Quick Launch live-log buttons and a categorized library of common investigations](docs/.images/EventLogExpert-Dashboard.png)
 
 ## Key features
 
@@ -21,20 +21,16 @@ For more information, check our [docs](docs/Home.md).
 
 ## Quick Start
 
-Download the `EventLogExpert_{version}_x64.appinstaller` (or the matching `EventLogExpert_{version}_x64.msix`) from the latest release and run it: <https://github.com/microsoft/EventLogExpert/releases/latest>.
+Download `EventLogExpert_{version}.msixbundle` from the latest release and double-click it to install: <https://github.com/microsoft/EventLogExpert/releases/latest>.
 
-The `.appinstaller` declares its dependency on the Windows App Runtime (currently `Microsoft.WindowsAppRuntime.1.7.msix`, also published in the same release) so App Installer fetches the runtime automatically on a clean machine. Updates are checked on launch.
+The bundle runs natively on both x64 and ARM64, and Windows installs the matching architecture automatically. It is self-contained (the Windows App Runtime ships inside the package), so there is no separate runtime to install. Updates are checked on launch.
 
-If you'd rather install the runtime manually first, grab `Microsoft.WindowsAppRuntime.1.7.msix` from the release and install it with:
+**Requirements:** Windows 11, Windows Server 2022, or Windows Server 2025 (x64 or ARM64).
 
-```
-Add-AppxPackage $home\Downloads\Microsoft.WindowsAppRuntime.1.7.msix
-```
-
-Then install the app:
+Prefer the command line? Install the same bundle with:
 
 ```
-Add-AppxPackage $home\Downloads\EventLogExpert_{version}_x64.msix
+Add-AppxPackage $home\Downloads\EventLogExpert_{version}.msixbundle
 ```
 
 ### First time setup

diff --git a/docs/.images/EventLogExpert-Dashboard.png b/docs/.images/EventLogExpert-Dashboard.png
diff --git a/docs/Filtering.md b/docs/Filtering.md
@@ -4,7 +4,8 @@
 
 The Filter pane sits above the event table. Every event in the active log set is evaluated against the applied filters; non-matches are hidden.
 
-<!-- screenshot: filter-pane --> ![Filter pane header showing the left-side action buttons, active-filter indicator, and right-side icon trio](.images/filter-pane.png)
+<!-- screenshot: filter-pane -->
+![Filter pane header showing the left-side action buttons, active-filter indicator, and right-side icon trio](.images/filter-pane.png)
 
 The pane header carries the row-adding actions on the left and the persistence / management actions on the right:
 

diff --git a/docs/Saved-Filters.md b/docs/Saved-Filters.md
@@ -6,7 +6,8 @@ The Filter Library is the single persisted surface for filter reuse. It replaces
 
 Open it from the [Filter pane](Filtering.md) header — the bookmarks icon labeled `Open Filter Library`. When the library fails to load or is still loading, the filter pane's `Recent` menu item and the `Apply Filter Set` picker surface guidance pointing back to this same button (the library does not auto-open from those flows).
 
-<!-- screenshot: filter-library-saved --> ![Filter Library modal, Saved tab](.images/filter-library-saved.png)
+<!-- screenshot: filter-library-saved -->
+![Filter Library modal, Saved tab](.images/filter-library-saved.png)
 
 ### Modal layout
 

diff --git a/docs/Settings.md b/docs/Settings.md
@@ -6,7 +6,8 @@
 
 `Save` writes the form fields and any pending enable/disable toggles you've made on database rows; `Exit` discards them. `Remove` and `Upgrade` are immediate side effects that persist regardless of `Save` / `Exit`. `Import Database` is also immediate, but a successful import additionally applies any pending form fields and toggles and closes the modal — make any other changes you want to keep before clicking it.
 
-<!-- screenshot: settings-modal --> ![Settings modal](.images/settings-modal.png)
+<!-- screenshot: settings-modal -->
+![Settings modal](.images/settings-modal.png)
 
 ### Time Zone
 

diff --git a/docs/Updates-And-Diagnostics.md b/docs/Updates-And-Diagnostics.md
@@ -29,7 +29,7 @@ The check ends with one of four user-facing alerts:
 
 Background checks (the automatic check that runs on app start) surface `Update Available` so a fresh release is offered as soon as the app launches. The other three alerts are suppressed on background checks so a missing network at startup does not produce a popup. `Update Failure` does fire on a background check, but only after you've accepted the `Update Available` prompt and the resulting installer attempt fails; pre-prompt failures (e.g., feed unreachable, or you click `No` on the prompt and the queued-for-next-restart scheduling fails) stay silent and only land in the debug log.
 
-The `.appinstaller` distributed with each release also wires up app-installer-driven background update checks on every launch, so this entry is mostly for "what's the latest right now" — the app finds new releases on its own.
+Because the app already runs that background check on launch, the `Check for Updates` entry is mostly a manual "what's the latest right now" lookup; the app finds new releases on its own.
 
 ### Release Notes
 
@@ -39,7 +39,8 @@ Opens the Release Notes modal, which renders the markdown body of the published
 
 Opens the Debug Log modal — the in-app view of the rolling diagnostic log written by the running session. The same log is also accessible as a file under the per-user app data directory; `View Logs` is the in-app surface.
 
-<!-- screenshot: debug-log-modal --> ![Debug Log modal](.images/debug-log-modal.png)
+<!-- screenshot: debug-log-modal -->
+![Debug Log modal](.images/debug-log-modal.png)
 
 Filter bar:
 

diff --git a/docs/Viewing-Events.md b/docs/Viewing-Events.md
@@ -4,7 +4,8 @@
 
 The main view has three regions: the **tab strip** (one tab per open log, plus a `Combined` tab when more than one log is open), the **event table**, and the **Details pane** (collapsible, bottom). The status bar runs along the very bottom — see [Opening Logs](Opening-Logs.md#live-log-behavior) for what it shows for live logs.
 
-<!-- screenshot: main-view --> ![Main view: tabs, event table, Details pane](.images/EventLogExpert-CombinedView.png)
+<!-- screenshot: main-view -->
+![Main view: tabs, event table, Details pane](.images/EventLogExpert-CombinedView.png)
 
 ### Tab strip