QMPlay2 is distributed for Windows both as a conventional setup program and as a portable archive. The two builds contain the identical player, so the choice depends chiefly on how you prefer to manage your software.
This guide covers both options, the settings worth reviewing at the outset, and a handful of control files that govern how the player starts.
Choosing the right build
- Installer: it adds Start menu entries, registers file types and manages updates. This suits a single computer that you use daily.
- Portable archive (.7z): it runs from any folder or USB drive and stores its settings alongside the program. This suits shared or managed machines.
Current Windows builds are 64-bit. Release 26.08.02 is the most recent version listed in the project changelog.
Installing with the setup program
- Download the Windows installer from the official releases page on GitHub.
- Run the file. Should SmartScreen display a prompt, confirm that the publisher and file name correspond to what you downloaded, then proceed.
- Select an installation folder. The default location beneath Program Files is suitable for most users.
- Complete the wizard and open QMPlay2 from the Start menu.
On first launch the player may ask whether to enable automatic updates. You can revise that choice later within the settings.
Using the portable build
Extract the .7z archive into a folder to which you have write access, using 7-Zip or a comparable tool, then run QMPlay2.exe.
To keep the settings within that folder, create an empty file named portable beside QMPlay2.exe. Without it, the settings are written to your user profile, as they are for the installed version.
A second empty file, noautoupdates, prevents the player from enabling automatic updates on its first run.
Setting file associations
QMPlay2 includes a file-association module. Open Options → Modules settings, select the file-association entry and tick the extensions you wish to open with the player.
Alternatively, right-click any media file in Explorer, choose Open with, and set QMPlay2 as the default application.
Settings worth reviewing first
- Video output: both Vulkan and OpenGL are available. If you encounter tearing or a black screen, try the alternative.
- Hardware decoding: disabled by default. Consult the hardware-acceleration guide to enable it.
- Single instance: under Settings → General settings, “Allow only one instance” causes new files to open in the running window.
Keeping YouTube playback working
YouTube support depends on the external yt-dlp tool, which QMPlay2 downloads on your behalf. Certain antivirus or firewall utilities block it.
If online videos fail to load, permit yt-dlp within your security software and allow the player to run external programs.
Removing or relocating the player
Remove the installed version from Settings → Apps in Windows. For the portable build, simply delete its folder. Your media files remain untouched in either case.
If the installation fails
- Parse error: the download did not complete. Delete the file and download it again.
- App not installed: remove any earlier copy first, then install the new file.
- Blocked by security software: your computer has scanned the file. Review the warning before deciding to continue.
Before you choose an installation method
QMPlay2 should be installed with a clear understanding of what the downloaded file contains. A source archive contains the files used to build the application. It is not the same as a Windows setup program and will not install the player when you extract it. For a normal installation, use a Windows executable package. A portable package is also a ready-made application, but it is unpacked into a folder rather than registered through a conventional setup wizard.
Check the computer architecture before choosing a package. A 64-bit application needs a compatible version of Windows; changing the folder name does not make an incompatible executable work. Also check that the file has finished downloading before trying to open it. If the archive cannot be extracted or the installer reports that it is incomplete, compare the downloaded size with the package information and obtain a fresh copy. Keep the original package until the player launches successfully.
A careful first installation
Save your work in other applications before starting setup. Choose a location that makes sense for a permanent installation, and review the options offered by the installer. If Windows asks for permission to make system changes, check the application and the location of the installer. Do not disable security software simply because an unfamiliar file cannot run. Confirm the package source and investigate the warning before continuing.
After setup finishes, launch QMPlay2 from its installed shortcut. Begin with a small local media file that you already know plays correctly. This first test checks the installed application, the audio output and the video window without involving an internet service. Check that pause, resume, seeking and volume adjustment work. Once that baseline is established, try a second file of another type. A successful local test makes it easier to separate later network problems from installation problems.
Keeping a portable folder organised
A portable installation is easiest to manage when it has its own folder. Extract the complete archive instead of opening the executable inside an archive viewer. The executable may depend on libraries and other files beside it, so moving only the application file to the desktop can prevent it from starting. Create a shortcut to the executable if you want quick access while keeping the extracted files together.
Choose a folder where your Windows account can write settings when you use the portable control file described above. A protected system directory is usually an inconvenient choice. Keep personal videos and music outside the application folder so that replacing the player does not mix software files with your library. Before moving the folder to another machine, close the player and copy its settings together with the application. Saved references to media on the original computer may need to be corrected.
Checking picture and sound after setup
Use ordinary playback settings for the first test. Select the speakers or headphones you intend to use, then check both the Windows volume and the player volume. A muted application can look like a missing codec problem even when decoding is working correctly. If headphones are connected after the player starts, verify that Windows and the application are using the same output device before changing unrelated settings.
For video, begin with the default output and a normal-sized window. A black picture with working sound is a different symptom from an application that never starts. Record which files show the problem and whether another file works. Try one output or decoder adjustment at a time, then replay the same short passage. Avoid making several changes together: even if playback improves, you will not know which change helped. Once local playback is reliable, configure hardware decoding if your graphics hardware supports your files.
File associations without confusion
A file association tells Windows which application to launch when a file is opened. It does not convert the media or alter its contents. Choose only the media types you want QMPlay2 to handle, especially if another player remains installed. Windows may present its own default-app confirmation after an application requests an association, so check the result by closing the player and opening a sample file from Explorer.
If double-clicking still opens another program, use Windows default-app settings or the Open with dialog to select the intended player. Test one extension first, such as an audio file you recognise, before changing many formats. When a file opens in QMPlay2 but fails to play, the association is already working; investigate the media file and playback support instead. Separating these two cases avoids reinstalling the application to solve a Windows preference that can be changed independently.
Updating and removing the player carefully
Before updating, close every running instance and note any custom settings that matter to you. Keep a backup of configuration files if you have spent time adjusting outputs, keyboard controls or module preferences. For a portable build, do not copy new files over a player that is still running. Extracting an update into a separate folder first also gives you a way to compare behaviour before replacing a working setup.
If you uninstall an installed build, use the Windows application removal interface. With a portable build, remove the extracted application folder only after checking that it contains no personal media or backups. Application removal and configuration removal can be separate operations, so do not assume that every preference has disappeared. If you are troubleshooting a startup problem, record the error message and installation method before changing anything else. That information is more useful than repeatedly reinstalling the same package without a comparison test.
A practical installation checklist
Finish the installation by checking the tasks you actually need every day. Open an audio file, open a video, switch between windowed and full-screen playback, and confirm that the playlist displays the expected items. If you use subtitles, test one local subtitle file. If you use an external display, connect it and check sound routing before relying on the setup for a presentation or a film.
Keep the working setup simple while you learn the interface. Additional modules, online playback and advanced output settings can be tested afterwards. Note the application version and whether you installed it or unpacked it; that makes future troubleshooting easier. A brief written record of the selected output and any deliberate changes also helps when you move to another computer. The goal is a repeatable installation that can be checked with a few familiar files, rather than settings changed without a clear reason.
FAQs
Does the source ZIP install QMPlay2 on Windows? No. A source ZIP is intended for building the software and contains project files. For ordinary use, choose a ready-made Windows installer or portable application package. Extracting source code does not produce an installed player, and a missing executable in that archive is not an extraction error.
Which is better, the installer or portable version? Choose the installer for a conventional setup managed through Windows. Choose portable packaging when you want to keep the application in a folder you manage yourself. Both choices still need a compatible system. Portable packaging does not automatically mean every setting or media reference will work unchanged on another computer.
Why does the portable executable fail after I move it? Check whether you moved only the executable rather than the complete extracted folder. Application libraries and resources may need to remain beside it. Restore the complete package in one location and try again before changing Windows settings. Also confirm that the package was fully extracted and matches your computer architecture.
Do I have to make it the default player? No. You can launch QMPlay2 and open files from within it while leaving your existing Windows defaults in place. Change associations only for the formats you want it to handle. If an association does not take effect, check the Windows default-app controls rather than assuming playback itself is broken.
Why does local playback work but online playback fail? Local playback and online extraction use different parts of the setup. If a familiar local file plays, the basic installation is functioning. Online playback may depend on network availability, a supported service and the external extraction tool. Investigate those separately instead of immediately removing a working installation.
Will removing the application delete my videos? Media stored in separate personal folders is independent of the player. However, deleting an entire portable folder also deletes any personal files you put inside it. Review that folder before removing it, and keep media libraries and application files separate so that future updates and removal remain straightforward.
Conclusion
QMPlay2 installation on Windows is most predictable when you choose the correct package, keep its files together and test local playback before adding more complicated sources. Decide whether a conventional installer or a portable folder fits the way you maintain software, then verify picture, sound and file opening with familiar media. Keep a record of your settings and preserve any configuration you need before updating. If something fails, describe the exact symptom and change one variable at a time. This gives you a dependable player setup and a useful starting point for troubleshooting without unnecessary reinstalls.