Dates: July 16, 2026
Esper Agent Version: v13.0.4549
New Features
- MSIX and MSIXBundle app support: you can now upload and deploy .msix and .msixbundle files alongside MSI and EXE apps. This is useful for apps that require clean install and uninstall behavior, or for teams supporting multiple device architectures from a single MSIXBundle upload. Configure signing certificates and dependencies right from the console. Now Available in Apps > Esper Windows Apps. See how to manage MSIX apps in the Esper console.
- Windows OS Update Scheduling: Admins can now schedule when Windows updates are installed on managed devices directly from a Blueprint. Configure the day of the week, week of the month, and time of day for update installation using the new Scheduled Install Day, Scheduled Install Week, and Scheduled Install Time settings. Scheduled install settings are only available when Allow Auto Update is set to Install and restart at scheduled time or Auto-install and restart without user control. Learn how to set up Windows OS update scheduling using a blueprint.
- Custom OMA-URI Policies for Windows: You can now apply SyncML/CSP XML payloads to Windows devices through a blueprint's Esper Settings or from the Devices & Groups page, giving you a way to configure settings not otherwise exposed in the console. Payloads can be applied as atomic transactions, so if any command in a multi-command payload fails, the entire block rolls back rather than partially applying. Learn more about OMA-URI policies.
- Cut Device List API responses by up to 96% with sparse fieldsets
GET /api/v2/devices/ and GET /v0/devices now support a fields parameter, so you can request only the top-level fields you need instead of the full device object. For integrations that only need a device identifier, for example, requesting ?fields=id cuts the response size by more than 96% per device.
This matters most for high-volume or high-device-count use cases: polling jobs, sync scripts, or service-to-service calls that run frequently across large fleets. Smaller responses mean less bandwidth and faster parsing on your end, without changing anything else about how the endpoint behaves.
GET /api/v2/devices/?fields=id,name,created_at
- A few things to know if you’re currently using (or in interested in using) this workflow:
- Works with both offset-based and cursor-based pagination.
- id is always included in the response, even if you don't request it.
- Only top-level fields are supported. Nested fields aren't yet available, so a field like hardware_info returns as a complete object rather than letting you select individual properties within it.
- Requesting a field that doesn't exist returns a 400 error with details on which field was invalid.
- Omitting the fields parameter returns the full device object, unchanged from current behavior. Existing integrations require no changes.
-
Android Esper Agent Updates:
- Fixed an issue where Google Maps could cause a device to become temporarily unresponsive during a cold start on devices with slow Google Play Services.
- Fixed a crash that occurred on certain devices when the Esper Agent disabled certain apps.
- Fixed an issue where devices could get stuck on the Wi-Fi connection screen during provisioning and required a restart to continue.
- Fixed an issue where the Esper logo appeared as a floating button over all screens on Android 12 devices after an Esper Agent update.
- Fixed an issue where the device display scaling broke on certain devices after resetting accessibility settings from a blueprint.
- Improved error messages for Zebra MX configuration failures applied through Blueprints.
Bug Fixes and Improvements
- We now show AC power information for Linux devices from the device’s details page. AC Power (No Battery) will now appear when a desktop Linux device is plugged into a wall outlet.
We’re excited to launch DevRel 194 over the coming days, and the Esper team is hard at work on the next release. Please contact Esper Support to share your thoughts on how Esper can improve future releases.