Vs_setup Msi Download

-->

Welcome to Visual Studio 2019! In this version, it's easy to choose and install just the features you need. And because of its reduced minimum footprint, it installs quickly and with less system impact.

Welcome to a new way to install Visual Studio! In this version, we've made it easier for you to choose and install just the features you need. We've also reduced the minimum footprint of Visual Studio so that it installs more quickly and with less system impact than ever before.

IF YOU COMPLY WITH THESE LICENSE TERMS, YOU HAVE THE RIGHTS BELOW. INSTALLATION AND USE RIGHTS. Installation and Use. You and your organization may use copies of the Visual Studio Isolated or Integrated Shells (the “software” or “the Shell”) with Visual Studio 2008, Visual Studio 2010, Visual Studio 2012, Visual Studio 2013, or Visual Studio 2015 to develop and test your. Download Vssetup.msi For Visual Studio 2010. This differs from the 2008 Express Editions, which did not ask for any key or activation if installed from the ISO. A more extreme case of that is PDF-XChange Viewer - which has zipped installers and exe installers (so if.exes are blocked you can download the.zip) two different msi installers and a portable zip. I'd default to.exe or.msi if I want an installer unless it's blocked since I KNOW its an installer. I ran WCU bootstrap.msi and WCU SOAP3 soapsdk.msi and installations were succesfull. Next I ran setup.exe again with step 2 (Visual Foxpro) and stoped again with message: The Windows Installer package.

Note

I have copied entire vcexpress/ folder tree to a local drive (first failed attempt was to use a mounted iso image, downloaded directly from M$ ) then I copied vcexpress/vssetup.ms (with underscore sign) to vcexpress/vssetup.msi (without underscore, type msi instead of ms ).

This topic applies to Visual Studio on Windows. For Visual Studio for Mac, see Install Visual Studio for Mac.

Want to know more about what else is new in this version? See our release notes.

Want to know more about what else is new in this version? See our release notes.

Ready to install? We'll walk you through it, step-by-step.

Step 1 - Make sure your computer is ready for Visual Studio

Before you begin installing Visual Studio:

  1. Check the system requirements. These requirements help you know whether your computer supports Visual Studio 2017.

  2. Apply the latest Windows updates. These updates ensure that your computer has both the latest security updates and the required system components for Visual Studio.

  3. Reboot. The reboot ensures that any pending installs or updates don't hinder the Visual Studio install.

  4. Free up space. Remove unneeded files and applications from your %SystemDrive% by, for example, running the Disk Cleanup app.

  1. Check the system requirements. These requirements help you know whether your computer supports Visual Studio 2019.

  2. Apply the latest Windows updates. These updates ensure that your computer has both the latest security updates and the required system components for Visual Studio.

  3. Reboot. The reboot ensures that any pending installs or updates don't hinder the Visual Studio install.

  4. Free up space. Remove unneeded files and applications from your %SystemDrive% by, for example, running the Disk Cleanup app.

For questions about running previous versions of Visual Studio side by side with Visual Studio 2017, see the Visual Studio compatibility details.

For questions about running previous versions of Visual Studio side by side with Visual Studio 2019, see the Visual Studio 2019 Platform Targeting and Compatibility page.

Step 2 - Download Visual Studio

Next, download the Visual Studio bootstrapper file.

To get a bootstrapper for Visual Studio 2017, see the Visual Studio previous versions download page for details on how to do so.

To do so, choose the following button, choose the edition of Visual Studio that you want, choose Save, and then choose Open folder.

Step 3 - Install the Visual Studio installer

Run the bootstrapper file to install the Visual Studio Installer. This new lightweight installer includes everything you need to both install and customize Visual Studio.

  1. From your Downloads folder, double-click the bootstrapper that matches or is similar to one of the following files:

    • vs_community.exe for Visual Studio Community
    • vs_professional.exe for Visual Studio Professional
    • vs_enterprise.exe for Visual Studio Enterprise

    If you receive a User Account Control notice, choose Yes.

  2. We'll ask you to acknowledge the Microsoft License Terms and the Microsoft Privacy Statement. Choose Continue.

Step 4 - Choose workloads

