---
TOCTitle: FAQ
ContentId: E02F97FD-842B-4D27-B461-37DD18B2582E
PageTitle: {% data variables.product.prodname_vscode %} Frequently Asked Questions
DateApproved: 02/04/2026
MetaDescription: Find answers to common questions about {% data variables.product.prodname_vscode %}, including accounts, AI features, licensing, and supported platforms.
---
# {% data variables.product.prodname_vscode %} FAQ

Our docs contain a **Common questions** section as needed for specific topics. We've captured items here that don't fit in the other topics.

If you don't see an answer to your question here, check our previously [reported issues on GitHub](https://github.com/microsoft/vscode/issues) and our [release notes](/updates).

## Can I use {% data variables.product.prodname_vscode_shortname %} without signing in?

Yes. You don't need an account to install {% data variables.product.prodname_vscode_shortname %} or use its core editor features.

Signing in with GitHub connects {% data variables.product.prodname_vscode_shortname %} to your GitHub Copilot plan and gives you access to the AI features, models, and usage allowances included with that plan. If you don't want to sign in, you can still use chat with a [bring-your-own-key model](/docs/agent-customization/language-models.md#bring-your-own-language-model-key) without a GitHub account or Copilot plan. Features that depend on the GitHub Copilot service, such as inline suggestions, semantic search, and embeddings, aren't available through bring-your-own-key models.

