Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

1,806,712

Downloads of v 14.0.33321:

594,564

Last Update:

24 Feb 2024

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

microsoft-vclibs vclibs uwp

Microsoft.VCLibs (Install)

  • 1
  • 2
  • 3

14.0.33321 | Updated: 24 Feb 2024

Downloads:

1,806,712

Downloads of v 14.0.33321:

594,564

Maintainer(s):

Software Author(s):

  • Microsoft

Microsoft.VCLibs (Install) 14.0.33321

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Microsoft. The inclusion of Microsoft trademark(s), if any, upon this webpage is solely to identify Microsoft goods or services and not for commercial purposes.

  • 1
  • 2
  • 3

This Package Contains an Exempted Check

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Exemption for this package version only:

Package Scanner thinks there should be more files to scan than there actually was, this appears to be an issue with Scanner rather than this package.

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Microsoft.VCLibs (Install), run the following command from the command line or from PowerShell:

>

To upgrade Microsoft.VCLibs (Install), run the following command from the command line or from PowerShell:

>

To uninstall Microsoft.VCLibs (Install), run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

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

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • 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 https://community.chocolatey.org/api/v2/. 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. Copy Your Script

choco upgrade microsoft-vclibs-140-00 -y --source="'INTERNAL REPO 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 microsoft-vclibs-140-00 -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install microsoft-vclibs-140-00
  win_chocolatey:
    name: microsoft-vclibs-140-00
    version: '14.0.33321'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'microsoft-vclibs-140-00' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '14.0.33321'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller microsoft-vclibs-140-00
{
    Name     = "microsoft-vclibs-140-00"
    Version  = "14.0.33321"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'microsoft-vclibs-140-00':
  ensure   => '14.0.33321',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

WARNING

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

Description

This is the Microsoft C++ UWP framework packages.
Windows desktop applications that have a dependency on the C++ Runtime libraries must specify the corresponding version of the C++ Runtime framework package for Desktop Bridge during creation of the application package. This must be done instead of just redistributing the C++ Runtime libraries that are included with Visual Studio or the Visual C++ Runtime redistributable (VCRedist). Windows desktop applications that run in a Desktop Bridge container cannot use the C++ Runtime libraries that are included with Visual Studio or VCRedist. An application that's running in a Desktop Bridge container and that uses an incorrect version of the C++ runtime libraries might fail when it tries to access resources such as the file system or the registry. This article discusses how to create a Desktop Bridge container that includes the correct C++ Runtime libraries.

NOTE: This is a manually updated package.


tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"

. $(Join-Path -Path $toolsDir -ChildPath "$($env:ChocolateyPackageName)-helpers.ps1")

$allAppXPackages = Get-AppxPackage
# there is likely going to be two packages returned for x86 and x64.
# we don't care about the architecture, just the version and they will both be the same.
$installedAppXPackage = @($allAppXPackages | Where-Object -Property Name -eq $internalAppXPackage.PackageName)
if ($installedAppXPackage.Count -gt 0) {
  # check there are no packages that take our package as a dependency
  if (Test-AppXDependency -Name $internalAppXPackage.PackageName -PackageList $allAppXPackages) {
    Write-Warning "We cannot remove $($internalAppXPackage.PackageName) as it is a dependency of another app package. Please remove it manually and then install this package again."
    return
  }
  else {
    # when you remove a package, you don't remove it per architecture. You just remove it for all architectures.
    Write-Host "Attempting to remove $($internalAppXPackage.PackageName). Note that this may fail and you may have to remove it manually."
    Remove-AppxPackage -Package $installedAppXPackage[0].PackageFullName
  }
}
else {
  Write-Warning "The $($internalAppXPackage.PackageName) app package does not appear to be installed."
}
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

# This can only be installed in a user context (*-AppxPackage).
# You cannot use *-AppxProvisionedPackage as it produced 'Element not found'.

$toolsDir = "$(Split-Path -Parent $MyInvocation.MyCommand.Definition)"

. $(Join-Path -Path $toolsDir -ChildPath "$($env:ChocolateyPackageName)-helpers.ps1")

$appxFileNamex86 = 'Microsoft.VCLibs.x86.14.00.Desktop.appx'
$appxFileNamex64 = 'Microsoft.VCLibs.x64.14.00.Desktop.appx'

$windowsVersion = [Environment]::OSVersion.Version
if ($windowsVersion.Major -lt "10") {
    throw "This package requires a minimum of Windows 10 / Server 2019."
}

# .appx is only  supported on Windows 10 version 1709 and later - https://learn.microsoft.com/en-us/windows/msix/supported-platforms
# See https://en.wikipedia.org/wiki/Windows_10_version_history for build numbers
if ($windowsVersion.Build -lt "16299") {
    throw "This package requires a minimum of Windows 10 / Server 2019 version 1709 / OS build 16299."
}

$removeAppXPackage = $false         # used to indicate if we should remove the currently installed AppX package before continuing
# get all of the packages as we may need to use that later
$allAppXPackages = Get-AppxPackage
# there is likely going to be two packages returned for x86 and x64.
# we don't care about the architecture, just the version and they will both be the same.
$installedAppXPackage = @($allAppXPackages | Where-Object -Property Name -EQ $internalAppXPackage.PackageName)
if (($installedAppXPackage.Count -gt 0) -and ([version]$installedAppXPackage[0].Version -ge [version]$internalAppXPackage.Version)) {
    # You can't install an older version of an installed appx package, you'd need to remove it first.
    # We also don't want to remove later versions as they will have been installed outside of the package ecosystem
    #   and may have been installed for very good reasons by another application.
    # We also don't want to just remove the same version again either for similar reasons.
    # If the user pases the `-f` or `--force` option to Chocolatey CLI we can attempt uninstall
    Write-Warning "The installed version of the app package, $($installedAppXPackage[0].Version), is the same or newer than the version this Chocolatey package installs, $($internalAppXPackage.Version)."
    Write-Warning "It may have been automatically updated on your computer as part of a Windows Update or another application."

    if ($env:ChocolateyForce) {
        Write-Warning "The '--force' option has been used so we will attempt to remove version $($installedAppXPackage[0].Version) and install version $($internalAppXPackage.Version)."
        $removeAppXPackage = $true
    }
    else {
        # we will not throw an error if a later version of the AppX package is detected
        Write-Warning "We cannot install this package version, $($internalAppXPackage.Version), over the installed version, $($installedAppXPackage[0].Version), without removing it first. Please remove it manually, or add the '--force' option to the command line."
        return
    }
}

if ($removeAppXPackage) {
    # we need to check we CAN remove the package - if it is a dependent package, it will fail if we try
    if (Test-AppXDependency -Name $internalAppXPackage.PackageName -PackageList $allAppXPackages) {
    Write-Warning "We cannot remove version $($installedAppXPackage[0].Version) of $($internalAppXPackage.PackageName) as it is a dependency of another app package. Please remove it manually and then install this package again."
    return
    }

    # when you remove a package, you don't remove it per architecture. You just remove it for all architectures.
    Write-Warning "Attempting to remove version $($installedAppXPackage[0].Version) of $($internalAppXPackage.PackageName). Note that this may fail and you may have to remove it manually."
    Remove-AppxPackage -Package $installedAppXPackage[0].PackageFullName
}

# For x64, the x86 version of the package is always installed too by the looks of it
$downloadArguments = @{
    packageName  = $env:ChocolateyPackageName
    fileFullPath = Join-Path -Path $toolsDir -ChildPath $appxFileNamex86
    url          = 'https://aka.ms/Microsoft.VCLibs.x86.14.00.Desktop.appx'
    checksum     = 'a7fb9d76e07b36d868179eb53ffd13740c25242176fa363f154798cf34edd4a9'
    checksumType = 'SHA256'
}

Get-ChocolateyWebFile @downloadArguments
Add-AppxPackage -Path (Join-Path -Path $toolsDir -ChildPath $appxFileNamex86)

if (Get-OSArchitectureWidth -eq '64') {
    $downloadArguments = @{
        packageName  = $env:ChocolateyPackageName
        fileFullPath = Join-Path -Path $toolsDir -ChildPath $appxFileNamex64
        url          = 'https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx'
        checksum     = 'b56a9101f706f9d95f815f5b7fa6efbac972e86573d378b96a07cff5540c5961'
        checksumType = 'SHA256'
    }

    Get-ChocolateyWebFile @downloadArguments
    Add-AppxPackage -Path (Join-Path -Path $toolsDir -ChildPath $appxFileNamex64)
}
tools\microsoft-vclibs-140-00-helpers.ps1
$ErrorActionPreference = 'Stop'

$internalAppXPackage = @{
    SoftwareName = 'Microsoft.VCLibs'
    PackageName  = 'Microsoft.VCLibs.140.00.UWPDesktop'
    #! This package version must have the 4 version segments that MATCH EXACTLY with the installed AppX version. EXACTLY.
    Version      = '14.0.33321.0'
}

function Test-AppXDependency {
    [CmdletBinding()]

    Param (
        [Parameter(Mandatory = $true)]
        [String]
        $Name,

        # An array of packages that should be the output from Get-AppXPackages
        [Parameter(Mandatory = $true)]
        [Object[]]
        $PackageList
    )

    ForEach ($pkg in $PackageList) {
        if ($pkg.Dependencies.Name -contains $Name) {
            return $true
        }
    }

    return $false
}

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.

Add to Builder Version Downloads Last Updated Status
Microsoft.VCLibs (Install) 14.0.30704.0 1212148 Friday, July 14, 2023 Exempted

This package has no dependencies.

Discussion for the Microsoft.VCLibs (Install) Package

Ground Rules:

  • This discussion is only about Microsoft.VCLibs (Install) and the Microsoft.VCLibs (Install) 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 Microsoft.VCLibs (Install), 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