After the installer is installed, you can use it to customize your installation by selecting the feature sets—or workloads—that you want. Here's how.

  1. Find the workload you want in the Visual Studio Installer.

    For example, choose the '.NET desktop development' workload. It comes with the default core editor, which includes basic code editing support for over 20 languages, the ability to open and edit code from any folder without requiring a project, and integrated source code control.

  2. After you choose the workload(s) you want, choose Install.

    Next, status screens appear that show the progress of your Visual Studio installation.

  1. Find the workload you want in the Visual Studio Installer.

    For example, choose the 'ASP.NET and web development' workload. It comes with the default core editor, which includes basic code editing support for over 20 languages, the ability to open and edit code from any folder without requiring a project, and integrated source code control.

  2. After you choose the workload(s) you want, choose Install.

    Next, status screens appear that show the progress of your Visual Studio installation.

Tip

At any time after installation, you can install workloads or components that you didn't install initially. If you have Visual Studio open, go to Tools > Get Tools and Features... which opens the Visual Studio Installer. Or, open Visual Studio Installer from the Start menu. From there, you can choose the workloads or components that you wish to install. Then, choose Modify.

Step 5 - Choose individual components (Optional)

If you don't want to use the Workloads feature to customize your Visual Studio installation, or you want to add more components than a workload installs, you can do so by installing or adding individual components from the Individual components tab. Choose what you want, and then follow the prompts.

Step 6 - Install language packs (Optional)

By default, the installer program tries to match the language of the operating system when it runs for the first time. To install Visual Studio in a language of your choosing, choose the Language packs tab from the Visual Studio Installer, and then follow the prompts.

Change the installer language from the command line

Another way that you can change the default language is by running the installer from the command line. For example, you can force the installer to run in English by using the following command: vs_installer.exe --locale en-US. The installer will remember this setting when it is run the next time. The installer supports the following language tokens: zh-cn, zh-tw, cs-cz, en-us, es-es, fr-fr, de-de, it-it, ja-jp, ko-kr, pl-pl, pt-br, ru-ru, and tr-tr.

Step 7 - Select the installation location (Optional)

New in 15.7: You can now reduce the installation footprint of Visual Studio on your system drive. You can choose to move the download cache, shared components, SDKs, and tools to different drives, and keep Visual Studio on the drive that runs it the fastest.

You can reduce the installation footprint of Visual Studio on your system drive. You can choose to move the download cache, shared components, SDKs, and tools to different drives, and keep Visual Studio on the drive that runs it the fastest.

Important

You can select a different drive only when you first install Visual Studio. If you've already installed it and want to change drives, you must uninstall Visual Studio and then reinstall it.

For more information, see the Select installation locations page.

Step 8 - Start developing

  1. After Visual Studio installation is complete, choose the Launch button to get started developing with Visual Studio.

  2. Choose File, and then choose New Project.

  3. Select a project type.

    For example, to build a C++ app, choose Installed, expand Visual C++, and then choose the C++ project type that you want to build.

    To build a C# app, choose Installed, expand Visual C#, and then choose the C# project type that you want to build.

  1. After Visual Studio installation is complete, choose the Launch button to get started developing with Visual Studio.

  2. On the start window, choose Create a new project.

  3. In the search box, enter the type of app you want to create to see a list of available templates. The list of templates depends on the workload(s) that you chose during installation. To see different templates, choose different workloads.

    You can also filter your search for a specific programming language by using the Language drop-down list. You can filter by using the Platform list and the Project type list, too.

  4. Visual Studio opens your new project, and you're ready to code!

Get support

Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.

Vs_setup Msi Download

We also offer an installation chat (English only) support option for installation-related issues.

Here are a few more support options:

  • Report product issues to us via the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
  • Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.
  • Use your GitHub account to talk to us and other Visual Studio developers in the Visual Studio conversation in the Gitter community.

See also

Vs_setup Msi Download Windows 10

-->

When you install Visual Studio from a command prompt, you can use a variety of command-line parameters to control or customize the installation. From the command line, you can perform the following actions:

  • Start the install with certain options preselected.
  • Automate the installation process.
  • Create a cache (layout) of the installation files for later use.

The command-line options are used in conjunction with the setup bootstrapper, which is the small (1 MB) file that initiates the download process. The bootstrapper is the first executable that is launched when you download from the Visual Studio site.

To get a bootstrapper for Visual Studio 2017, see the Visual Studio previous versions download page for details on how to do so.

Use the following links to get a direct link to the latest release bootstrapper for the product edition that you're installing:

Your bootstrapper file should match or be similar to one of the following file names:

  • vs_enterprise.exe
  • vs_professional.exe
  • vs_community.exe
Vs_setup Msi Download

Tip

If you previously downloaded a bootstrapper file and want to verify its version, here's how. In Windows, open File Explorer, right-click the bootstrapper file, choose Properties, choose the Details tab, and then view the Product version number. To match that number to a release of Visual Studio, see the Visual Studio build numbers and release dates page.

