Downloads of v 4.6.00081.20150925:


Last Update:

28 Sep 2015

Package Maintainer(s):

Software Author(s):

  • Microsoft


microsoft .net framework 4.6 redistributable

Microsoft .NET Framework 4.6

  • 1
  • 2
  • 3

4.6.00081.20150925 | Updated: 28 Sep 2015



Downloads of v 4.6.00081.20150925:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Microsoft .NET Framework 4.6 4.6.00081.20150925

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install Microsoft .NET Framework 4.6, run the following command from the command line or from PowerShell:


To upgrade Microsoft .NET Framework 4.6, run the following command from the command line or from PowerShell:


To uninstall Microsoft .NET Framework 4.6, 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 dotnet4.6 -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 dotnet4.6 -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 dotnet4.6 installed
    name: dotnet4.6
    state: present
    version: 4.6.00081.20150925
    source: STEP 3 URL

See docs at

chocolatey_package 'dotnet4.6' do
  action    :install
  version  '4.6.00081.20150925'
  source   'STEP 3 URL'

See docs at

    Name: dotnet4.6,
    Version: 4.6.00081.20150925,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller dotnet4.6
   Name     = 'dotnet4.6'
   Ensure   = 'Present'
   Version  = '4.6.00081.20150925'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'dotnet4.6':
  provider => 'chocolatey',
  ensure   => '4.6.00081.20150925',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install dotnet4.6 version="4.6.00081.20150925" 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 was approved by moderator jberezanski on 28 Sep 2015.


The Microsoft .NET Framework 4.6 is a highly compatible, in-place update to the Microsoft .NET Framework 4, Microsoft .NET Framework 4.5, Microsoft .NET Framework 4.5.1 and Microsoft .NET Framework 4.5.2. The web installer is a small package that automatically determines and downloads only the components applicable for a particular platform.

Function IsInstalled {
    $ver = (Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full').Release
    return (!($ver -eq $null) -and ($ver -ge 393295))

if (IsInstalled) {
    Write-Host "Microsoft .NET Framework 4.6 or later is already installed"
else {
    $packageName = 'DotNet46'
    $installerType = 'exe'
    $Url = ''
    $silentArgs = "/Passive /NoRestart /Log ""$env:temp\net46.log"""
    $validExitCodes = @(
        0, # success
        3010 # success, restart required

    Install-ChocolateyPackage $packageName $installerType $silentArgs $Url -validExitCodes $validExitCodes

    if (-Not (IsInstalled)) {
        Write-Host "A restart is required to finalise the Microsoft .NET Framework 4.6 installation"

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
Dot Net 4.6 Framework RC 4.6.00057.0-RC 587 Saturday, May 9, 2015 Exempted

This package has no dependencies.

Discussion for the Microsoft .NET Framework 4.6 Package

Ground Rules:

  • This discussion is only about Microsoft .NET Framework 4.6 and the Microsoft .NET Framework 4.6 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 Framework 4.6, 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