Windows Media Player 11 SDK Windows Media Player Setup Command-line Parameters
.gif)
| Previous | Next |
Windows Media Player Setup Command-line Parameters
The setup programs for Windows Media Player 11 are named wmp11-windowsxp-x86-localeId.exe and wmp11-windowsxp-x64-localeId.exe, where localeId is a locale identifier.
The setup program for Windows Media Player 10 is named MP10Setup.exe. It is supported on Windows XP operating systems only.
The setup programs for Windows Media Player 9 Series are named MPSetup.exe and MPSetupXP.exe.
- MPSetup.exe is supported on Windows 98 Second Edition, Windows Millennium Edition, Windows 2000, and Windows XP operating systems.
- MPSetupXP.exe is supported only on Windows XP.
MPSetup.exe is a superset of the MPSetupXP.exe setup program. It contains files that are needed by operating systems released before Windows XP. MPSetup.exe is functionally equivalent to MPSetupXP.exe when run on Windows XP, but the setup program file size is larger because it has not been optimized for installation on Windows XP operating systems.
Here are some of the commonly used command-line parameters for performing an unattended or quiet mode installation. The examples use MP10Setup.exe. You should substitute the appropriate setup program name for your application.
For unattended installation with no UI and no restart or restart prompt:
We recommend using the following command line for most redistribution scenarios.
MP10Setup.exe /q:A /c:"setup_wm.exe /Q /R:N /P:#e"
This is the standard command line that should usually be used to perform an unattended setup. This is the recommended default command line to use for most redistribution scenarios.
To prevent library migration:
MP10Setup.exe /q:A /c:"setup_wm.exe /Q /R:N /NoMigrate /P:#e"
To cache the installation package for later Windows upgrade migration:
MP10Setup.exe /q:A /R:N /c:"setup_wm.exe /Q /R:N /P:#e"
The /P:#e parameter specifies that the Windows Media Player installation package should be cached during Windows Media Player setup. This command is used to handle future upgrades of the operating system. This command should only be omitted by corporate IT administrators.
The only case where /P:#e should not be included on the command line is when you own the target system and know that the target system will never be upgraded to a later operating system. For example, if you are installing Windows Media Player 9 Series on Windows 2000 and the computer may someday be upgraded to Windows XP, you must use /P:#e on the command line. Otherwise, after the Windows XP installation, the Windows Media Player files will be overwritten with the files for Windows Media Player for Windows XP.
Note that the /P:#e parameter is not required for Windows Media Player 10 setup.
To create a nested system restore point:
/NestedRestore
Use this if your application creates a system restore point to nest the Windows Media Player restore point within your application restore point.
To disallow the creation of a system restore point:
/DisallowSystemRestore
This flag will disable the creation of a system restore point. Under most circumstances this flag should not be used with general software redistribution scenarios. This should be used only when you can make an explicit choice on behalf of the end user not to support the rollback of the Windows Media Player files to an earlier version of the Player. This flag should be used only in a corporate deployment or original equipment manufacturer (OEM) installation scenario.
To set the initial active online store:
See Setup Command-line Parameters for Online Stores.
Notes
- The command-line parameters are case-sensitive.
- When suppressing the restart prompt, you must check the InstallResult registry key and handle restart notification in the calling setup application.
- Windows Media Player 9 Series or later will also install the Windows Media Format runtime, so there is no need to include both the Windows Media Player distribution package and the Windows Media Format runtime distribution package in the same software redistribution package. Therefore, if you include MPSetup.exe or MPSetupXP.exe in your installation, you do not need to include WMFdist.exe.
See Also
| Previous | Next |