The corollary argument '-preserve' will be used to preserve files if the default setting has been modified. An additional argument '-purge' will be added for the uninstall scenario to remove all files and subsequently the directory if the user wishes. Some portable applications generate or consume other files. If no command value is provided, then the entry will use the filename of the exe.

Portable / standalone executables should have their “command” value specified so the Windows Package Manager can determine the default value to use when creating a new entry in the 'App Paths' registry during installation.

To have the upgrade scenario honor the custom name, this information should be recorded in the installed packages data store. In that vein, a '-rename' argument should be added so the user can choose a value they prefer. The installation instructions suggest renaming the file after it has been downloaded. Some packages like GitLab Runner have a file name including extra metadata (gitlab-runner-windows-386.exe). Users should be able to specify the location for where the program is “installed” on their machine with the “-location” argument. Notable concerns include the location of the package, creating or updating an entry in Windows Apps & Features. When one of these packages is encountered, there are several aspects to “installing” these packages and supporting the “upgrade” behavior. The installer type “portable” will be added to the enumerated list of installer types to support these types of packages. Just because an installer doesn't exist for a particular package doesn't mean you shouldn't be able to install it with the Windows Package Manager. This specification describes how these types of programs will be treated as 'packages' by the Windows Package Manager. Several packages do not have an installer.

Advanced installer portable