Automatic Updates (Windows MSI)
From v1.18.1, Dev Machine Guard installs made with the signed Windows Installer (MSI) update themselves. Devices deployed through Microsoft Configuration Manager (SCCM) or Microsoft Intune download, verify, test, and switch to new releases on their own, with no user prompts and no reboots. You no longer need a new SCCM Application or Intune app for every release.
This page covers how automatic updates work, the one-time move to v1.18.1, how to opt out, what the network needs, and how to verify and troubleshoot devices.
What changes in v1.18.1
One final MSI deployment: devices on v1.17.0 or older have no updater. Move them to v1.18.1 (or later) with one last MSI deployment, set up as a new SCCM Application or Intune app that supersedes the current one. Each device keeps its tenant configuration and device ID, so it keeps its existing record in the StepSecurity dashboard.
Releases then arrive automatically: the first automatic update is the next release after v1.18.1. StepSecurity sets which release your tenant's devices take and how quickly it reaches them.
No prompts and no admin rights: updates run in the background as SYSTEM. Users see no windows, User Account Control (UAC) prompts, or notifications.
No reboots: neither an update nor the MSI (install, upgrade, repair, or uninstall) restarts the machine, and an update never interrupts a running scan.
Your choice per deployment:
AUTOUPDATE=1orAUTOUPDATE=0at install time turns automatic updates on or off. The dashboard's Windows install page offers the same Automatic updates On / Off choice.Newer MSIs remain supported: you can still deploy a newer MSI, for example so that newly enrolled devices start on a recent version.
How it works
The MSI installs a small, stable bootstrap, a seed copy of the agent (the MSI's own version, used as a fallback), and three scheduled tasks:
StepSecurity Dev Machine Guard
Logged-in user
The periodic scan, every SCANFREQUENCY hours
StepSecurity Dev Machine Guard (Logon)
Logged-in user
The same scan at logon
StepSecurity Dev Machine Guard (Update)
SYSTEM
The updater: every hour (with up to 10 minutes of random delay) and 15 minutes after boot
Scans keep running as the logged-in user, and nothing stays resident between runs.
The Update task takes each new release through these steps:
Check: about every 6 hours, the updater asks the StepSecurity API (Application Programming Interface) which version your tenant should run.
Download: it downloads the release files from GitHub Releases, about 30 MB per version and once per device. If you configured a download mirror, it is used only when the GitHub download fails.
Verify: before anything is put in place, the updater checks the StepSecurity-signed checksum against a release key built into the agent, the SHA-256 hash of every downloaded file, and, on the Windows executables, a valid timestamped Authenticode signature from the same publisher as the running agent.
Stage and self-check: the new version goes into its own
versions\<version>folder and runs a self-check as SYSTEM before it can be used.Switch: the switch happens only when no scan is running. The previous version is kept for rollback.
Health probation: the next scans on the new version are watched. One healthy scan confirms the version, reported as Update confirmed.
Automatic rollback: if two scans fail (crash, hang, or can't start) with no healthy one, the device switches back to the previous version and quarantines the failed one, so it is never installed on that device again.
Reporting: every outcome, success or failure, is reported with the device ID and shown on the device's page in the StepSecurity dashboard.
If a download or verification fails, the files are discarded and the update is retried at the next check. If the self-check fails, the version is quarantined and the device stays on the version it runs.
Move to v1.18.1
From the v1.18.1 release (or any later release), download the MSI for your architecture and, for Intune, the matching .intunewin:
stepsecurity-dev-machine-guard-<version>-x64.msi(Windows on Intel/AMD)stepsecurity-dev-machine-guard-<version>-arm64.msi(Windows on ARM)
The commands below use the x64 file name. For ARM64, swap in the -arm64 file name.
SCCM
Credentials: Pass tenant credentials in a bootstrap file at C:\ProgramData\StepSecurity\bootstrap.json rather than inline. SCCM stores the installation program in its site database, and AppEnforce.log on every device records it verbatim, so an inline API key would end up in both. The MSI installer pattern on the Script page generates this file filled in for your tenant:
Distribute the file to each device before the install (for example with Group Policy Preferences), restrict it to SYSTEM and Administrators, and keep it in place. Every MSI install and upgrade that passes BOOTSTRAPFILE reads it. If the file is missing, the install fails with exit code 1603 and is rolled back.
Step 1: Create the Application.
Create a new Application with a Windows Installer (*.msi) deployment type for the new MSI. Set the Installation program to:
Step 2: Set the repair program.
Use exactly this form:
Step 3: Set the uninstall program.
SCCM fills it in from the MSI
ProductCode.Add
/norestartand a log path:
Step 4: Set the detection method.
Use either rule. Both stay stable while the device updates itself:
The MSI
ProductCode(the SCCM default for an MSI deployment type).A Registry rule on
HKEY_LOCAL_MACHINE\SOFTWARE\StepSecurity, valueAgentVersion, String, Equals the MSI version (for example1.18.1), 64-bit.
Step 5: Set up supersedence.
On the Supersedence tab, select Add and pick the existing Dev Machine Guard Application's deployment type.
Leave Uninstall cleared: the new MSI replaces the old one itself (a Windows Installer major upgrade) and keeps the device's self-update state.
Deploy the new Application as Required to the same collection, with Automatically upgrade any superseded versions of this application selected.
Once the new Application is deployed, SCCM shows the superseded Application's deployment as Not Applicable on those devices. This is expected.
Intune
Step 1: Add the app.
Add a new Windows app (Win32) with the new
.intunewinpackage.Set Install behavior to System.
Copy the install command filled in for your tenant from the Win32 app pattern on the Script page:
Set the Uninstall command to
uninstall.cmd. UseAUTOUPDATE=0to opt out.
Step 2: Set the detection rule.
Add a Registry rule on
HKEY_LOCAL_MACHINE\SOFTWARE\StepSecurity, valueAgentVersion, String comparison, Equals the MSI version (for example1.18.1). Never detect onRunningVersion.
Step 3: Set up supersedence.
Add the existing Dev Machine Guard app and set Uninstall previous version to No. The new MSI upgrades the old one in place.
For the full Intune setup, see Microsoft Intune.
During the upgrade
Exit code 3010 (restart required): this can occur on the upgrade from an MSI that does not yet stop Dev Machine Guard before replacing files. The install succeeded, and Dev Machine Guard doesn't need that restart to run. SCCM and Intune treat 3010 as a soft reboot and follow your client restart settings.
Repairs on v1.17.0 or older: use the repair form from Step 2 above. A
/frepair on these versions could restart the machine without a prompt.
Opt out of automatic updates
The AUTOUPDATE MSI property sets a device's automatic update setting:
AUTOUPDATE
Effect on install, upgrade, or repair (/i ... REINSTALL=ALL)
0 (or false)
Automatic updates off
1 (or true)
Automatic updates on
Not set
The current setting is kept; a new install starts with automatic updates on
When a device is opted out with AUTOUPDATE=0:
It stays on the version it runs at that moment. To upgrade it, deploy a newer MSI.
Health checks and automatic rollback of a bad version still apply.
It reports Auto update off in the dashboard, naming the version it isn't taking, at most once a day per version.
The opt-out is sticky. The setting lives in C:\ProgramData\StepSecurity\config.json, which upgrades and uninstalls keep. An opted-out device stays opted out across upgrades, repairs, and an uninstall followed by a reinstall, unless an install passes AUTOUPDATE=1.
To turn automatic updates back on, redeploy with AUTOUPDATE=1, or in SCCM run the repair form with the property:
Release pacing, pausing, and rollback
StepSecurity controls these for your tenant: which version your devices take, how fast a new release reaches them, pausing a release, and moving the fleet back to an earlier release. To change them, contact [email protected]. Devices pick up a change at their next check, within about 6 hours.
A device never takes a version older than v1.18.1, the first self-updating release.
An MSI never downgrades a device. An MSI older than the installed one, deployed outside the supersedence chain, fails with exit code 1603 ("A newer version of StepSecurity Dev Machine Guard is already installed").
If a device has already updated itself past a newer MSI you deploy, the upgrade still succeeds and the device keeps its newer version. The MSI's version becomes the fallback.
Network requirements
The Update task runs as SYSTEM, so these endpoints must be reachable for the machine account, over HTTPS on port 443:
Your tenant's StepSecurity API host
The host in APIENDPOINT. Used for the target version check (about every 6 hours) and update reports. Scans already use this host.
github.com
Release downloads
release-assets.githubusercontent.com
GitHub redirects release downloads to this host
Your download mirror, if configured
Used only when the GitHub download fails
Each update downloads three files (the agent, the launcher, and the Linux agent used for WSL scans), about 30 MB together, once per device.
Proxy. The updater picks a proxy per request, in this order:
Machine-wide environment variables:
HTTPS_PROXY,HTTP_PROXY, andNO_PROXY. The SYSTEM account doesn't read user variables.Otherwise, the WinHTTP machine proxy and its bypass list.
Otherwise, a direct connection.
PAC (Proxy Auto-Configuration) files, WPAD (Web Proxy Auto-Discovery), and proxies that require user authentication (NTLM or Kerberos) aren't supported. Allow the endpoints above for the machine without authentication.
TLS inspection. If a proxy or firewall inspects TLS (Transport Layer Security), its root certificate must be in the Local Computer Trusted Root store, because the SYSTEM account doesn't see per-user certificate stores. A proxy that blocks or rewrites executable downloads makes every update fail with Download failed or Verification failed, so let the release downloads through unchanged.
Disk space. Before downloading, the updater needs free space on the system drive of three times the current version's size plus 50 MB (about 140 MB today). It keeps only the current version, the previous one, the MSI's seed, and, for up to a day, a downloaded version waiting to switch. Older version folders are deleted automatically.
Download mirror (optional)
If devices can't reach GitHub, host the release files on an HTTPS server you control and add update_mirror_url to the bootstrap file:
The updater requests <update_mirror_url>/<version>/<release file name>, with no v before the version. Mirror these three files for each version and architecture (amd64 or arm64) you run:
stepsecurity-dev-machine-guard-<version>-windows_<arch>.exestepsecurity-dev-machine-guard-task-<version>-windows_<arch>.exestepsecurity-dev-machine-guard-<version>-linux_<arch>
The URL must use https://, with no user name, password, query, or fragment. Mirrored files go through the same signature checks, so the mirror itself needs no special trust. The bootstrap file is applied on install and on each MSI upgrade, so a mirror added later reaches existing devices with their next MSI upgrade.
Antivirus and EDR exclusions
The MSI and the updater write each new version under C:\Program Files\StepSecurity\versions\, then rename its folder into place. While an antivirus or EDR (endpoint detection and response) product scans a newly written executable, it holds the file open and Windows blocks the rename. From v1.19.0, Dev Machine Guard waits up to 60 seconds for the hold to clear. A product that holds the files longer, or blocks the write, stops the update with Access is denied.
Exclude the following, or set them to monitor only for writes and renames by SYSTEM:
The folder C:\Program Files\StepSecurity\, including versions\, seed\, and state\
New versions are written and renamed here
These processes, by full path: C:\Program Files\StepSecurity\stepsecurity-dev-machine-guard-bootstrap.exe, and stepsecurity-dev-machine-guard.exe and stepsecurity-dev-machine-guard-task.exe under C:\Program Files\StepSecurity\seed\*\ and C:\Program Files\StepSecurity\versions\*\
The updater and scans run as these processes
Always use full paths or path-constrained EDR rules. An exclusion by file name alone also covers any executable with the same name anywhere on the device.
When the rename stays blocked, the error names the process holding the files, for example held by MsMpEng.exe. That is the product to configure. holder not identified usually means a kernel-mode filter or an application control policy blocked the write.
Verify a device
Update task: the task exists and runs as SYSTEM.
To run an update check now instead of waiting for the next hour:
Registry: both values return the MSI version right after the upgrade.
AgentVersionis the installed MSI version, which SCCM and Intune detect.RunningVersionis the version the device runs. After later self-updates,RunningVersionis higher thanAgentVersion. This is expected.SCCM or Intune: the app is reported as installed, and the dashboard shows the new agent version under the same device record.
StepSecurity dashboard: the device page has a Self-update card with the running version, the latest update event and its reason, and a timeline of recent update events. In the device list, a cue next to the agent version shows the update outcome from the last 24 hours: ↑ Updated after a successful update, or a red ⚠ label (for example ⚠ Rolled back) for events that need attention.
After the next release: the device shows Updated, then Update confirmed. Opted-out devices show Auto update off.
On the device, C:\Program Files\StepSecurity\state\state.json (readable without admin rights) names the current version, the previous one that a rollback would return to, any version on probation, and any version in quarantine. C:\Program Files\StepSecurity\state\update.log has one timestamped line per updater step.
Troubleshooting
Each update outcome appears in the dashboard with a label, the versions it went from and to, and a reason. Hover over the label to see the raw event name.
Updated (update_ok)
The device switched to the new version.
Nothing. Expect Update confirmed after the next successful scan.
Update confirmed (update_confirmed)
The new version completed a scan and is kept.
Nothing.
Rolled back (update_rolled_back)
The new version failed on this device, and the device went back to the previous version. It won't take that version again.
One device: check for software that kills or blocks processes in C:\Program Files\StepSecurity\versions\. Many devices: contact StepSecurity support.
Download failed (update_download_failed)
The release files couldn't be downloaded from GitHub or the mirror.
Allow github.com and release-assets.githubusercontent.com for the machine, or configure a mirror. Retried at the next check.
Verification failed (update_verify_failed)
A downloaded file failed a signature, checksum, or publisher check. Nothing was installed.
One device: look for a proxy, TLS inspection, or security tool that alters downloads. Many devices: contact StepSecurity support.
Staging failed (update_stage_failed)
The new version couldn't be written to disk. Reason av_deleted means antivirus deleted the files.
Free disk space. For av_deleted, exclude C:\Program Files\StepSecurity\ from file quarantine.
Health check failed (update_health_failed)
The new version failed its self-check before the switch. The device stays on its version and won't take that one again.
Check that the device's config.json is complete. Many devices: contact StepSecurity support.
Switch failed (update_switch_failed)
The new version was ready, but the switch couldn't be saved.
Check disk health and free space. Retried automatically.
Switch deferred (update_switch_deferred)
A scan was running at four update runs in a row, so the switch kept waiting.
Usually nothing. If it repeats, check for scans that never finish.
Update check failed (update_check_failed)
The device couldn't get its target version from the StepSecurity API.
Check the machine's access to your API host, the proxy settings, and the API key in config.json.
Below version floor (update_refused_floor)
The device was offered a version older than v1.18.1 and refused it.
Contact StepSecurity support.
Auto update off (update_disabled)
Automatic updates are off on this device (AUTOUPDATE=0).
Expected for opted-out devices. To turn them back on, see Opt out of automatic updates.
Version pointer invalid (update_pointer_invalid)
A scan couldn't start the current version and ran a fallback.
Usually fixed by the next update run. If it repeats, check that the Update task exists and runs, then repair the MSI.
Permissions repaired (update_acl_drift)
Something changed the permissions on the updater's folders, and the updater restored them.
If it repeats, find the tool or Group Policy changing permissions under C:\Program Files\StepSecurity\.
Update state corrupt (update_state_corrupt)
state.json was missing or unreadable and was rebuilt.
Once: nothing. Repeated: check disk health and tools that delete files under C:\Program Files\StepSecurity\state\.
Updater failing (update_updater_failed)
The updater in the current version failed three times in a row, and the MSI's copy took over.
Contact StepSecurity support with the device's update.log.
No update events from a device usually means it still runs an MSI older than v1.18.1 and needs the final MSI deployment, the Update task is missing (check with schtasks /query, then repair the MSI), or the device can't reach your API host.
The last event is Updated, with nothing since: the new version is on probation. The device makes no update checks until a scan on the new version succeeds or the probation ends. Check that scans are running.
Exit code 1603 with "A newer version ... is already installed": usually a newer Dev Machine Guard MSI really is installed (see Release pacing, pausing, and rollback). A failed install or upgrade can also leave a phantom registration that isn't in Programs and Features yet blocks lower versions. To detect it, run this in an elevated PowerShell. The GUID is the x64 MSI's UpgradeCode; for the ARM64 MSI, use {99C4A108-6A71-4006-8AA7-F3D14DA045A9}.
ProductState=5 is installed, and a healthy device has exactly one. ProductState=1 is a phantom. Remove each phantom by its ProductCode with msiexec /x {PHANTOM-PRODUCT-CODE} /qn /norestart, then redeploy.
Other 1603 failures: the MSI log names the failing step. Common causes are a BOOTSTRAPFILE path that doesn't exist or isn't readable by SYSTEM, and incomplete credentials. A failed install or upgrade is rolled back completely, so the device keeps its version, tasks, and settings.
When opening a support case, attach:
MSI verbose log
The /l*v path in your command (for example C:\Windows\Temp\dmg-install.log). Intune: C:\ProgramData\StepSecurity\install.log
SCCM client logs
C:\Windows\CCM\Logs\AppEnforce.log, AppDiscovery.log, and AppIntentEval.log
Updater log
C:\Program Files\StepSecurity\state\update.log and update.log.1
Updater state
C:\Program Files\StepSecurity\state\state.json
Versions
Output of Get-ItemProperty -Path 'HKLM:\Software\StepSecurity'
Include the device ID from the dashboard.
Uninstall
Uninstalling (the SCCM uninstall program, msiexec /x {PRODUCT-CODE}, or Intune's uninstall.cmd) stops all Dev Machine Guard processes and removes the three scheduled tasks, everything under C:\Program Files\StepSecurity\ (including all downloaded versions and the updater state), and the AgentVersion and RunningVersion registry values.
It keeps C:\ProgramData\StepSecurity\, which holds config.json (tenant configuration, API key, and the automatic update setting) and the device ID, so a reinstalled device keeps its record in the dashboard. To remove everything, for example when decommissioning a device, delete the folder after the uninstall:
Last updated
Was this helpful?