Downloads of v 10.0.60828:


Last Update:

04 Sep 2018

Package Maintainer(s):

Software Author(s):

  • Microsoft


vstor2010 vstor VisualStudio Microsoft Office .NET dotnet runtime

Visual Studio 2010 Tools for Office Runtime

  • 1
  • 2
  • 3

10.0.60828 | Updated: 04 Sep 2018



Downloads of v 10.0.60828:


Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Visual Studio 2010 Tools for Office Runtime 10.0.60828

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install Visual Studio 2010 Tools for Office Runtime, run the following command from the command line or from PowerShell:


To upgrade Visual Studio 2010 Tools for Office Runtime, run the following command from the command line or from PowerShell:


To uninstall Visual Studio 2010 Tools for Office Runtime, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade vstor2010 -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade vstor2010 -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure vstor2010 installed
    name: vstor2010
    state: present
    version: 10.0.60828
    source: STEP 3 URL

See docs at

chocolatey_package 'vstor2010' do
  action    :install
  version  '10.0.60828'
  source   'STEP 3 URL'

See docs at

    Name: vstor2010,
    Version: 10.0.60828,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller vstor2010
   Name     = 'vstor2010'
   Ensure   = 'Present'
   Version  = '10.0.60828'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'vstor2010':
  provider => 'chocolatey',
  ensure   => '10.0.60828',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install vstor2010 version="10.0.60828" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 05 Sep 2018.


Visual Studio 2010 Tools for Office Runtime is required to run Microsoft Office based solutions built using Microsoft Visual Studio 2010, 2012, 2013, 2015 and 2017.

Prerequisite Note

Running Office customizations built for this version of Visual Studio Tools for Office requires at least one of the following versions of Microsoft Office: 2007, 2010, 2013, 2016. However, this package does not have an Office install as a pre-requisite. It will attempt to discover an Office install before it proceeds, but it will only provide a warning if one is not found.

$ErrorActionPreference = 'Stop'

$packageArgs = @{
   packageName  = $env:ChocolateyPackageName
   url           = ''
   fileType      = 'EXE'
   Checksum      = '2B656781C884647A5368DADB0A4D63488413EA59A86D73E1802308D526B2BF84'
   checksumType  = 'sha256'
   softwareName  = 'Microsoft Visual Studio 2010 Tools for Office Runtime*'
   silentArgs    = '/quiet /norestart'
   validExitCodes= @(0, 3010)

$OfficeApps = 'winword.exe','excel.exe','outlook.exe','powerpnt.exe','vision.exe','infopath.exe','winproj.exe'
$OfficeVersions = 12,14,15,16

$Found = $false
foreach ($app in $OfficeApps) {
   $RegPath = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\$App"
   if (Test-Path $RegPath) {
      $key = Get-ItemProperty -Path $RegPath -Name "Path"
      $ver = $key.path -replace '.*?(\d\d)\\$','$1'
      if ($OfficeVersions -contains $ver) {
         $Found = $true

if (-not $Found) {
   Write-Warning "No required application of MS Office was found!"
   Write-Warning "The install will continue, but customizations written"
   Write-Warning "for this runtime will not work without MS Office."

Install-ChocolateyPackage @packageArgs 
$ErrorActionPreference = 'Stop'

$SoftwareName = 'Microsoft Visual Studio 2010 Tools for Office Runtime*'

[array]$key = Get-UninstallRegistryKey -SoftwareName $softwareName

if ($key.Count -eq 0) {
   Write-Warning "$env:ChocolateyPackageName has already been uninstalled by other means."
} elseif ($key.Count -le 2) {
   # VSTOR install usually creates two uninstall keys.  Either does the job fully,
   #    but only one is silent for Chocolatey's Automatic Uninstaller
   $uninstallString = $key[0].UninstallString
   if ($uninstallString -like 'MsiExec*') {
      $packageArgs = @{
         packageName   = $env:ChocolateyPackageName
         softwareName  = $SoftwareName
         file          = $uninstallString
         fileType      = 'MSI'
         silentArgs    = "/qn /norestart"
         validExitCodes= @(0, 3010, 1605, 1614, 1641) #
   } else {
      $packageArgs = @{
         packageName   = $env:ChocolateyPackageName
         softwareName  = $SoftwareName
         file          = $uninstallString
         fileType      = 'EXE'
         silentArgs    =  '/uninstall /quiet /norestart'
         validExitCodes= @(0)
   Uninstall-ChocolateyPackage @packageArgs
} elseif ($key.Count -gt 2) {
   Write-Warning "$($key.Count) matches found!"
   Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
   Write-Warning "Please alert package maintainer the following keys were matched:"
   $key | % {Write-Warning "- $($_.DisplayName)"}


These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft
* updates,
* supplements,
* Internet-based services, and 
* support services

for this software, unless other terms accompany those items. If so, those terms apply.

**If you comply with these license terms, you have the rights below.**
1.  **INSTALLATION AND USE RIGHTS.** You may install and use any number of copies of the software on your devices.
2.  **Scope of License.** The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. You may not
    * disclose the results of any benchmark tests of the software to any third party without Microsoft’s prior written approval;
    * work around any technical limitations in the software;
    * reverse engineer, decompile or disassemble the software, except and only to the extent that applicable law expressly permits, despite this limitation;
    * make more copies of the software than specified in this agreement or allowed by applicable law, despite this limitation;
    * publish the software for others to copy;
    * rent, lease or lend the software;
    * transfer the software or this agreement to any third party; or
    * use the software for commercial software hosting services.
3.  **BACKUP COPY.** You may make one backup copy of the software. You may use it only to reinstall the software.
4.  **DOCUMENTATION.** Any person that has valid access to your computer or internal network may copy and use the documentation for your internal, reference purposes.
5.  **Export Restrictions.** The software is subject to United States export laws and regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see
6.  **SUPPORT SERVICES.** Because this software is “as is,” we may not provide support services for it.
7.  **Entire Agreement.** This agreement, and the terms for supplements, updates, Internet-based services and support services that you use, are the entire agreement for the software and support services.
8.  **Applicable Law.** something.  
    a. **United States.** If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles. The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort.
    b. **Outside the United States.** If you acquired the software in any other country, the laws of that country apply.
9.  **Legal Effect.** This agreement describes certain legal rights. You may have other rights under the laws of your country. You may also have rights with respect to the party from whom you acquired the software. This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so.
10.  **Disclaimer of Warranty. The software is licensed “as-is.” You bear the risk of using it. Microsoft gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this agreement cannot change. To the extent permitted under your local laws, Microsoft excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.**
11.  **Limitation on and Exclusion of Remedies and Damages. You can recover from Microsoft and its suppliers only direct damages up to U.S. $5.00. You cannot recover any other damages, including consequential, lost profits, special, indirect or incidental damages.**  
This limitation applies to
    * anything related to the software, services, content (including code) on third party Internet sites, or third party programs; and
    * claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law.   

    It also applies even if Microsoft knew or should have known about the possibility of the damages. The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Visual Studio 2010 Tools for Office Runtime 10.0.60724 1668 Wednesday, February 21, 2018 Approved
Discussion for the Visual Studio 2010 Tools for Office Runtime Package

Ground Rules:

  • This discussion is only about Visual Studio 2010 Tools for Office Runtime and the Visual Studio 2010 Tools for Office Runtime package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Visual Studio 2010 Tools for Office Runtime, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus