# extensions.autoUpdate setting not available via MDM

**URL:** <https://forum.cursor.com/t/extensions-autoupdate-setting-not-available-via-mdm/163975>\
**Category:** Help\
**Tags:** extensions\
**Created:** [June 24, 2026, 9:18am UTC](https://forum.cursor.com/t/extensions-autoupdate-setting-not-available-via-mdm/163975 "2026-06-24T09:18:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![RomainM](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@RomainM](https://forum.cursor.com/u/RomainM)\
**Post date:** [June 24, 2026, 9:18am UTC](https://forum.cursor.com/t/extensions-autoupdate-setting-not-available-via-mdm/163975/1 "2026-06-24T09:18:12Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Hi,

I want to configure and deploy a cursor config via our MDM for MacOS laptops. I would like to configure the extensions.autoUpdate setting (which is available in VSCode) but it is missing in the latest Cursor version.  
As far as I understand, the setting “UpdateMode” is only scope to the Cursor application and not the extensions.

Did I miss anything? Could you add it back to the Cursor config? so it can be managed via MDM

Thank you!

### Steps to Reproduce

Create a cursor config file (.mobileconfig file) with the key:  
“”"  
ExtensionsAutoUpdate  
off  
“”"

This works on VSCode but not for Cursor.

### Expected Behavior

Prevent Cursor extensions to be automatically updated

### Operating System

MacOS

### Version Information

Version: 3.8.23 (Universal)  
VS Code Extension API: 1.105.1  
Commit: 7cf19b7482706625cdb70db3211b7dd035b7aa30  
Date: 2026-06-23T14:57:42.334Z  
Layout: editor  
Build Type: Stable  
Release Track: Default  
Electron: 40.10.3  
Chromium: 144.0.7559.236  
Node.js: 24.15.0  
V8: 14.4.258.32-electron.0  
xterm.js: 6.1.0-beta.256  
OS: Darwin arm64 24.6.0

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [June 24, 2026, 10:02am UTC](https://forum.cursor.com/t/extensions-autoupdate-setting-not-available-via-mdm/163975/5 "2026-06-24T10:02:27Z")

</div>

Hey, thanks for the detailed report. You understood it correctly. `UpdateMode` `update.mode` only applies to the Cursor app updater, it doesn’t apply to extensions.

About `extensions.autoUpdate`: the setting exists in Cursor and works locally, but unlike VS Code it isn’t registered as an MDM policy yet, so there’s no `ExtensionsAutoUpdate` key in Cursor `.mobileconfig` profiles. Right now the profile only supports `AllowedExtensions`, `AllowedTeamId`, `ExtensionGalleryServiceUrl`, and `UpdateMode`.

Workaround: deploy a managed `settings.json` via MDM with:

```json
{
  "extensions.autoUpdate": false,
  "extensions.autoCheckUpdates": false
}

```

This will stop extension auto-updates on machines. The downside is that unlike a real MDM policy, this `settings.json` is still editable by the user, so it doesn’t provide strict enforcement.

Expanding the MDM policy set including `ExtensionsAutoUpdate` is already tracked as a request here: [MacOS managed settings](https://forum.cursor.com/t/133779). I’d recommend adding your use case there so it’s captured in one place. I’m moving this thread to Feature Requests.

---

<div class="post-metadata">

**Author:** ![RomainM](https://avatars.discourse-cdn.com/v4/letter/r/f9ae1b/32.png) [@RomainM](https://forum.cursor.com/u/RomainM)\
**Post date:** [June 25, 2026, 7:18am UTC](https://forum.cursor.com/t/extensions-autoupdate-setting-not-available-via-mdm/163975/6 "2026-06-25T07:18:45Z")

</div>

Sure! Thanks for the quick response.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [July 25, 2026, 7:18am UTC](https://forum.cursor.com/t/extensions-autoupdate-setting-not-available-via-mdm/163975/7 "2026-07-25T07:18:52Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.