Command-line parameters

Visual Studio command-line parameters are case-insensitive.

Syntax: vs_enterprise.exe [command] <options>...

Vs_setup Msi Download

Replace vs_enterprise.exe as appropriate for the product edition you're installing. (Alternatively, you can use vs_installer.exe.)

Tip

For more examples of how to use the command line to install Visual Studio, see the Command-line parameter examples page.

CommandDescription
(blank)Installs the product.
modifyModifies an installed product.
updateUpdates an installed product.
repairRepairs an installed product.
uninstallUninstalls an installed product.
exportNew in version 15.9: Exports installation selection to an installation configuration file. Note: Can only be used with vs_installer.exe.
CommandDescription
(blank)Installs the product.
modifyModifies an installed product.
updateUpdates an installed product.
repairRepairs an installed product.
uninstallUninstalls an installed product.
exportExports installation selection to an installation configuration file. Note: Can only be used with vs_installer.exe.

Install options

Vs_setup.msi Download 2010

Install optionDescription
--installPath <dir>The installation directory for the instance to act upon. For the install command, this is Optional and is where the instance will be installed. For other commands, this is Required and is where the previously installed instance was installed.
--addProductLang <language-locale>Optional: During an install or modify operation, this determines the UI language packs that are installed to the product. It can appear multiple times on the command line to add multiple language packs. If not present, the installation uses the machine locale. For more information, see the List of language locales section on this page.
--removeProductLang <language-locale>Optional: During an install or modify operation, this determines the UI language packs that are to be removed from the product. It can appear multiple times on the command line to add multiple language packs. For more information, see the List of language locales section on this page.
--add <one or more workload or component IDs>Optional: One or more workload or component IDs to add. The required components of the artifact are installed, but not the recommended or optional components. You can control additional components globally using --includeRecommended and/or --includeOptional. To include multiple workloads or components, repeat the --add command (for example, --add Workload1 --add Workload2). For finer-grained control, you can append ;includeRecommended or ;includeOptional to the ID (for example, --add Workload1;includeRecommended or --add Workload2;includeRecommended;includeOptional). For more information, see the Workload and component IDs page. You can repeat this option as necessary.
--remove <one or more workload or component IDs>Optional: One or more workload or component IDs to remove. For more information, see our Workload and component IDs page. You can repeat this option as necessary.
--in <path>Optional: The URI or path to a response file.
--allOptional: Whether to install all workloads and components for a product.
--allWorkloadsOptional: Installs all workloads and components, no recommended or optional components.
--includeRecommendedOptional: Includes the recommended components for any workloads that are installed, but not the optional components. The workloads are specified either with --allWorkloads or --add.
--includeOptionalOptional: Includes the optional components for any workloads that are installed, but not the recommended components. The workloads are specified either with --allWorkloads or --add.
--quiet, -qOptional: Don't display any user interface while performing the installation.
--passive, -pOptional: Display the user interface, but don't request any interaction from the user.
--norestartOptional: If present, commands with --passive or --quiet won't automatically restart the machine (if necessary). This is ignored if neither --passive nor --quiet are specified.
--nickname <name>Optional: This defines the nickname to assign to an installed product. The nickname can't be longer than 10 characters.
--productKeyOptional: This defines the product key to use for an installed product. It's composed of 25 alphanumeric characters either in the format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx or xxxxxxxxxxxxxxxxxxxxxxxxx.
--help, --?, -h, -?Display an offline version of this page.
--config <path>Optional and New in 15.9: During an install or modify operation, this determines the workloads and components to add based on a previously saved installation configuration file. This operation is additive and it won't remove any workload or component if they aren't present in the file. Also, items that don't apply to the product won't be added. During an export operation, this determines the location to save the installation configuration file.
Install optionDescription
--installPath <dir>The installation directory for the instance to act upon. For the install command, this is Optional and is where the instance will be installed. For other commands, this is Required and is where the previously installed instance was installed.
--addProductLang <language-locale>Optional: During an install or modify operation, this determines the UI language packs that are installed to the product. It can appear multiple times on the command line to add multiple language packs. If not present, the installation uses the machine locale. For more information, see the List of language locales section on this page.
--removeProductLang <language-locale>Optional: During an install or modify operation, this determines the UI language packs that are to be removed from the product. It can appear multiple times on the command line to add multiple language packs. For more information, see the List of language locales section on this page.
--add <one or more workload or component IDs>Optional: One or more workload or component IDs to add. The required components of the artifact are installed, but not the recommended or optional components. You can control additional components globally using --includeRecommended and/or --includeOptional. To include multiple workloads or components, repeat the --add command (for example, --add Workload1 --add Workload2). For finer-grained control, you can append ;includeRecommended or ;includeOptional to the ID (for example, --add Workload1;includeRecommended or --add Workload2;includeRecommended;includeOptional). For more information, see the Workload and component IDs page. You can repeat this option as necessary.
--remove <one or more workload or component IDs>Optional: One or more workload or component IDs to remove. For more information, see our Workload and component IDs page. You can repeat this option as necessary.
--in <path>Optional: The URI or path to a response file.
--allOptional: Whether to install all workloads and components for a product.
--allWorkloadsOptional: Installs all workloads and components, no recommended or optional components.
--includeRecommendedOptional: Includes the recommended components for any workloads that are installed, but not the optional components. The workloads are specified either with --allWorkloads or --add.
--includeOptionalOptional: Includes the optional components for any workloads that are installed, but not the recommended components. The workloads are specified either with --allWorkloads or --add.
--quiet, -qOptional: Don't display any user interface while performing the installation.
--passive, -pOptional: Display the user interface, but don't request any interaction from the user.
--norestartOptional: If present, commands with --passive or --quiet won't automatically restart the machine (if necessary). This is ignored if neither --passive nor --quiet are specified.
--nickname <name>Optional: This defines the nickname to assign to an installed product. The nickname can't be longer than 10 characters.
--productKeyOptional: This defines the product key to use for an installed product. It's composed of 25 alphanumeric characters either in the format xxxxx-xxxxx-xxxxx-xxxxx-xxxxx or xxxxxxxxxxxxxxxxxxxxxxxxx.
--help, --?, -h, -?Display an offline version of this page.
--config <path>Optional: During an install or modify operation, this determines the workloads and components to add based on a previously saved installation configuration file. This operation is additive and it won't remove any workload or component if they aren't present in the file. Also, items that don't apply to the product won't be added. During an export operation, this determines the location to save the installation configuration file.

