diff --git a/src/pages/get-started/install/windows.mdx b/src/pages/get-started/install/windows.mdx
index e2ccbaee..82d0deb9 100644
--- a/src/pages/get-started/install/windows.mdx
+++ b/src/pages/get-started/install/windows.mdx
@@ -19,7 +19,7 @@ The NetBird client (agent) allows a peer to join a pre-existing NetBird deployme
 Both installers support silent (unattended) installation for use with RMM tools, MDM platforms, and scripted deployments.
 
 <Note>
-    Silent installation writes to `C:\Program Files` and registers a Windows service, so it requires an elevated (administrator or `SYSTEM`) context. Deployment tools such as PDQ, Intune, and Group Policy run as `SYSTEM`, so this is already satisfied. A standard user running the same command interactively is prompted for elevation, and running it silently without elevation fails with exit code `1625` (`This installation is forbidden by system policy`).
+    Silent installation writes to `C:\Program Files` and registers a Windows service, so it requires an elevated administrator or `SYSTEM` context. Make sure the deployment job runs elevated: tools such as PDQ, Intune, and Group Policy typically install as `SYSTEM` when targeting computers, but a job configured to run in the user's context is not elevated and fails with exit code `1625` (`This installation is forbidden by system policy`). A standard user running the installer interactively is prompted for elevation instead.
 </Note>
 
 ### EXE Installer (NSIS)
@@ -68,7 +68,7 @@ netbird up --setup-key <SETUP KEY>
 
 ### Updating an Existing Installation
 
-There is no separate update package. The same installer upgrades an existing installation in place: run the newer version and it replaces the installed one, keeping the peer's registration and configuration. Push the newer MSI (or EXE) through the same RMM or MDM tool you used to install it.
+There is no separate update package. The same installer upgrades an existing installation in place: run the newer version and it replaces the installed one, keeping the peer's registration and configuration. Push the newer MSI (or EXE) through a deployment job that runs the installer even when NetBird is already present. Some install jobs deliberately skip deployment once they detect an existing installation, so a job like that will not upgrade. The script in the [Group Policy deployment guide](/manage/peers/mdm-deployment/windows-gpo-deployment), for example, exits early if NetBird is already installed, so use an upgrade-capable job for updates.
 
 ```bash
 msiexec /i netbird_installer_<NEW_VERSION>_windows_amd64.msi /quiet
@@ -80,7 +80,7 @@ Or with the EXE installer:
 netbird_installer_<NEW_VERSION>_windows_amd64.exe /S
 ```
 
-Like the initial install, an upgrade requires an elevated context, which deployment tools already provide by running as `SYSTEM`. Downgrades are blocked: installing a version older than the one already present exits with an error (`1603`) and leaves the current installation untouched.
+Like the initial install, an upgrade requires an elevated context, so the upgrade job must run as administrator or `SYSTEM`. Downgrades are blocked: installing a version older than the one already present exits with an error (`1603`) and leaves the current installation untouched.
 
 <Note>
     Alternatively, you can let end users update from the client itself with [Automatic Updates](/manage/peers/auto-update), where the NetBird service performs the install with no administrator rights required from the user.