Downloads of v 10.0.10586.15:


Last Update:

16 Jul 2016

Package Maintainer(s):

Software Author(s):

  • Microsoft


windbg sos sos.dll debugging

Debugging Tools for Windows (windbg)

  • 1
  • 2
  • 3

10.0.10586.15 | Updated: 16 Jul 2016



Downloads of v 10.0.10586.15:



Software Author(s):

  • Microsoft

  • 1
  • 2
  • 3
Debugging Tools for Windows (windbg) 10.0.10586.15

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Debugging Tools for Windows (windbg), run the following command from the command line or from PowerShell:


To upgrade Debugging Tools for Windows (windbg), run the following command from the command line or from PowerShell:


To uninstall Debugging Tools for Windows (windbg), 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

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 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 windbg -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 windbg -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install windbg
    name: windbg
    version: '10.0.10586.15'
    state: present

See docs at

chocolatey_package 'windbg' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '10.0.10586.15'

See docs at

cChocoPackageInstaller windbg
    Name     = "windbg"
    Version  = "10.0.10586.15"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'windbg':
  ensure   => '10.0.10586.15',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. 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 doc on 17 Jul 2016.


Microsoft Windows Debugger (WinDbg) is a powerful Windows-based debugger that is capable of both user-mode and kernel-mode debugging. WinDbg provides debugging for the Windows kernel, kernel-mode drivers, and system services, as well as user-mode applications and drivers.

The package will copy sos.dll from the most recent .NET runtime on your machine to the same directory where windbg.exe is installed.

Package Parameters

The following package parameters can be set:

  • /SymbolPath:'D:\Symbols' - The local path to store symbols in (and also sets the _NT_SYMBOL_PATH environment variable)

These parameters can be passed to the installer with the use of -params.
For example: -params '"/SymbolPath:c:\symbols"'.

    [string] $SymbolPath = "$env:SYSTEMROOT\Symbols"

$ErrorActionPreference = 'Stop';

$arguments = @{}

$packageParameters = $env:chocolateyPackageParameters