You can also use {% data variables.product.prodname_vscode_shortname %} without AI features. To hide the built-in AI features, see [Remove AI features from {% data variables.product.prodname_vscode_shortname %}](/docs/setup/copilot.md#remove-ai-features-from-vs-code).

## Open sourcing AI in {% data variables.product.prodname_vscode_shortname %}

We've open sourced the GitHub Copilot Chat extension under the MIT license and are bringing relevant components into {% data variables.product.prodname_vscode_shortname %} core. Read all details in our [announcement blog post](https://aka.ms/vscode-copilot-oss-blog) and [first milestone update](/blogs/2025/06/30/openSourceAIEditorFirstMilestone.md).

### Does this affect my current GitHub Copilot subscription? Is GitHub Copilot free now?

This change does not affect current GitHub Copilot subscriptions. To use GitHub Copilot, you'll continue to need both a GitHub account, and access to a GitHub Copilot subscription.

Individual developers who don't have access to Copilot through an organization or enterprise have access to the [GitHub Copilot free plan](https://aka.ms/github-docs-copilot-free) ([restrictions may apply](https://docs.github.com/en/site-policy/other-site-policies/github-and-trade-controls#github-copilot)). If that plan doesn't meet your needs, you can sign up for a Copilot paid plan or [bring your own model keys](/docs/agent-customization/language-models.md#bring-your-own-language-model-key).

### Will the GitHub Copilot backend services also be open sourced?

The GitHub Copilot services are not affected and will remain closed source.

### What is the timeline? When can I provide a contribution to the AI experience in {% data variables.product.prodname_vscode_shortname %}?

We have [completed the first step](https://code.visualstudio.com/blogs/2025/06/30/openSourceAIEditorFirstMilestone) of this process by open sourcing the GitHub Copilot Chat extension. The source code is available in the [microsoft/vscode-copilot-chat](https://github.com/microsoft/vscode-copilot-chat) repository.

In the coming months, we will bring the relevant components of the Copilot Chat extension into the core {% data variables.product.prodname_vscode_shortname %} repository. Check our [plan item](https://github.com/microsoft/vscode/issues/249031) for details and updates about the timeline.

Our goal is to make the experience for contributing to our AI features as simple as contributing to any part of {% data variables.product.prodname_vscode_shortname %}. As part of this, we want to make it possible to use the Copilot backend services for debugging and testing purposes when contributing.
Check the [CONTRIBUTING.md](https://github.com/microsoft/vscode-copilot-chat/blob/main/CONTRIBUTING.md) file for details on how to contribute.

### Why integrate GitHub Copilot into the core {% data variables.product.prodname_vscode_shortname %} repository?

In the time since GitHub Copilot was first released, it's become clear that AI-powered tools are core to how we write code. From usage telemetry, we can see that more users are actually using AI features in {% data variables.product.prodname_vscode_shortname %} than some other features like debugging or testing.

Making AI functionality a core part of {% data variables.product.prodname_vscode_shortname %} is a reaffirmation in our belief that working in the open leads to a better product for our users and fosters a diverse ecosystem of extensions.

### I'm an extension author. How am I affected?

We maintain backwards compatibility for stable APIs. You should not expect any impact on your extension.
We're continuously evolving and expanding the {% data variables.product.prodname_vscode_shortname %} extension APIs based on feedback from extension authors. If you need additional APIs to make your extension successful, we would love to hear from you – please file an API request in the [microsoft/vscode repo](https://github.com/microsoft/vscode/issues).

### I already use other AI coding extensions in {% data variables.product.prodname_vscode_shortname %} (Cline, Roo Code, ...). How does this affect me?

You can continue to use these extensions in {% data variables.product.prodname_vscode_shortname %}!
We love that the community is building extensions to make the developer experience in {% data variables.product.prodname_vscode_shortname %} better.
To improve the experience for other AI extensions, we're constantly adding APIs like the [Language Model](https://code.visualstudio.com/api/references/vscode-api#lm) API for directly calling language models from an extension, the [Tools](https://code.visualstudio.com/api/references/vscode-api#LanguageModelChatTool) API for interacting with language model tools and integrating with the built-in or your own agents, or the [Shell Execution](https://code.visualstudio.com/api/references/vscode-api#ShellExecution) API for running and interacting with terminal commands (particularly useful for agentic experiences). Going forward, we are planning to add even more APIs to meet the needs of extension authors.

### Will this change anything about how you collect data?

No, nothing is changing. By open sourcing GitHub Copilot Chat, we are making it fully transparent how we collect data and enable you to verify this in the source code. Learn more about [telemetry in {% data variables.product.prodname_vscode_shortname %}](/docs/configure/telemetry.md) and the [GitHub Copilot Trust Center](https://copilot.github.trust.page/).

### How will the {% data variables.product.prodname_vscode_shortname %} team prioritize between AI features and non-AI features in future releases?

We believe that AI-powered tools are core to how we write code. We invest in both AI features and improving the core editor experience. This is also reflected in a 50/50% split of the team working on AI versus other features.
Many of the non-AI features might not always be as visible to the user, such as performance, security, accessibility, Electron updates, and more.

### Will bringing AI features into the core {% data variables.product.prodname_vscode_shortname %} repository affect the (startup) performance of {% data variables.product.prodname_vscode_shortname %}?

Performance is our core priority and we are committed to maintaining the performance of {% data variables.product.prodname_vscode_shortname %} as we integrate AI features. In addition, if you don't enable AI functionality in {% data variables.product.prodname_vscode_shortname %}, no associated background processes will run that could affect performance.

### Can I disable AI functionality in {% data variables.product.prodname_vscode_shortname %}?

You can disable the built-in AI features in {% data variables.product.prodname_vscode_shortname %} with the `setting(chat.disableAIFeatures)` setting, similar to how you configure other features in {% data variables.product.prodname_vscode_shortname %}. This disables and hides features like chat or inline suggestions in {% data variables.product.prodname_vscode_shortname %} and disables the Copilot extensions. You can configure the setting at the workspace or user level.

Alternatively, use the **Learn How to Hide AI Features** action from the Chat menu in the title bar to access the setting.

> [!NOTE]
> If you have previously disabled the built-in AI features, your choice is respected upon updating to a new version of {% data variables.product.prodname_vscode_shortname %}.

### If I disable AI functionality in {% data variables.product.prodname_vscode_shortname %}, is my data still sent to Microsoft?

No, if you disable AI functionality in {% data variables.product.prodname_vscode_shortname %} or if you don't login to your Copilot subscription from {% data variables.product.prodname_vscode_shortname %}, your data is not sent to the Copilot backend services. Learn more about [telemetry in {% data variables.product.prodname_vscode_shortname %}](/docs/configure/telemetry.md) and the [GitHub Copilot Trust Center](https://copilot.github.trust.page/).

### Are the models that {% data variables.product.prodname_vscode_shortname %} uses in the Copilot extension open source (OSS)?

No. The models used by GitHub Copilot are licensed separately, and that does not change. In fact, most of those models are from third parties such as OpenAI, Anthropic and Google...

## What is the difference between {% data variables.product.prodname_vscode %} and Visual Studio IDE?

{% data variables.product.prodname_vscode %} is a streamlined code editor with support for development operations like debugging, task running, and version control. It aims to provide just the tools a developer needs for a quick code-build-debug cycle and leaves more complex workflows to fuller featured IDEs, such as [Visual Studio IDE](https://visualstudio.microsoft.com).

## Is {% data variables.product.prodname_vscode_shortname %} free?

Yes, {% data variables.product.prodname_vscode_shortname %} is free for private or commercial use. See the [product license](https://code.visualstudio.com/license) for details.

If you don't yet have a Copilot subscription, you can use Copilot for free by signing up for the [{% data variables.copilot.copilot_free_short %} plan](https://github.com/github-copilot/signup) and get a monthly allowance of inline suggestions and AI credits.

## Platform support

### Which OSs are supported?

{% data variables.product.prodname_vscode_shortname %} runs on macOS, Linux, and Windows. See the [Requirements documentation](requirements) for the supported versions. You can find more platform specific details in the [Setup overview](/docs/getstarted/overview.md).

### Can I run {% data variables.product.prodname_vscode_shortname %} on older Windows versions?

Microsoft ended support and is no longer providing security updates for [Windows 7](https://learn.microsoft.com/lifecycle/products/windows-7), [Windows 8, and Windows 8.1](https://learn.microsoft.com/en-us/lifecycle/announcements/windows-8-1-end-support-january-2023). {% data variables.product.prodname_vscode_shortname %} desktop versions starting with 1.71 (August 2022) no longer run on Windows 7 and starting with 1.80 (June 2023) will no longer run on Windows 8 and 8.1. You will need to upgrade to a newer Windows version to use later versions of {% data variables.product.prodname_vscode_shortname %}.

{% data variables.product.prodname_vscode_shortname %} will no longer provide product updates or security fixes on old Windows versions. {% data variables.product.prodname_vscode_shortname %} [version 1.70.3](https://code.visualstudio.com/updates/v1_70) is the last available release for Windows 7 users and version 1.79 will be the last available release for Windows 8 and 8.1 users. You can learn more about upgrading your Windows version at [support.microsoft.com](https://support.microsoft.com/windows/windows-7-support-ended-on-january-14-2020-b75d4580-2cc7-895a-2c9c-1466d9a53962).

Additionally, 32-bit OEM support has been dropped with Windows 10, version 2004. The last stable {% data variables.product.prodname_vscode_shortname %} version to support Windows 32-bit is 1.83 (September 2023). You will need to update to the 64-bit release.

### Can I run {% data variables.product.prodname_vscode_shortname %} on old macOS versions?

{% data variables.product.prodname_vscode_shortname %} desktop version starting with 1.105 (September 2025) is deprecating support for macOS Big Sur (version 11.0 and older). Starting with {% data variables.product.prodname_vscode_shortname %} 1.107 (November 2025), we will stop updating {% data variables.product.prodname_vscode_shortname %} on macOS Big Sur (version 11.0 and older). You will need to upgrade to a newer macOS version to use later versions of {% data variables.product.prodname_vscode_shortname %}.

{% data variables.product.prodname_vscode_shortname %} will no longer provide product updates or security fixes on macOS Big Sur (versions 11.0 and older) and {% data variables.product.prodname_vscode_shortname %} version 1.106 will be the last available release for macOS Big Sur (11.0 and older). You can learn more about upgrading your macOS version at [support.apple.com](https://support.apple.com/en-us/HT201260).

### Can I run {% data variables.product.prodname_vscode_shortname %} on older Linux distributions?

Starting with {% data variables.product.prodname_vscode_shortname %} release 1.86.1 (January 2024), {% data variables.product.prodname_vscode_shortname %} desktop is only compatible with Linux distributions based on glibc 2.28 or later, for example, Debian 10, RHEL 8, or Ubuntu 20.04.

If you are unable to upgrade your Linux distribution, the recommended alternative is to use our [web client](/docs/remote/vscode-web.md). If you would like to use the desktop version, then you can download the {% data variables.product.prodname_vscode_shortname %} release 1.85 from [here](https://code.visualstudio.com/updates/v1_85). Depending on your platform, make sure to disable updates to stay on that version. A good recommendation is to set up the installation with [Portable Mode](/docs/setup/portable.md).

### Can I run a portable version of {% data variables.product.prodname_vscode_shortname %}?

Yes, {% data variables.product.prodname_vscode_shortname %} has a [Portable Mode](/docs/setup/portable.md) that lets you keep settings and data in the same location as your installation, for example, on a USB drive.


## Telemetry and crash reporting

### How to disable telemetry reporting

{% data variables.product.prodname_vscode_shortname %} collects usage data and sends it to Microsoft to help improve our products and services. Read our [privacy statement](https://go.microsoft.com/fwlink/?LinkID=528096&clcid=0x409) and [telemetry documentation](/docs/configure/telemetry.md) to learn more.

If you don't want to send usage data to Microsoft, you can set the `setting(telemetry.telemetryLevel)` user [setting](/docs/configure/settings.md) to `off`.

From **File** > **Preferences** > **Settings**, search for `telemetry`, and set the **Telemetry: Telemetry Level** setting to `off`. This will silence all telemetry events from {% data variables.product.prodname_vscode_shortname %} going forward.

> **Important Notice**: {% data variables.product.prodname_vscode_shortname %} gives you the option to install Microsoft and third party extensions. These extensions may be collecting their own usage data and are not controlled by the `setting(telemetry.telemetryLevel)` setting. Consult the specific extension's documentation to learn about its telemetry reporting.

#### How to disable experiments

{% data variables.product.prodname_vscode_shortname %} uses experiments to try out new features or progressively roll them out. Our experimentation framework calls out to a Microsoft-owned service and is therefore disabled when telemetry is disabled. However, if you want to disable experiments regardless of your telemetry preferences, you may set the `setting(workbench.enableExperiments)` user [setting](/docs/configure/settings.md) to `false`.

From **File** > **Preferences** > **Settings**, search for `experiments`, and uncheck the **Workbench: Enable Experiments** setting. This will prevent {% data variables.product.prodname_vscode_shortname %} from calling out to the service and opt out of any ongoing experiments.

### How to disable crash reporting

{% data variables.product.prodname_vscode_shortname %} collects data about any crashes that occur and sends it to Microsoft to help improve our products and services. Read our [privacy statement](https://go.microsoft.com/fwlink/?LinkID=528096&clcid=0x409) and [telemetry documentation](/docs/configure/telemetry.md) to learn more.

If you don't want to send crash data to Microsoft, you can change the `setting(telemetry.telemetryLevel)` user [setting](/docs/configure/settings.md) to `off`.

From **File** > **Preferences** > **Settings**, search for `telemetry`, and set the **Telemetry: Telemetry Level** setting to `off`. This will silence all telemetry events including crash reporting from {% data variables.product.prodname_vscode_shortname %}. You will need to restart {% data variables.product.prodname_vscode_shortname %} for the setting change to take effect.

## GDPR and {% data variables.product.prodname_vscode_shortname %}

Now that the General Data Protection Regulation (GDPR) is in effect, we want to take this opportunity to reiterate that we take privacy very seriously. That's both for Microsoft as a company and specifically within the {% data variables.product.prodname_vscode_shortname %} team.

To support GDPR:

* The {% data variables.product.prodname_vscode_shortname %} product notifies all users that they can opt out of telemetry collection.
* The team actively reviews and classifies all telemetry sent (documented in [our OSS codebase](https://github.com/microsoft/vscode/pull/34997)).
* There are valid data retention policies in place for any data collected, for example crash dumps.

You can learn more about {% data variables.product.prodname_vscode_shortname %}'s GDPR compliance in the [telemetry documentation](/docs/configure/telemetry.md).

## What online services does {% data variables.product.prodname_vscode_shortname %} use?

Beyond crash reporting and telemetry, {% data variables.product.prodname_vscode_shortname %} uses online services for various other purposes such as downloading product updates, finding, installing, and updating extensions, or providing Natural Language Search within the Settings editor. You can learn more in [Managing online services](/docs/configure/telemetry.md#managing-online-services).

You can choose to turn on/off features that use these services. From **File** > **Preferences** > **Settings**, and type the tag `@tag:usesOnlineServices`. This will display all settings that control the usage of online services and you can individually switch them on or off.

## Licensing

### Location

You can find the {% data variables.product.prodname_vscode_shortname %} licenses, third party notices and [Chromium](https://www.chromium.org) Open Source credit list under your {% data variables.product.prodname_vscode_shortname %} installation location `resources\app` folder. {% data variables.product.prodname_vscode_shortname %}'s `ThirdPartyNotices.txt`, Chromium's `Credits_*.html`, and {% data variables.product.prodname_vscode_shortname %}'s English language `LICENSE.txt` are available under `resources\app`. Localized versions of `LICENSE.txt` by language ID are under `resources\app\licenses`.

### Why does {% data variables.product.prodname_vscode %} have a different license than the vscode GitHub repository?

To learn why {% data variables.product.prodname_vscode %}, the product, has a different license than the open-source [vscode GitHub repository](https://github.com/microsoft/vscode), see [issue #60](https://github.com/microsoft/vscode/issues/60#issuecomment-161792005) for a detailed explanation.

### What is the difference between the `vscode` repository and the Microsoft {% data variables.product.prodname_vscode %} distribution?

The [github.com/microsoft/vscode](https://github.com/microsoft/vscode) repository (`Code - OSS`) is where we develop the {% data variables.product.prodname_vscode %} product. Not only do we write code and work on issues there, we also publish our roadmap and iteration and endgame plans. The source code is available to everyone under a standard [MIT license](https://github.com/microsoft/vscode/blob/main/LICENSE.txt).

{% data variables.product.prodname_vscode %} is a distribution of the `Code - OSS` repository with Microsoft specific customizations (including source code), released under a traditional [Microsoft product license](https://code.visualstudio.com/License/).

See the [{% data variables.product.prodname_vscode %} and 'Code - OSS' Differences](https://github.com/microsoft/vscode/wiki/Differences-between-the-repository-and-Visual-Studio-Code) article for more details.

### What does "Built on Open Source" mean?

[Microsoft {% data variables.product.prodname_vscode %}](https://code.visualstudio.com) is a [Microsoft licensed](https://code.visualstudio.com/License/) distribution of ['Code - OSS'](https://github.com/microsoft/vscode) that includes Microsoft proprietary assets (such as icons) and features (Visual Studio Marketplace integration, small aspects of enabling Remote Development). While these additions make up a very small percentage of the overall distribution code base, it is more accurate to say that {% data variables.product.prodname_vscode %} is "built" on open source, rather than "is" open source, because of these differences. More information on what each distribution includes can be found in the [{% data variables.product.prodname_vscode %} and 'Code - OSS' Differences](https://github.com/microsoft/vscode/wiki/Differences-between-the-repository-and-Visual-Studio-Code) article.

## Extensions

### Are all {% data variables.product.prodname_vscode_shortname %} extensions open source?

Extension authors are free to choose a license that fits their business needs. While many extension authors have opted to release their source code under an open-source license, some extensions like [Wallaby.js](https://marketplace.visualstudio.com/items?itemName=WallabyJs.wallaby-vscode), [Google Cloud Code](https://marketplace.visualstudio.com/items?itemName=GoogleCloudTools.cloudcode), and the [{% data variables.product.prodname_vscode_shortname %} Remote Development extensions](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack) use proprietary licenses.

At Microsoft, we have a mix of open and closed source extensions. Reliance on existing proprietary source code or libraries, source code that crosses into Microsoft licensed tools or services (e.g., the C# DevKit extension uses the Visual Studio subscription license model, see [License](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csdevkit)), and business model differences across the entirety of Microsoft may result in extensions choosing a proprietary license. You can find a list of Microsoft contributed {% data variables.product.prodname_vscode %} extensions and their source code licenses in the [Microsoft Extension Licenses](/docs/supporting/oss-extensions.md) article.

### How do I find the license for an extension?

Most extensions will have a link to their license on the Marketplace page (their "Read Me" document), found on the right column under **Resources**. If you don't find a link, you may find the license in the extension's repository if it is public, or you can contact the extension author through the Q & A section of the Marketplace.

### Can I use a Microsoft extension outside of {% data variables.product.prodname_vscode_shortname %}?

No. While the source code for an extension from Microsoft may be open source, we do not license extensions from Microsoft or its affiliates that are published to and acquired from the Visual Studio Marketplace for use outside of the Visual Studio family of products: Microsoft Visual Studio, {% data variables.product.prodname_vscode %}, GitHub Codespaces, Azure DevOps, Azure DevOps Server, and successor products and services offered by us and Microsoft affiliates, such as GitHub, Inc. We build, test, deploy, and support these extensions and services only in the Visual Studio family of products, to ensure they meet our security and quality standards. We do not do this for extensions elsewhere, including those built on a fork of the [Code - OSS Repository](https://github.com/microsoft/vscode). Please see _Conditions: Use Rights for Marketplace/NuGet Offerings_ in the Visual Studio Marketplace [Terms of Service](https://aka.ms/vsmarketplace-ToU) for more information.


### I can't access the Visual Studio Marketplace from product << fill in the blank >>, why not?

We provide the Visual Studio Marketplace for use only by the Visual Studio family of products: Microsoft Visual Studio, {% data variables.product.prodname_vscode %}, GitHub Codespaces, Azure DevOps, Azure DevOps Server, and successor products and services offered by us and Microsoft affiliates, such as GitHub, Inc. Therefore, alternative products including those built on a fork of the [Code - OSS Repository](https://github.com/microsoft/vscode), are not permitted to access the Visual Studio Marketplace. We do this to protect the security and quality of the ecosystem, including the following measures:

* Extensions run in the context and with the permissions of the product, and they might contain executable code. The [Marketplace vets every extension](/docs/configure/extensions/extension-runtime-security.md#marketplace-protections) for security and to prevent them from performing malicious activity. When you install an extension with a product in the Visual Studio family, you know that it has been vetted to run in that context.

* When a malicious extension is reported and verified, or a vulnerability is found in an extension dependency, the extension is removed from the Marketplace, added to a block list, and automatically uninstalled by {% data variables.product.prodname_vscode_shortname %}.

* Microsoft spends considerable resources in running, maintaining, and securing this global online service. Products in the Visual Studio family are designed to access the Marketplace in a secure and reliable manner, so that the Marketplace is available when you need it.

* Extensions might integrate deeply with the product. The Marketplace ensures that we maintain API compatibility and that extensions use the product's extensions APIs correctly. This helps ensure that extensions you install work correctly across version updates.

See [#31168](https://github.com/microsoft/vscode/issues/31168#issuecomment-2810912914) for additional details on this topic.

### Why should I install extensions from the Visual Studio Marketplace?

Installing extensions from the Visual Studio Marketplace has many advantages over installing them from other sources.

* The Visual Studio Marketplace employs [several mechanisms](/docs/configure/extensions/extension-runtime-security.md#marketplace-protections) to protect you from installing malicious extensions, including malware scanning, dynamic detection, publisher verification, and more. When you install extensions from a different source, there is no guarantee that the extension is safe to run in your context.

* When a malicious extension is reported and verified, or a vulnerability is found in an extension dependency, the extension is removed from the Marketplace, added to a *block list*, and automatically uninstalled by {% data variables.product.prodname_vscode_shortname %}.

* The Marketplace enables you to easily find, install, and update extensions. When an update is available, for example because of a security fix, {% data variables.product.prodname_vscode_shortname %} automatically installs the updated version.

* Extensions might integrate deeply with the product. The Marketplace ensures that we maintain API compatibility and that extensions use the product's extensions APIs correctly. This helps ensure that extensions you install work correctly across version updates.

### Report an issue with a {% data variables.product.prodname_vscode_shortname %} extension

For bugs, feature requests or to contact an extension author, you should use the links available in the [{% data variables.product.prodname_vscode %} Marketplace](https://marketplace.visualstudio.com/vscode) or use **Help: Report Issue** from the Command Palette. However, if there is an issue where an extension does not follow our code of conduct, for example it includes profanity, pornography or presents a risk to the user, then we have [an email alias to report the issue](mailto:VSMarketplace@microsoft.com). Once the mail is received, our Marketplace team will look into an appropriate course of action, up to and including unpublishing the extension.

## {% data variables.product.prodname_vscode_shortname %} versions

### How do I find my current {% data variables.product.prodname_vscode_shortname %} version?

You can find the {% data variables.product.prodname_vscode_shortname %} version information in the About dialog box.

On macOS, go to **Code** > **About {% data variables.product.prodname_vscode %}**.

On Windows and Linux, go to **Help** > **About**.

The {% data variables.product.prodname_vscode_shortname %} version is the first **Version** number listed and has the version format 'major.minor.release', for example '1.100.0'.

### Previous release versions

You can find links to some release downloads at the top of a version's release notes:

![Download links in release notes](images/faq/links-release-notes.png)

If you need a type of installation not listed there, you can manually download via the following URLs:

Download type | URL
--- | ---
Windows x64 System installer | https://update.code.visualstudio.com/{version}/win32-x64/stable
Windows x64 User installer| https://update.code.visualstudio.com/{version}/win32-x64-user/stable
Windows x64 zip | https://update.code.visualstudio.com/{version}/win32-x64-archive/stable
Windows x64 CLI | https://update.code.visualstudio.com/{version}/cli-win32-x64/stable
Windows Arm64 System installer | https://update.code.visualstudio.com/{version}/win32-arm64/stable
Windows Arm64 User installer | https://update.code.visualstudio.com/{version}/win32-arm64-user/stable
Windows Arm64 zip | https://update.code.visualstudio.com/{version}/win32-arm64-archive/stable
Windows Arm64 CLI | https://update.code.visualstudio.com/{version}/cli-win32-arm64/stable
macOS Universal | https://update.code.visualstudio.com/{version}/darwin-universal/stable
macOS Intel chip | https://update.code.visualstudio.com/{version}/darwin/stable
macOS Intel chip CLI | https://update.code.visualstudio.com/{version}/cli-darwin-x64/stable
macOS Apple silicon | https://update.code.visualstudio.com/{version}/darwin-arm64/stable
macOS Apple silicon CLI | https://update.code.visualstudio.com/{version}/cli-darwin-arm64/stable
Linux x64 | https://update.code.visualstudio.com/{version}/linux-x64/stable
Linux x64 debian | https://update.code.visualstudio.com/{version}/linux-deb-x64/stable
Linux x64 rpm | https://update.code.visualstudio.com/{version}/linux-rpm-x64/stable
Linux x64 snap | https://update.code.visualstudio.com/{version}/linux-snap-x64/stable
Linux x64 CLI | https://update.code.visualstudio.com/{version}/cli-linux-x64/stable
Linux Arm32 | https://update.code.visualstudio.com/{version}/linux-armhf/stable
Linux Arm32 debian | https://update.code.visualstudio.com/{version}/linux-deb-armhf/stable
Linux Arm32 rpm | https://update.code.visualstudio.com/{version}/linux-rpm-armhf/stable
Linux Arm32 CLI | https://update.code.visualstudio.com/{version}/cli-linux-armhf/stable
Linux Arm64  | https://update.code.visualstudio.com/{version}/linux-arm64/stable
Linux Arm64 debian | https://update.code.visualstudio.com/{version}/linux-deb-arm64/stable
Linux Arm64 rpm | https://update.code.visualstudio.com/{version}/linux-rpm-arm64/stable
Linux Arm64 CLI | https://update.code.visualstudio.com/{version}/cli-linux-arm64/stable

Substitute the specific release you want in the `{version}` placeholder. For example, to download the Linux Arm64 debian version for 1.83.1, you would use

```bash
https://update.code.visualstudio.com/1.83.1/linux-deb-arm64/stable
```

You can use the version string `latest`, if you'd like to always download the latest {% data variables.product.prodname_vscode_shortname %} stable version.

#### Windows 32-bit versions

Windows x86 32-bit versions are no longer actively supported after release 1.83 and could pose a security risk.

Download type | URL
--- | ---
Windows x86 System installer | https://update.code.visualstudio.com/{version}/win32/stable
Windows x86 User installer | https://update.code.visualstudio.com/{version}/win32-user/stable
Windows x86 zip | https://update.code.visualstudio.com/{version}/win32-archive/stable
Windows x86 CLI | https://update.code.visualstudio.com/{version}/cli-win32-ia32/stable

### Prerelease versions

Want an early peek at new {% data variables.product.prodname_vscode_shortname %} features?  You can try prerelease versions of {% data variables.product.prodname_vscode_shortname %} by installing the "Insiders" build.  The Insiders build installs side by side to your stable {% data variables.product.prodname_vscode_shortname %} install and has isolated settings, configurations, and extensions.  The Insiders build is updated nightly so you'll get the latest bug fixes and feature updates from the day before.

To install the Insiders build, go to the [Insiders download page](/insiders).

### How do I opt out of {% data variables.product.prodname_vscode_shortname %} auto-updates?

By default, {% data variables.product.prodname_vscode_shortname %} is set up to auto-update for macOS and Windows users when we release new updates. If you do not want to get automatic updates, configure the **Update: Mode** setting (`setting(update.mode)`) from `default` to `none`.

To modify the update mode, go to **File** > **Preferences** > **Settings**, search for `update mode` and change the setting to `none`.

If you use the JSON editor for your settings, add the following line:

```json
{
    "update.mode": "none"
}
```

You can install a previous release of {% data variables.product.prodname_vscode_shortname %} by uninstalling your current version and then installing the download provided at the top of a specific [release notes](/updates) page.

> [!NOTE]
> On Linux: If the {% data variables.product.prodname_vscode_shortname %} repository was installed correctly then your system package manager should handle auto-updating in the same way as other packages on the system. See [Installing {% data variables.product.prodname_vscode_shortname %} on Linux](/docs/setup/linux.md).

#### Opt out of extension updates

By default, {% data variables.product.prodname_vscode_shortname %} automatically updates extensions as new versions become available. If you do not want extensions to automatically update, you can set the **Extensions: Auto Update** setting (`setting(extensions.autoUpdate)`) to `off` in the Settings editor (`kb(workbench.action.openSettings)`).

If you use the JSON editor to modify your settings, add the following line:

```json
{
    "extensions.autoUpdate": "off"
}
```

## Where can I find the {% data variables.product.prodname_vscode %} icons?

**Are there guidelines for using the icons and names?**

You can download the official {% data variables.product.prodname_vscode %} icons and read the usage guidelines at [Icons and names usage guidelines](/brand).

## What is a {% data variables.product.prodname_vscode_shortname %} "workspace"?

A {% data variables.product.prodname_vscode_shortname %} "workspace" is usually just your project root folder. {% data variables.product.prodname_vscode_shortname %} uses the "workspace" concept in order to scope project configurations such as project-specific [settings](/docs/configure/settings.md) as well as config files for [debugging](/docs/debugtest/debugging.md) and [tasks](/docs/debugtest/tasks.md). Workspace files are stored at the project root in a `.vscode` folder. You can also have more than one root folder in a {% data variables.product.prodname_vscode_shortname %} workspace through a feature called [Multi-root workspaces](/docs/editing/workspaces/multi-root-workspaces.md).

You can learn more in the [What is a {% data variables.product.prodname_vscode_shortname %} "workspace"?](/docs/editing/workspaces/workspaces.md) article.

## Problems and issues

### Installation appears to be corrupt [Unsupported]

{% data variables.product.prodname_vscode_shortname %} does a background check to detect if the installation has been changed on disk and if so, you will see the text **[Unsupported]** in the title bar. This is done since some extensions directly modify (patch) the {% data variables.product.prodname_vscode_shortname %} product in such a way that is semi-permanent (until the next update) and this can cause hard to reproduce issues. We are not trying to block {% data variables.product.prodname_vscode_shortname %} patching, but we want to raise awareness that patching {% data variables.product.prodname_vscode_shortname %} means you are running an unsupported version. [Reinstalling {% data variables.product.prodname_vscode_shortname %}](/download) will replace the modified files and silence the warning.

You may also see the **[Unsupported]** message if {% data variables.product.prodname_vscode_shortname %} files have been mistakenly quarantined or removed by anti-virus software (see issue [#94858](https://github.com/microsoft/vscode/issues/94858) for an example). Check your anti-virus software settings and reinstall {% data variables.product.prodname_vscode_shortname %} to repair the missing files.

### Resolving shell environment fails

When {% data variables.product.prodname_vscode_shortname %} is launched from a terminal (for example, via `code .`), it has access to environment settings defined in your `.bashrc` or `.zshrc` files. This means features like tasks or debug targets also have access to those settings.

However, when launching from your platform's user interface (for example, the {% data variables.product.prodname_vscode_shortname %} icon in the macOS dock), you normally are not running in the context of a shell and you don't have access to those environment settings. This means that depending on how you launch {% data variables.product.prodname_vscode_shortname %}, you may not have the same environment.

To work around this, when launched via a UI gesture, {% data variables.product.prodname_vscode_shortname %} will start a small process to run (or "resolve") the shell environment defined in your `.bashrc`, `.zshrc`, or PowerShell profile files. If, after a configurable timeout (via `application.shellEnvironmentResolutionTimeout`, defaults to 10 seconds), the shell environment has still not been resolved or resolving failed for any other reason, {% data variables.product.prodname_vscode_shortname %} will abort the "resolve" process, launch without your shell's environment settings, and you will see an error like the following:

![Shell environment startup error](images/faq/shell-env-error.png)

If the error message indicates that resolving your shell environment took too long, the [steps below](#investigate-slow-shell-initialization) can help you investigate what might be causing slowness. You can also increase the timeout by configuring the `application.shellEnvironmentResolutionTimeout` setting. But keep in mind that increasing this value means you will have to wait longer to use some of the features in {% data variables.product.prodname_vscode_shortname %}, such as extensions.

If you see other errors, please create an [issue](https://github.com/microsoft/vscode/issues) to get help.

#### Investigate slow shell initialization

The process outlined below may help you identify which parts of your shell initialization are taking the most time:

* Open your shell's startup file (for example, in {% data variables.product.prodname_vscode_shortname %} by typing `~/.bashrc` or `~/.zshrc` in Quick Open (`kb(workbench.action.quickOpen)`)).
* Selectively comment out potentially long running operations (such as `nvm` if you find that).
* Save and fully restart {% data variables.product.prodname_vscode_shortname %}.
* Continue commenting out operations until the error disappears.

>**Note**: While `nvm` is a powerful and useful Node.js package manager, it can cause slow shell startup times, if being run during shell initialization. You might consider package manager alternatives such as [asdf](https://asdf-vm.com) or search on the internet for `nvm` performance suggestions.

#### Launch {% data variables.product.prodname_vscode_shortname %} from a terminal

If modifying your shell environment isn't practical, you can avoid {% data variables.product.prodname_vscode_shortname %}'s resolving shell environment phase by launching {% data variables.product.prodname_vscode_shortname %} directly from a fully initialized terminal.

* Typing `code` from an open terminal will launch {% data variables.product.prodname_vscode_shortname %} with your last workspace.
* Typing `code .` will launch {% data variables.product.prodname_vscode_shortname %} open to the current folder.

### {% data variables.product.prodname_vscode_shortname %} is blank?

The Electron shell used by {% data variables.product.prodname_vscode %} has trouble with some GPU (graphics processing unit) hardware acceleration. If {% data variables.product.prodname_vscode_shortname %} is displaying a blank (empty) main window, you can try disabling GPU acceleration when launching {% data variables.product.prodname_vscode_shortname %} by adding the Electron `--disable-gpu` command-line switch.

```bash
code --disable-gpu
```

If this happened after an update, deleting the `GPUCache` directory can resolve the issue.

```bash
rm -r ~/.config/Code/GPUCache
```

### {% data variables.product.prodname_vscode_shortname %} gets unresponsive right after opening a folder

When you open a folder, {% data variables.product.prodname_vscode_shortname %} will search for typical project files to offer you additional tooling (for example, the solution picker in the Status bar to open a solution). If you open a folder with lots of files, the search can take a large amount of time and CPU resources during which {% data variables.product.prodname_vscode_shortname %} might be slow to respond. We plan to improve this in the future but for now you can exclude folders from the explorer via the `setting(files.exclude)` setting and they will not be searched for project files:

```json
    "files.exclude": {
        "**/largeFolder": true
    }
```

## Technical support channels

You can ask questions and search for answers on [Stack Overflow](https://stackoverflow.com/questions/tagged/vscode) and enter issues and feature requests directly in our [GitHub repository](https://github.com/microsoft/vscode/issues).

If you'd like to contact a professional support engineer, you can open a ticket with the [Microsoft assisted support team](https://support.microsoft.com/oas/default.aspx?prid=16064).