Check the current package requirements
The official manual lists Windows and .NET Desktop Runtime requirements and distinguishes stable, beta, portable and setup routes. Read the current requirements for the intended release before installing. Keep the package’s source and version with your setup notes.
A portable copy and an installed copy can coexist, so verify which executable actually launches. For a hypothetical two-copy setup, editing one folder’s configuration while opening the other copy can make a correct change appear ineffective. Identify the active copy before troubleshooting the setting itself. If you launch through a shortcut, inspect where it points before editing the configuration.
Configure the relevant layer
mpv.net’s manual separates configuration folders, input/context menus and frontend-specific options from mpv behaviour. Use the documented route for the intended action. Back up existing configuration before importing a larger collection of custom commands or scripts.
Start with one permitted local item and a small change that can be reversed. Confirm that normal playback still works before adding optional integrations. A player supporting an internet-access integration does not make every website or protected video a permitted direct source.
Treat file associations as a Windows choice
The manual describes registering associations through setup and notes that Windows may still need its default-app selection changed. A successful player installation and the application chosen when double-clicking a file are separate observations. Check both if another player keeps opening.
For support, state the active executable, release type, Windows version and whether the failure concerns launching, a menu command or media playback. Redact private media paths. This reference does not run an installer, alter defaults or verify a subscription; it explains how to identify the appropriate configuration scope.