Important

When specifying multiple workloads and components, you must repeat the --add or --remove command-line switch for each item.

Layout options

Layout optionsDescription
--layout <dir>Specifies a directory to create an offline install cache. For more information, see Create a network-based installation of Visual Studio.
--lang <one or more language-locales>Optional: Used with --layout to prepare an offline install cache with resource packages with the specified language(s). For more information, see the List of language locales section on this page.
--add <one or more workload or component IDs>Optional: One or more workload or component IDs to add. The required components of the artifact are installed, but not the recommended or optional components. You can control additional components globally using --includeRecommended and/or --includeOptional. For finer-grained control, you can append ;includeRecommended or ;includeOptional to the ID (for example, --add Workload1;includeRecommended or --add Workload2;includeOptional). For more information, see the Workload and component IDs page.
Note: If --add is used, only the specified workloads and components and their dependencies are downloaded. If --add isn't specified, all workloads and components are downloaded to the layout.
--includeRecommendedOptional: Includes the recommended components for any workloads that are installed, but not the optional components. The workloads are specified either with --allWorkloads or --add.
--includeOptionalOptional: Includes the recommended and optional components for any workloads being included in the layout. The workloads are specified with --add.
--keepLayoutVersionNew in 15.3, optional: Apply changes to the layout without updating the version of the layout.
--verifyNew in 15.3, optional: Verify the contents of a layout. Any corrupt or missing files are listed.
--fixNew in 15.3, optional: Verify the contents of a layout. If any files are corrupt or missing, they're redownloaded. Internet access is required to fix a layout.
--clean <one or more paths to catalogs>New in 15.3, optional: Removes old versions of components from a layout that has been updated to a newer version.
Advanced install optionsDescription
--channelId <id>Optional: The ID of the channel for the instance to be installed. This is required for the install command, and ignored for other commands if --installPath is specified.
--channelUri <uri>Optional: The URI of the channel manifest. If updates aren't wanted, --channelUri can point to a non-existent file (for example, --channelUri C:doesntExist.chman). This can be used for the install command; it's ignored for other commands.
--installChannelUri <uri>Optional: The URI of the channel manifest to use for the installation. The URI specified by --channelUri (which must be specified when --installChannelUri is specified) is used to detect updates. This can be used for the install command; it's ignored for other commands.
--installCatalogUri <uri>Optional: The URI of the catalog manifest to use for the installation. If specified, the channel manager attempts to download the catalog manifest from this URI before using the URI in the install channel manifest. This parameter is used to support offline install, where the layout cache will be created with the product catalog already downloaded. This can be used for the install command; it's ignored for other commands.
--productId <id>Optional The ID of the product for the instance that will be installed. This is pre-populated in normal installation conditions.
--waitOptional: The process will wait until the install is completed before returning an exit code. This is useful when automating installations where one needs to wait for the install to finish to handle the return code from that install.
--locale <language-locale>Optional: Change the display language of the user interface for the installer itself. Setting will be persisted. For more information, see the List of language locales section on this page.
--cacheNew in 15.2, optional: If present, packages will be kept after being installed for subsequent repairs. This overrides the global policy setting to be used for subsequent installs, repairs, or modifications. The default policy is to cache packages. This is ignored for the uninstall command. Read how to disable or move the package cache for more information.
--nocacheNew in 15.2, optional: If present, packages will be deleted after being installed or repaired. They'll be downloaded again only if needed and deleted again after use. This overrides the global policy setting to be used for subsequent installs, repairs, or modifications. The default policy is to cache packages. This is ignored for the uninstall command. Read how to disable or move the package cache for more information.
--noUpdateInstallerNew in 15.2, optional: If present, prevents the installer from updating itself when quiet is specified. The installer will fail the command and return a non-zero exit code if noUpdateInstaller is specified with quiet when an installer update is required.
--noWebNew in 15.3, optional: If present, Visual Studio setup uses the files in your layout directory to install Visual Studio. If a user tries to install components that aren't in the layout, setup fails. For more information, see Deploying from a network installation.
Important: This switch doesn't stop Visual Studio setup from checking for updates. For more information, see Control updates to network-based Visual Studio deployments.
--path <name>=<path>New in 15.7, optional: Used to specify custom install paths for the installation. Supported path names are shared, cache, and install.
--path cache=<path>New in 15.7, optional: Uses the location you specify to download installation files. This location can only be set the first time that Visual Studio is installed. Example: --path cache='C:VScache'
--path shared=<path>New in 15.7, optional: Contains shared files for side-by-side Visual Studio installations. Some tools and SDKs install to a location on this drive, while some others might override this setting and install to another drive. Example: --path shared='C:VSshared'
Important: This can be set only once and on the first time that Visual Studio is installed.
--path install=<path>New in 15.7, optional: Equivalent to –-installPath. Specifically, --installPath 'C:VS' and --path install='C:VS' are equivalent. Only one of these commands can be used at a time.
Layout optionsDescription
--layout <dir>Specifies a directory to create an offline install cache. For more information, see Create a network-based installation of Visual Studio.
--lang <one or more language-locales>Optional: Used with --layout to prepare an offline install cache with resource packages with the specified language(s). For more information, see the List of language locales section on this page.
--add <one or more workload or component IDs>Optional: One or more workload or component IDs to add. The required components of the artifact are installed, but not the recommended or optional components. You can control additional components globally using --includeRecommended and/or --includeOptional. For finer-grained control, you can append ;includeRecommended or ;includeOptional to the ID (for example, --add Workload1;includeRecommended or --add Workload2;includeOptional). For more information, see the Workload and component IDs page.
Note: If --add is used, only the specified workloads and components and their dependencies are downloaded. If --add isn't specified, all workloads and components are downloaded to the layout.
--includeRecommendedOptional: Includes the recommended components for any workloads that are installed, but not the optional components. The workloads are specified either with --allWorkloads or --add.
--includeOptionalOptional: Includes the recommended and optional components for any workloads being included in the layout. The workloads are specified with --add.
--keepLayoutVersionOptional: Apply changes to the layout without updating the version of the layout.
--verifyOptional: Verify the contents of a layout. Any corrupt or missing files are listed.
--fixOptional: Verify the contents of a layout. If any files are corrupt or missing, they're redownloaded. Internet access is required to fix a layout.
--clean <one or more paths to catalogs>Optional: Removes old versions of components from a layout that has been updated to a newer version.
Advanced install optionsDescription
--channelId <id>Optional: The ID of the channel for the instance to be installed. This is required for the install command, and ignored for other commands if --installPath is specified.
--channelUri <uri>Optional: The URI of the channel manifest. If updates aren't wanted, --channelUri can point to a non-existent file (for example, --channelUri C:doesntExist.chman). This can be used for the install command; it's ignored for other commands.
--installChannelUri <uri>Optional: The URI of the channel manifest to use for the installation. The URI specified by --channelUri (which must be specified when --installChannelUri is specified) is used to detect updates. This can be used for the install command; it's ignored for other commands.
--installCatalogUri <uri>Optional: The URI of the catalog manifest to use for the installation. If specified, the channel manager attempts to download the catalog manifest from this URI before using the URI in the install channel manifest. This parameter is used to support offline install, where the layout cache will be created with the product catalog already downloaded. This can be used for the install command; it's ignored for other commands.
--productId <id>Optional The ID of the product for the instance that will be installed. This is pre-populated in normal installation conditions.
--waitOptional: The process will wait until the install is completed before returning an exit code. This is useful when automating installations where one needs to wait for the install to finish to handle the return code from that install.
--locale <language-locale>Optional: Change the display language of the user interface for the installer itself. Setting will be persisted. For more information, see the List of language locales section on this page.
--cacheOptional: If present, packages will be kept after being installed for subsequent repairs. This overrides the global policy setting to be used for subsequent installs, repairs, or modifications. The default policy is to cache packages. This is ignored for the uninstall command. Read how to disable or move the package cache for more information.
--nocacheOptional: If present, packages will be deleted after being installed or repaired. They'll be downloaded again only if needed and deleted again after use. This overrides the global policy setting to be used for subsequent installs, repairs, or modifications. The default policy is to cache packages. This is ignored for the uninstall command. Read how to disable or move the package cache for more information.
--noUpdateInstallerOptional: If present, prevents the installer from updating itself when quiet is specified. The installer will fail the command and return a non-zero exit code if noUpdateInstaller is specified with quiet when an installer update is required.
--noWebOptional: If present, Visual Studio setup uses the files in your layout directory to install Visual Studio. If a user tries to install components that aren't in the layout, setup fails. For more information, see Deploying from a network installation.
Important: This switch doesn't stop Visual Studio setup from checking for updates. For more information, see Control updates to network-based Visual Studio deployments. New in 16.3.5: This switch prevents errors and improves performance with offline installs and updates.
--path <name>=<path>Optional: Used to specify custom install paths for the installation. Supported path names are shared, cache, and install.
--path cache=<path>Optional: Uses the location you specify to download installation files. This location can only be set the first time that Visual Studio is installed. Example: --path cache='C:VScache'
--path shared=<path>Optional: Contains shared files for side-by-side Visual Studio installations. Some tools and SDKs install to a location on this drive, while some others might override this setting and install to another drive. Example: --path shared='C:VSshared'
Important: This can be set only once and on the first time that Visual Studio is installed.
--path install=<path>Optional: Equivalent to –-installPath. Specifically, --installPath 'C:VS' and --path install='C:VS' are equivalent. Only one of these commands can be used at a time.

