Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand



Downloads of v 2023.12.10:


Last Update:

26 Dec 2023

Package Maintainer(s):

Software Author(s):

  • mpv team


mpv video media player multimedia admin

mpv (Install)

  • 1
  • 2
  • 3

2023.12.10 | Updated: 26 Dec 2023



Downloads of v 2023.12.10:



Software Author(s):

  • mpv team

mpv (Install) 2023.12.10

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install mpv (Install), run the following command from the command line or from PowerShell:


To upgrade mpv (Install), run the following command from the command line or from PowerShell:


To uninstall mpv (Install), run the following command from the command line or from PowerShell:


Deployment Method:


This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

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 https://community.chocolatey.org/api/v2/. 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 mpv.install -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 mpv.install -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 mpv.install
    name: mpv.install
    version: '2023.12.10'
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

chocolatey_package 'mpv.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2023.12.10'

See docs at https://docs.chef.io/resource_chocolatey_package.html.

cChocoPackageInstaller mpv.install
    Name     = "mpv.install"
    Version  = "2023.12.10"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

package { 'mpv.install':
  ensure   => '2023.12.10',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. 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.

Package Approved

This package was approved as a trusted package on 21 Jul 2024.


Maintainer Note

What's the difference between this package and mpvio? None, but this package is stuck following a now defunct version scheme of mpv.
Why does the mpv package use a different version than the official project? Long ago, the Windows builds of mpv were provided by a contributor who made Windows specific changes to mpv. Since the chocolatey package was following that specific build, it made sense (at the time) to mirror that build's version scheme.


a free, open source, and cross-platform media player


mpv is a free (as in freedom) media player for the command line. It supports a wide variety of media file formats, audio and video codecs, and subtitle types.


Powerful scripting capabilities can make the player do almost anything. There is a large selection of user scripts on the wiki.

On Screen Controller

While mpv strives for minimalism and provides no real GUI, it has a small controller on top of the video for basic control.

High quality video output

mpv has an OpenGL, Vulkan, and D3D11 based video output that is capable of many features loved by videophiles, such as video scaling with popular high quality algorithms, color management, frame timing, interpolation, HDR, and more.

GPU video decoding

mpv can leverage most hardware decoding APIs on all platforms. Hardware decoding can be enabled at runtime on demand.


A straightforward C API was designed from the ground up to make mpv usable as a library and facilitate easy integration into other applications.

Active development

mpv is under active development, focusing on code refactoring and cleanups as well as adding features. Want a feature? Post a patch or request it!

md5: 134FB262B73D73DEC2D0EEBF219027D7 | sha1: E9F733515324BA90CE2EFC6CFAC905C3AF37AB1E | sha256: 2AA273E38B6F04936FDF005B7181CDF9A2FE72027B35FD8215E21FF6A5166C17 | sha512: F203E39F5978C47352DA4F3358E80C3E71F3F01DB63EC870F5DDDB17F1DADCC0737EE2BCAB16A049AFC5857C58971FA55F623603F4D2ABA4E343233F28D58F88
md5: 9F25067777B98FB63364498A727380A3 | sha1: 85EE75EB621839D25FF84472DEE147AF762A379D | sha256: 105A2E84C1FD4527D201C60F881A37852BBBEE42C73398F92CA929BD089BF05B | sha512: 18B793E11683AB9BB3B6C2274606F583DB3730431F537330F2E0403AC5D980C57E102C2BE924493008E5249F1F803EFDE5D5FFF49329BF1F467D37B68C040824
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The embedded software have been downloaded from the listed download
location on <https://sourceforge.net/projects/mpv-player-windows/files/stable/> and <https://github.com/rossy/mpv-install>
and can be verified by doing the following:

1. Go to

	x32: https://sourceforge.net/projects/mpv-player-windows/files/release/mpv-0.37.0-i686.7z
	x64: https://sourceforge.net/projects/mpv-player-windows/files/release/mpv-0.37.0-x86_64.7z
	zip: https://github.com/rossy/mpv-install/archive/master.zip

	to download the installer.

2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'

3. The checksums should match the following:

  checksumType: sha256
  checksum32: BF4E1EF4A1FBC9CBDB76156B32A5C58CF6AECC36A04E6B83548B9F03A1AC0037
  checksum64: 2AA273E38B6F04936FDF005B7181CDF9A2FE72027B35FD8215E21FF6A5166C17
  checksumzp: 105A2E84C1FD4527D201C60F881A37852BBBEE42C73398F92CA929BD089BF05B

The files 'LICENSE.mpv-install.txt' 'LICENSE.txt' have been obtained from <https://raw.githubusercontent.com/rossy/mpv-install/master/COPYING>
$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
  packageName = 'mpv.install'
  file        = gi "$toolsDir\*_x32.7z"
  file64      = gi "$toolsDir\*_x64.7z"
  destination = "$toolsDir"

If ( Get-Item $toolsDir\doc\mpv.html -ea 0) {
  Write-Warning 'For technical reasons, please uninstall then reinstall mpv.'
  Write-Warning 'cuninst mpv.install; cinst mpv.install'
  Write-Error 'The builds provided by this package have changed and mpv needs to be reinstalled.'

Get-ChocolateyUnzip @packageArgs
Get-ChocolateyUnzip -file "$toolsDir\rossy.zip" -destination $toolsDir
Move-Item "$toolsDir\mpv-install-master\*" $toolsDir -Force
Remove-Item "$toolsDir\mpv-install-master"
Start-ChocolateyProcessAsAdmin -Statements "/K $toolsDir\mpv-install.bat /u" -ExeToRun "$env:SystemRoot\System32\cmd.exe" -Elevated -validExitCodes '0'
Remove-Item -force "$toolsDir\*.zip","$toolsDir\*.7z" -ea 0

# mpv can't be shimmed, the shim doesn't work with mpv.com
# as of 2016.01.18, there is a dll dependency, so mpv can't be hardlinked to chocolatey\bin
# adding to PATH until chocolatey implements a /usr/lib equivalent
$pathType = 'User'
If ( Test-ProcessAdminRights ) { $pathType = 'Machine' }
Install-ChocolateyPath $toolsDir $pathType
Copyright © 2015, James Ross-Gowan <[email protected]>

Permission to use, copy, modify, and/or distribute this software for any
purpose with or without fee is hereby granted, provided that the above
copyright notice and this permission notice appear in all copies.

mpv is a fork of mplayer2, which is a fork of MPlayer.

mpv as a whole is licensed under the GNU General Public License GPL version 2
or later (called GPLv2+ in this document, see LICENSE.GPL for full license
text) by default, or the GNU Lesser General Public License LGPL version 2 or
later (LGPLv2.1+ in this document, see LICENSE.LGPL for full license text) if
built with the --enable-lgpl configure switch.

Most source files are LGPLv2.1+ or GPLv2+, but some files are available under
more liberal licenses, such as BSD, MIT, ISC, and possibly others. Look at the
copyright header of each source file, and grep the sources for "Copyright" if
you need to know details. C source files without Copyright notice are usually
licensed as LGPLv2.1+. Also see the list of files with specific licenses below
(not all files can have a standard license header).

All new contributions must be LGPLv2.1+ licensed. Using a more liberal license
compatible to LGPLv2.1+ is also ok.

Changes done to GPL code must come with the implicit/explicit agreement that the
project can relicense the changes to LGPLv2.1+ at a later point without asking
the contributor. This is a safeguard for making potential relicensing of
remaining GPL code to LGPLv2.1+ easier.

See DOCS/contribute.md for binding rules wrt. licensing for contributions.

For information about authors and contributors, consult the git log, which
contains the complete SVN and CVS history as well.

"v2.1+" in this context means "version 2.1 or later".

Some libraries are GPLv2+ or GPLv3+ only. Building mpv with Samba support makes
it GPLv3+.

mpv can be built as LGPLv2.1+ with the --enable-lgpl configure option. To add
a LGPL mode to mpv, MPlayer code had to be relicensed from GPLv2+ to LGPLv2.1+
by asking the MPlayer authors for permission. Since permission could not be
obtained from everyone, LGPL mode disables the following features, some of
them quite central:
- Linux X11 video output
- BSD audio output via OSS
- NVIDIA/Linux hardware decoding (vdpau, although nvdec usually works)
- Linux TV input
- minor features: jack, DVD, CDDA, SMB, CACA, legacy direct3d VO
Some of these will be fixed in the future. The intended use for LGPL mode is
with libmpv, and currently it's not recommended to build mpv CLI in LGPL mode
at all.

The following files are still GPL only (--enable-lgpl disables them):

    audio/out/ao_jack.c             will stay GPL
    audio/out/ao_oss.c              will stay GPL
    stream/dvb*                     must stay GPL
    stream/stream_cdda.c            unknown
    stream/stream_dvb.*             must stay GPL
    stream/stream_dvdnav.c          unknown
    video/out/vo_caca.c             unknown
    video/out/vo_direct3d.c         unknown
    video/out/vo_vaapi.c            probably impossible (some company's code)
    video/out/vo_vdpau.c            probably impossible (nVidia's code)
    video/out/vo_x11.c              probably impossible
    video/out/vo_xv.c               probably impossible
    video/out/x11_common.*          probably impossible
    video/vdpau.c                   hard (GPL-only parts must be ifdefed)
    video/vdpau.h                   unknown
    video/vdpau_mixer.*             actual code must be rewritten
    DOCS/man/                       GPLv2+
    bootstrap.py                    unknown license, probably GPLv2+ or LGPLv2+
    etc/mplayer-input.conf          unknown license, probably GPLv2+
    mpv.desktop                     unknown license, probably GPLv2+
    etc/restore-old-bindings.conf   unknown license, probably GPLv2+

None of the cases listed above affect the final binary if it's built as
LGPL. Linked libraries still can affect the final license (for example if
FFmpeg was built as GPL).
md5: D9B7D82D88722C1DB6260F8F43B5C599 | sha1: A4E138669B25098B10D27D6AA959361AC49157E8 | sha256: BF4E1EF4A1FBC9CBDB76156B32A5C58CF6AECC36A04E6B83548B9F03A1AC0037 | sha512: AD26B77869B1D89C5438EE52FF37566C2BAEA24ADD5207CC666151CA291CC1AB571C9DFB29639E44B01A87A1BE72D0F5B3F1C36C61E848AD63CC5D2950F7D827
$packageName = 'mpv.install'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

# Remove from Machine PATH
$machinePath = Get-EnvironmentVariable -Name 'PATH' -Scope Machine
if ( $machinePath.Contains($toolsDir) ) {
  $cleanMachinePath = $([Environment]::GetEnvironmentVariable("PATH",[EnvironmentVariableTarget]::Machine)).Replace("$toolsDir;",'')
  [Environment]::SetEnvironmentVariable("PATH", "$cleanMachinePath", [EnvironmentVariableTarget]::Machine)
# Remove from User PATH
$userPath = Get-EnvironmentVariable -Name 'PATH' -Scope User
if ( $userPath.Contains($toolsDir) ) {
  $cleanUserPath = $([Environment]::GetEnvironmentVariable("PATH", [EnvironmentVariableTarget]::User)).Replace("$toolsDir;",'')
   [Environment]::SetEnvironmentVariable("PATH", "$cleanUserPath", [EnvironmentVariableTarget]::User)

Start-ChocolateyProcessAsAdmin "/K $toolsDir\mpv-uninstall.bat /u" "$env:SystemRoot\System32\cmd.exe" -validExitCodes '0'

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
mpv (Install) 2023.01.28 35846 Monday, March 27, 2023 Approved
mpv (Install) 2022.11.14 17535 Friday, November 18, 2022 Approved
mpv (Install) 2021.11.01 37621 Sunday, November 7, 2021 Approved
mpv (Install) 2020.12.06 32627 Friday, January 8, 2021 Approved
mpv (Install) 2020.1.27 22791 Tuesday, March 17, 2020 Approved
mpv (Install) 2019.12.29 5838 Thursday, January 23, 2020 Approved
mpv (Install) 2019.11.02 7743 Monday, November 11, 2019 Approved
mpv (Install) 2018.10.02 10745 Wednesday, October 3, 2018 Approved
mpv (Install) 2018.07.31 2610 Wednesday, August 1, 2018 Approved
mpv (Install) 2018.07.22 1877 Tuesday, July 24, 2018 Approved
mpv (Install) 2017.12.25 4761 Saturday, December 30, 2017 Approved
mpv (Install) 2017.09.13 3067 Wednesday, September 13, 2017 Approved
mpv (Install) 2017.07.18 1987 Thursday, July 20, 2017 Approved
mpv (Install) 2017.04.23 1959 Wednesday, April 26, 2017 Approved
mpv (Install) 2017.02.12 1675 Tuesday, February 14, 2017 Approved
mpv (Install) 2016.12.25 608 Monday, December 26, 2016 Approved
mpv (Install) 2016.11.20 577 Wednesday, November 23, 2016 Approved
mpv (Install) 2016.10.20 588 Friday, October 21, 2016 Approved
mpv (Install) 2016.08.26 558 Wednesday, September 7, 2016 Approved
mpv (Install) 2016.08.16 571 Thursday, August 18, 2016 Approved
mpv (Install) 2016.07.10 542 Monday, July 11, 2016 Approved
mpv (Install) 2016.06.25 448 Saturday, June 25, 2016 Approved
mpv (Install) 2016.04.11.1 367 Monday, May 9, 2016 Approved
mpv (Install) 2016.04.11 496 Friday, April 15, 2016 Approved
mpv (Install) 2016.02.29 528 Monday, February 29, 2016 Approved
mpv (Install) 2016.01.18 504 Wednesday, January 20, 2016 Approved
mpv (Install) 2015.12.11 489 Saturday, December 26, 2015 Approved

This package has no dependencies.

Discussion for the mpv (Install) Package

Ground Rules:

  • This discussion is only about mpv (Install) and the mpv (Install) 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 mpv (Install), 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