# Now parse the packageParameters using good old regular expression
if ($packageParameters) {
    $match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
    $option_name = 'option'
    $value_name = 'value'

    if ($packageParameters -match $match_pattern ){
        $results = $packageParameters | Select-String $match_pattern -AllMatches
        $results.matches | % {
        Throw "Package Parameters were found but were invalid (REGEX Failure)"

    if ($arguments.ContainsKey("SymbolPath")) {
        $SymbolPath = $arguments["SymbolPath"]
} else {
    Write-Debug "No Package Parameters Passed in"

$tempFolder = "$env:temp\chocolatey\windbg"
mkdir $tempFolder -ErrorAction SilentlyContinue | Out-Null

$files = @{
  [uri] "" = "5485A0196019040933CA3D2AC191ADD8";
  [uri] "" = "B613D33E83BA7957A541190495298C8C";
  [uri] "" = "1F6FDBFF5003F0C51ACACB874E261CE6";
  [uri] "" = "252400AA6C5D21200AAB26B7DDF9E922";
  [uri] "" = "95BCDD0525D60B776154CB3BA644D0F1";
  [uri] "" = "4FD5ACDDF5A847D871D1F649B9357D61";
  [uri] "" = "6C810D6810FDE05122B529783B0F4B7F";
  [uri] "" = "3F081494D7DAB394EB4A2328C61A8933";
  [uri] "" = "07F868A5A376E25986013105273FD4BC";
  [uri] "" = "81FE210D77A396179E9CD38429BD5A98";
  [uri] "" = "7FA3C9D094EB44F965C00D3881BC4826";
  [uri] "" = "CCAEB708D0E9ED0C20E83EE231B5D17B";
  [uri] "" = "4E11957C0FEC91452AD6E8F25EB6E42E";
  [uri] "" = "C5FF97BE7BF22E3285FCC8F056601571";
  [uri] "" = "18730B9DB7CA4DEA724A79A614AF0E10";
  [uri] "" = "A5CFE736004236FE8CE13534AA1F9267";
  [uri] "" = "4B6497BBEC3221B4F11CD9B7A310CD70";
  [uri] "" = "C5A87344B6DFC0713319F55721014ACD";
  [uri] "" = "2CFEEDD8D04072993CD69D0111C949CD";
  [uri] "" = "49357E854D13B49F6CC6857788EEE3E4";
  [uri] "" = "20CDBAD7500CC6D7C62F48B4C6277090";
  [uri] "" = "74AD6FE4798BE84E3DF5D30EEA4CF30F";
  [uri] "" = "7127A943A5073827B4F9A5420E817640";
  [uri] "" = "B1901462BB2A6ECFDE18FBB06D3D88BE";
  [uri] "" = "0F4F0278231DC5D86B10D7D37B8FDB0F";
  [uri] "" = "8F9439AA9C6479C4DD3056022D280A31";
  [uri] "" = "1CE023028A276A8EB770744C9CF94A6E";
  [uri] "" = "A421FDCD0371EDDE135924577559C60C";
  [uri] "" = "8F76087A96021DF5A78390FB118905E5";
  [uri] "" = "69183D31031FBEBAA771B4F34AFA608B";
  [uri] "" = "C3B6C376C865ACC0A72ECA763C5A281C";
  [uri] "" = "797B3CC82C95F2D82B7EEFEE83C735A4";
  [uri] "" = "28C0F31D28CB266F5589A23ABB463296";
  [uri] "" = "D02DC8B69A702A47C083278938C4D2F1";
  [uri] "" = "8668B5B4DE5F343A59381F23C52E4324";
  [uri] "" = "70D38BE03DEA8DF81E98AABFD521B531";
  [uri] "" = "02B5F85874DCA60D890150CB0021C1B6";
  [uri] "" = "9DADFA94AF72E145E9E751EAA09939BE";
  [uri] "" = "3BE4AEF745068B849EB480F12FD27496";

foreach ($file in $files.GetEnumerator()) {    
    Get-ChocolateyWebFile -PackageName "windbg" -url $file.Key.AbsoluteUri -Checksum $file.Value -checksumType MD5 -FileFullPath ([System.IO.Path]::Combine($tempFolder, [System.IO.Path]::GetFilename($file.Key.LocalPath)))

Install-ChocolateyInstallPackage "windbg" "msi" "/q" "$tempFolder\SDK Debuggers-x86_en-us.msi"

if(${env:ProgramFiles(x86)} -ne $null){ $programFiles86 = ${env:ProgramFiles(x86)} } else { $programFiles86 = $env:ProgramFiles }
$windbgPath = (Join-Path $programFiles86 "Windows Kits\10\Debuggers")

[Environment]::SetEnvironmentVariable( '_NT_SYMBOL_PATH', "symsrv*symsrv.dll*$SymbolPath*", 'User')
$env:_NT_SYMBOL_PATH = "symsrv*symsrv.dll*$SymbolPath*"

$fxDir = "$env:windir\Microsoft.NET\Framework"
if(Test-Path $fxDir) {
    $frameworksx86 = dir "$fxdir\v*" | ? { $_.psiscontainer -and $_.Name -match "v[0-9]" }

$statement = @"
    copy-item (join-path '$($frameworksx86[-1])' "sos.dll") '$windbgPath\x86';
    copy-item '$windbgPath\x86\windbg.exe' '$windbgPath\x86\windbgx86.exe';
    Install-ChocolateyDesktopLink '$windbgPath\x64\windbg.exe';
    Install-ChocolateyDesktopLink '$windbgPath\x86\windbgx86.exe';
$fxDir = "${fxdir}64"
if(Test-Path $fxDir) {
    $frameworksx64 = dir "$fxdir\v*" | ? { $_.psiscontainer -and $_.Name -match "v[0-9]"}
    $statement += @"
    copy-item (join-path '$($frameworksx64[-1])' "sos.dll") '$windbgPath\x64';
Start-ChocolateyProcessAsAdmin "$statement" -minimized -nosleep

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
Debugging Tools for Windows (windbg) 8.59.20160823 136637 Wednesday, August 24, 2016 Approved
Debugging Tools for Windows (windbg) 8.59.20141003 6876 Saturday, October 4, 2014 Approved
Debugging Tools for Windows (windbg) 8.59.20140318 1311 Tuesday, March 18, 2014 Unknown
Debugging Tools for Windows (windbg) 8.59.20140202 734 Monday, February 3, 2014 Unknown
Debugging Tools for Windows (windbg) 8.59.20140201 424 Sunday, February 2, 2014 Unknown
Debugging Tools for Windows (windbg) 8.59.20130717 924 Thursday, July 18, 2013 Unknown
Debugging Tools for Windows (windbg) 8.59.20120910 842 Monday, September 10, 2012 Unknown
Debugging Tools for Windows (windbg) 8.59.20120909 488 Sunday, September 9, 2012 Unknown
Debugging Tools for Windows (windbg) 8.59 514 Sunday, September 9, 2012 Unknown

This package has no dependencies.

Discussion for the Debugging Tools for Windows (windbg) Package

Ground Rules:

  • This discussion is only about Debugging Tools for Windows (windbg) and the Debugging Tools for Windows (windbg) 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 Debugging Tools for Windows (windbg), 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