Downloads of v 3.1.8:


Last Update:

08 Sep 2020

Package Maintainer(s):

Software Author(s):

  • Microsoft


microsoft .net core runtime redistributable

Microsoft .NET Core Runtime (Portable)

This is not the latest version of Microsoft .NET Core Runtime (Portable) available.

3.1.8 | Updated: 08 Sep 2020



Downloads of v 3.1.8:


Software Author(s):

  • Microsoft

Microsoft .NET Core Runtime (Portable) 3.1.8

This is not the latest version of Microsoft .NET Core Runtime (Portable) available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Microsoft .NET Core Runtime (Portable), run the following command from the command line or from PowerShell:


To upgrade Microsoft .NET Core Runtime (Portable), run the following command from the command line or from PowerShell:


To uninstall Microsoft .NET Core Runtime (Portable), 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 dotnetcore-runtime.portable -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 dotnetcore-runtime.portable -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 dotnetcore-runtime.portable installed
    name: dotnetcore-runtime.portable
    state: present
    version: 3.1.8
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'dotnetcore-runtime.portable' do
  action    :install
  version  '3.1.8'
  source   'STEP 3 URL'

See docs at

    Name: dotnetcore-runtime.portable,
    Version: 3.1.8,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller dotnetcore-runtime.portable
   Name     = 'dotnetcore-runtime.portable'
   Ensure   = 'Present'
   Version  = '3.1.8'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'dotnetcore-runtime.portable':
  provider => 'chocolatey',
  ensure   => '3.1.8',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install dotnetcore-runtime.portable version="3.1.8" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 05 Oct 2020.


.NET Core is a general purpose development platform maintained by Microsoft and the .NET community on GitHub. It is cross-platform, supporting Windows, macOS and Linux, and can be used in device, cloud, and embedded/IoT scenarios.

This package is required to run console applications with the .NET Core runtime. The .NET Core Runtime is installed in the Chocolatey package installation directory, enabling side-by-side install of multiple versions. No shims are generated by default, so this package will also coexist peacefully with the dotnetcore-runtime.install package. To enable side-by-side installs, pass the --sxs argument to Chocolatey when installing this package.

.NET Core supports Windows 7 SP1 / Server 2008 R2 or later. On Windows 7 / Server 2008 R2, security update KB2533623 must be installed, according to documented system requirements.

The package supports the following parameters (--package-parameters, --params):

  • ShimDotnetExe - allows Chocolatey to generate a shim for dotnet.exe, effectively adding dotnet.exe to PATH

Example: cinst -y --params="ShimDotnetExe" dotnetcore-runtime.portable

$ErrorActionPreference = 'Stop'
Set-StrictMode -Version 2

$data = & (Join-Path -Path (Split-Path -Path $MyInvocation.MyCommand.Path) -ChildPath data.ps1)

function Test-ShouldShimDotnetExe
    return $Env:chocolateyPackageParameters -like '*ShimDotnetExe*'

function Test-SideBySide
        [string] $packageDir,
        [string] $packageName,
        [string] $version

    return $packageDir -like "*\$packageName.$version*"

$packageDir = Split-Path -Parent -Path (Split-Path -Parent -Path $MyInvocation.MyCommand.Definition)
$sxs = Test-SideBySide -packageDir $packageDir -packageName $data.PackageName -version $data.Version
if ($sxs)
    Write-Verbose 'Performing a side-by-side installation.'
    Write-Verbose 'Performing a non-side-by-side installation'

$shouldShimDotnetExe = Test-ShouldShimDotnetExe
if ($shouldShimDotnetExe)
    Write-Output "A shim for dotnet.exe will be generated, as requested. The 'dotnet' command will be available from all command prompts."
    if ($sxs)
        Write-Warning 'In a side-by-side installation, only the last installed dotnet.exe will be accessible via the shim.'
    Write-Output "A shim for dotnet.exe will not be generated. The 'dotnet' command will need to be invoked using the full path ($packageDir\dotnet.exe)."

$arguments = @{
    packageName = $data.PackageName
    unzipLocation = $packageDir
    url = $data.Url
    checksum = $data.Checksum
    checksumType = $data.ChecksumType
    url64bit = $data.Url64
    checksum64 = $data.Checksum64
    checksumType64 = $data.ChecksumType64
Set-StrictMode -Off
Install-ChocolateyZipPackage @arguments | Out-Null # returns unzipLocation
Set-StrictMode -Version 2

Write-Debug "Generating ShimGen .ignore files"
$rootDotnetExePath = Join-Path -Path $packageDir -ChildPath 'dotnet.exe'
Get-ChildItem -Path $packageDir -Include '*.exe' -Recurse | ForEach-Object -Process {
    $filePath = $_.FullName
    Write-Debug "Found exe file: $filePath"
    if ($filePath -ne $rootDotnetExePath -or (-not $shouldShimDotnetExe))
        $ignoreFilePath = "$filePath.ignore"
        Write-Debug "Creating file $ignoreFilePath"
        New-Item -Path $ignoreFilePath -ItemType File -Force | Out-Null
    PackageName = 'dotnetcore-runtime.portable'
    Version = '3.1.8'
    Url = ''
    Checksum = 'd86682842da87bf7809508436d19e8e43dd4ddf44cce3e19e8a7a1fa1b1dd0f5e9d735a0be078322533d96b3d002c731142a463d2f4dc34979e5525d3f3687a5'
    ChecksumType = 'sha512'
    Url64 = ''
    Checksum64 = '6c6a2e0d2e9e6750df74badf6260d9657838a5fbe2d088f97c7e415379180a296e7a951e579be8182a8f80cd87e61e24c8e3807d4727d089b4e3a2902ff4bc8f'
    ChecksumType64 = 'sha512'

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
Microsoft .NET Core Runtime (Portable) 5.0.0-rc2204755 8 Tuesday, October 13, 2020 Exempted
Microsoft .NET Core Runtime (Portable) 5.0.0-rc12045114 4 Sunday, October 11, 2020 Exempted
Microsoft .NET Core Runtime (Portable) 3.1.8 68 Tuesday, September 8, 2020 Approved
Microsoft .NET Core Runtime (Portable) 3.1.5 172 Tuesday, June 9, 2020 Approved
Microsoft .NET Core Runtime (Portable) 3.1.3 475 Thursday, April 2, 2020 Approved
Microsoft .NET Core Runtime (Portable) 3.1.2 167 Tuesday, February 18, 2020 Approved


.NET Core Release Notes


Initial package release for .NET Core 2.0.6.

Discussion for the Microsoft .NET Core Runtime (Portable) Package

Ground Rules:

  • This discussion is only about Microsoft .NET Core Runtime (Portable) and the Microsoft .NET Core Runtime (Portable) 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 .NET Core Runtime (Portable), 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