Skip to main content
As an IT administrator, you can deploy the Requestly API Client to Windows devices as an MSIX package, and control its automatic updates with a policy.
This guide covers Windows only. An enterprise build for macOS and Linux is coming soon.

What to expect

  • The app installs per user or for all users on a device, and updates itself through Windows.
  • You can turn automatic updates off with a registry value, Group Policy or Intune.
  • Users who move from the .exe installer keep their data and stay signed in.

Before you start

System requirements

Device settings

Check these settings on each device before you deploy.
The app is not in the Microsoft Store. If Windows archives it, Windows cannot restore it. Set Archive infrequently used apps to Disabled to keep the app installed.

Deploy the app

Choose one method. In each command, replace <path>, <server> and <share> with your own values. The commands use requestly-api-client-2610.15.1-win-x64.msix as an example. Replace it with the file name of the version you downloaded.
Run Add-AppxPackage as the user. You do not need admin rights.

Install location and user data

The app installs to this folder, for version X.Y.Z.0 on an x64 device:
User data and logs stay in the same folder as with the .exe installer, so users keep their data when they move to the MSIX:
The app log is %APPDATA%\Requestly API Client\logs\main.log.

Configure automatic updates

Set the policy in Computer Configuration (HKLM), before the app first starts.
The policy lives in this key:
Set the value with reg add or your management tool. This command turns automatic updates off:

Supported settings

* Default. When the value is not set, or has any other type or value, updates stay on.

Good to know

  • An app installed for all users (DISM, or Intune with Device context) reads only HKLM. A User Configuration policy has no effect on it.
  • After a self-update, Intune can show the app as “Failed” (0x87D1041C), because Intune looks for the exact version it deployed. The app is not affected.
  • To move from the .exe installer: remove its assignment, uninstall it for each user, then install the MSIX.

FAQ

Yes. Set AutoUpdate to 0 with a registry value, Group Policy or Intune. See Configure automatic updates. When updates are off, the app shows no update prompt, and Check for Updates is disabled.
No. When you deploy a new version while the app is open, the app keeps running. The user gets the new version the next time they start the app.
No. If the app has already updated itself to a newer version, a later DISM or Intune deployment of an older version does not downgrade it.
These policies block packaged apps that they do not allow. Allow the publisher BrowserStack, Inc. with no upper version limit, so that the rule also covers future updates. Do not allow the app by its file path, because the path changes with each version.
Run this in PowerShell:
Add -AllUsers and run it as admin to see every user on the device.