Downloads of v 2.10.10:


Last Update:

18 Nov 2014

Package Maintainer(s):

Software Author(s):

  • John Bailey et al.




This is not the latest version of Pidgin available.

  • 1
  • 2
  • 3

2.10.10 | Updated: 18 Nov 2014



Downloads of v 2.10.10:


Software Author(s):

  • John Bailey et al.



  • 1
  • 2
  • 3
Pidgin 2.10.10

This is not the latest version of Pidgin available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

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 Pidgin, run the following command from the command line or from PowerShell:


To upgrade Pidgin, run the following command from the command line or from PowerShell:


To uninstall Pidgin, 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 pidgin -y --source="'INTERNAL REPO URL'" --version="'2.10.10'" [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 pidgin -y --source="'INTERNAL REPO URL'" --version="'2.10.10'" 

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

Exit $exitCode

- name: Install pidgin
    name: pidgin
    version: '2.10.10'
    state: present

See docs at

chocolatey_package 'pidgin' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.10.10'

See docs at

cChocoPackageInstaller pidgin
    Name     = "pidgin"
    Version  = "2.10.10"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'pidgin':
  ensure   => '2.10.10',
  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.

This package was approved by moderator purity on 20 Nov 2014.


Pidgin is a chat program which lets you log in to accounts on multiple chat networks simultaneously. This means that you can be chatting with friends on MSN, talking to a friend on Google Talk, and sitting in a Yahoo chat room all at the same time. Pidgin is compatible with the following chat networks out of the box: AIM, ICQ, Google Talk, Jabber/XMPP, MSN Messenger, Yahoo!, Bonjour, Gadu-Gadu, IRC, Novell GroupWise Messenger, Lotus Sametime, SILC, SIMPLE, MXit, and Zephyr. It can support many more with plugins. See for more information.

$package_name = 'Pidgin'
$file_type = 'exe'
$silent_args = '/S'
$url = ''
Stop-Process -ProcessName pidgin*

Install-ChocolateyPackage $package_name $file_type $silent_args $url
$package_name = 'Pidgin'
$installer_type = 'EXE'
$silent_args = '/S'
$valid_exit_codes = @(0)

$un_folder = "Pidgin"
$un_file = "pidgin-uninst.exe"

try {
    $64_bit = 0
    if (Test-Path "${Env:ProgramFiles(x86)}\$un_folder\$un_file") {
        $un_path = "${Env:ProgramFiles(x86)}\$un_folder\$un_file"
    } else {
	   $64_bit = 1
        $un_path = "${Env:ProgramFiles}\$un_folder\$un_file"
    Uninstall-ChocolateyPackage $package_name $installer_type $silent_args $un_path -ValidExitCodes $valid_exit_codes
} catch {
  Write-ChocolateyFailure $package_name $($_.Exception.Message)

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
Pidgin 2.14.7 2055 Friday, September 17, 2021 Approved
Pidgin 2.14.6 2368 Friday, July 16, 2021 Approved
Pidgin 2.14.5 2175 Friday, June 4, 2021 Approved
Pidgin 2.14.4 1766 Thursday, May 6, 2021 Approved
Pidgin 2.14.3 35 Thursday, May 6, 2021 Approved
Pidgin 2.14.2 27 Thursday, May 6, 2021 Approved
Pidgin 6757 Thursday, June 25, 2020 Approved
Pidgin 2.13.0 43585 Thursday, July 12, 2018 Approved

Pidgin 2.10.10 contains important security updates.

This package has no dependencies.

Discussion for the Pidgin Package

Ground Rules:

  • This discussion is only about Pidgin and the Pidgin 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 Pidgin, 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