Downloads of v 1.3.4:


Last Update:

10 Oct 2014

Package Maintainer(s):

Software Author(s):

  • Peter Pawlowski


foobar2000 media player admin


This is not the latest version of foobar2000 available.

1.3.4 | Updated: 10 Oct 2014



Downloads of v 1.3.4:



Software Author(s):

  • Peter Pawlowski

foobar2000 1.3.4

This is not the latest version of foobar2000 available.

All Checks are Unknown

2 Test of Unknown Status

Validation Testing Unknown

Verification Testing Unknown

To install foobar2000, run the following command from the command line or from PowerShell:


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


To uninstall foobar2000, 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 foobar2000 -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 foobar2000 -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 foobar2000 installed
    name: foobar2000
    state: present
    version: 1.3.4
    source: STEP 3 URL

See docs at

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

chocolatey_package 'foobar2000' do
  action    :install
  version  '1.3.4'
  source   'STEP 3 URL'

See docs at

    Name: foobar2000,
    Version: 1.3.4,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller foobar2000
   Name     = 'foobar2000'
   Ensure   = 'Present'
   Version  = '1.3.4'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'foobar2000':
  provider => 'chocolatey',
  ensure   => '1.3.4',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install foobar2000 version="1.3.4" 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 mwrock on 26 Oct 2014.


foobar2000 is an advanced freeware audio player for the Windows platform. Some of the basic features include full unicode support, ReplayGain support and native support for several popular audio formats.

try {

    $packageName = "foobar2000"
    $fileType = "exe"
    $silentArgs = "/S"
    $pwd = "$(split-path -parent $MyInvocation.MyCommand.Definition)"

	Import-Module "$($pwd)\Get-FilenameFromRegex.ps1"
	# Why does an import failure on this module not throw an error?

	$url1 = Get-FilenameFromRegex "" 'download_foobar2000/([\d]+)/">Foobar2000 1.3.4<' '$1/'

    Write-Host "Found URL which contains the download URL 1: $url1"

    $url2 = Get-FilenameFromRegex "$url1" 'download_foobar2000/download/([\w\d]+)/' '$1/'
    Write-Host "Found URL which contains the download URL 2: $url2"

	$url3 = Get-FilenameFromRegex "$url2" '/download/file/([\w\d]+)/' '$1/'
	Write-Host "Found download URL: $url3"

	Install-ChocolateyPackage $packageName $fileType $silentArgs $url3

    Write-ChocolateySuccess $name
} catch {
  Write-ChocolateyFailure $name $($_.Exception.Message)
# Redsandro - I will just include the required module in the package as long as it is not merged with Chocolatey

# Some files have a changing element/hash in the download path, making an automated download harder.
# This file gets the correct download url from a download page with a regular expression.
# Good for e.g. Foobar2000, Rename Master, etc
# Usage: Get-FilenameFromRegex download_page find replace
# Examples:
# Get-FilenameFromRegex "" '/cms/file.php\?f=userupload/8/files/;c=([\w\d]+)' '$1/userupload/8/files/'
# Remember to escape regex characters, like the question mark in the querystring

function Get-FilenameFromRegex {

    try {

        ## Example # $source_url = ""
        ## Example # $find = '/cms/file.php\?f=userupload/8/files/;c=([\w\d]+)'
        ## Example # $replace = '$1/userupload/8/files/'

        # Download and open download page
        $tempfile = "$env:TEMP\chocolatey_temp_download.html"
        $wc = new-object
        $wc.UseDefaultCredentials = $true
        $wc.downloadfile($source_url, $tempfile)
        $source = Get-Content $tempfile

        $nothing = ''+$source -cmatch $find # Get the matches, prevent output
        # Replace Match-references with previous matches: $1 $2 -> $matches[1] $matches[2]
        #$download_url = $replace -creplace "\$`(\d+)",$matches[$1]
        # This one is not working :(
        # I have a temporary fix that only allows ONE match. However, in most cases we only need one match.
        $download_url = $replace -creplace "\$`(\d+)",$matches[1]
        Remove-Item $tempfile

        return $download_url

    } catch {
        $errorMessage = "Could not get Regex from download page."
        Write-Error $errorMessage
        throw $errorMessage

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
foobar2000 1.6.1 4925 Saturday, September 26, 2020 Approved
foobar2000 1.6 1865 Tuesday, September 22, 2020 Approved
foobar2000 1.5.5 7860 Tuesday, June 30, 2020 Approved
foobar2000 1.5.4 6211 Tuesday, May 12, 2020 Approved
foobar2000 1.5.3 5630 Wednesday, April 1, 2020 Approved
foobar2000 5311 Wednesday, February 26, 2020 Approved
foobar2000 1.5.2 2202 Wednesday, February 19, 2020 Approved
foobar2000 1.5.1 5300 Tuesday, December 31, 2019 Approved
foobar2000 1.5.0 3973 Thursday, December 5, 2019 Approved

This package has no dependencies.

Discussion for the foobar2000 Package

Ground Rules:

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