List of workload IDs and component IDs

For a list of workload and component IDs sorted by Visual Studio product, see the Visual Studio workload and component IDs page.

List of language locales

Language-localeLanguage
Cs-czCzech
De-deGerman
En-usEnglish
Es-esSpanish
Fr-frFrench
It-itItalian
Ja-jpJapanese
Ko-krKorean
Pl-plPolish
Pt-brPortuguese - Brazil
Ru-ruRussian
Tr-trTurkish
Zh-cnChinese - Simplified
Zh-twChinese - Traditional

Error codes

Depending on the result of the operation, the %ERRORLEVEL% environment variable is set to one of the following values:

ValueResult
0Operation completed successfully
1602Operation was canceled
1641Operation completed successfully, and reboot was initiated
3010Operation completed successfully, but install requires reboot before it can be used
5003Bootstrapper failed to download installer
5004Operation was canceled
5005Bootstrapper command-line parse error
5007Operation was blocked - the computer does not meet the requirements
-1073741510Microsoft Visual Studio Installer was terminated (by the user or external process)
Other
(for example:
-1, 1, 1603)
Failure condition occurred - check the logs for more information

Each operation generates several log files in the %TEMP% directory that indicate the progress of the installation. Sort the folder by date and look for files that begin with dd_bootstrapper, dd_client, and dd_setup for the bootstrapper, the installer app, and the setup engine, respectively.

Get support

Office 2013 Msi Download

Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.

Vs_setup.msi Download 2010 Ultimate

We also offer an installation chat (English only) support option for installation-related issues.

Here are a few more support options:

  • Report product issues to us via the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
  • Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.
  • Use your GitHub account to talk to us and other Visual Studio developers in the Visual Studio conversation in the Gitter community.

Microsoft Msi Free Downloads

See also