Change:
return Promise.resolve(this.syncDelayer.trigger(() => this.syncWithGallery(), 0)); } <ins> private getAutoUpdateValue(): boolean | 'onlyEnabledExtensions' { const autoUpdate = this.configurationService.getValue<boolean | 'onlyEnabledExtensions'>(AutoUpdateConfigurationKey); return isBoolean(autoUpdate) || autoUpdate === 'onlyEnabledExtensions' ? autoUpdate : true; } </ins> private isAutoUpdateEnabled(): boolean { <del> return this.configurationService.getValue(AutoUpdateConfigurationKey); </del> <ins> return this.getAutoUpdateValue() !== false; </ins> } private isAutoCheckUpdatesEnabled(): boolean {

Discussion:
Today I noticed that VSCode updates and installs extensions even if they are disabled. In fact, I was reminded of a couple of extensions I no longer use by the hundreds of megabytes downloaded in the background. Could you consider adding this as a toggle in settings or disabling this behavior altogether?
I see your point. But what is the reason behind having such extension installed and disabled, instead of uninstalling it?
So that they don't update in the background and waste traffic on my metered connection ;) I switch between a lot of languages and runtimes regularly. I use VSCode for C++, C#, F#, PHP, Python, JS/Flow, Processing, GLSL/HLSL, Arduino and others, but I like to keep a "working set" of supporting extensions, depending on the project I'm working on. This comes down to the question "what does disabling extensions actually do", besides declutter the list? Initially I thought this would help with memory usage and startup time, but I don't believe that's really the case. If there's no practical use for disabling, maybe that option should be deprecated in favor of just uninstalling them.
Yes, Disabling helps you in creating a working set. But I see your point and agreed that not auto updating a disabled extension makes sense.
Know that disabled extension can also still popup a notification as well. I'm sure the C++ extension (ms-vscode.cpptools) occasionally (not sure when exactly) asks you to enter a survey even when the extension is disabled.
This should not happen. Please file a separate issue with steps to repro.
I will take a look at this one and follow up with a pull request.
I was wondering about the current status of this issue? If this issue still persists, I would love to contribute and try to resolve it. If this is the case, I would highly appreciate a code pointer to the update procedure, as I am fairly new to this project.
I have not had the chance to look into this. is this something that we still want to pursue?
It looks to me like you have already implemented the desired changes a few days ago?
This is not yet supported and contribution is very much appreciated. Code pointer: Auto update of extensions happen here
Thank you I will look into it. I would say, we just out the disabled extensions and do not return them.

Do you have something different / more elaborate in mind? And do you happen to know an easy way to test this function (i.e. forcing an auto-update)?
I was able to implement this feature and also a configuration to let users decide on whether disabled extensions should be updated. The PR can be found at .