Skip to content
The Package Support Framework (PSF) is a kit for applying compatibility fixes to packaged desktop applications.
C++ C# Other
Branch: master
Clone or download
Latest commit 0274e05 Sep 14, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
Detours Breaking Change: Renaming fraemwork to align with functionality Sep 25, 2018
PsfLauncher Adding stating script wrapper Aug 27, 2019
PsfRunDll removed exception structure in favor throw at the point of the except… Jul 18, 2019
PsfRuntime Moving all PS logic into PsfPowershellScriptRunner Aug 20, 2019
PsfShimMonitor Updates Feb 21, 2019
fixups Fixed wide char errors in electron solution Jul 19, 2019
include removed exception structure in favor throw at the point of the except… Jul 18, 2019
samples/PSFSample Adding new test cert for the PSF Sample application Apr 11, 2019
tests Forgot to add the config.json fiel Aug 30, 2019
.gitignore Update for pre-release review Jul 5, 2018 Breaking Change: Renaming fraemwork to align with functionality Sep 25, 2018
CentennialFixups.sln Adding XSD. Apr 10, 2019
Common.Build.props Add MultiProcessorCompilation Nov 28, 2018
Common.props Reverting SDK back to RS1 May 14, 2019
Fixups.props Breaking Change: Renaming fraemwork to align with functionality Sep 25, 2018
LICENSE Initial commit Jun 7, 2018
MetadataSchema.xsd Removing unnecessary declerations Apr 11, 2019
Microsoft.PackageSupportFramework.nuspec Removing spacing Mar 25, 2019
Microsoft.PackageSupportFramework.targets Pointing PSFSample to newest NuGet package. Sep 26, 2018 Merge branch 'master' into develop Sep 14, 2019
SignConfig.xml Changing sign code to work with build system' Sep 12, 2019
buildall.cmd PR comments addressed Aug 14, 2019 Breaking Change: Renaming fraemwork to align with functionality Sep 25, 2018
readme.txt Breaking Change: Renaming fraemwork to align with functionality Sep 25, 2018
thirdparty.txt Update for pre-release review Jul 5, 2018

Package Support Framework

This project provides tools, libraries, documentation and samples for creating app-compat fixups to enable classic Win32 applications to be distributed and executed as packaged apps.


Check out our step by step guide, it will walk you through the main PSF workflows and provides the key documentation.

See also:


Code licensed under the MIT License.

Branch structure

Package Support Framework adopts a development and master branching style.


This branch represents the source in the most recent nuget package. The code in this branch is the most stable. Please do not fork off this branch for development.


This branch has the latest code. Keep in mind that there might be features in this branch that is not yet in master. Please make a private fork off this branch to make any contributions to Package Support Framework.


This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit

Submit your own fixup(s) to the community:

  1. Create a private fork for yourself
  2. Make your changes in your private branch
  3. For new files that you are adding include the following Copyright statement.
    // Copyright (c) #YOUR NAME#. All rights reserved.
    // Licensed under the MIT license. See LICENSE file in the project root for full license information.
  4. Create a pull request into 'fork:Microsoft/MSIX-PackageSupportFramework' 'base:develop'

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

Here is how you can contribute to the Package Support Framework:

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact with any additional questions or comments.

Script support

Scripts allow IT Pros to customize the app for the user environment dynamically. The scripts typically change registry keys or perform file modifications based on the machine or server configuration.

Each exe defined in the application manifest can have their own scripts. PSF allows one PowerShell script to be run before an exe runs, and one PowerShell script to be ran after the exe runs.

Prerequisite to allow scripts to run

In order to allow scripts to run you need to set the execution policy to unrestricted or RemoteSigned.

Run the one of the two following powershell commands to set the execution policy: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned or Set-ExecutionPolicy -ExecutionPolicy Unrestricted depending if you want the execution policy to be remoteSigned or unrestricted.

The execution policy needs to be set for both the 64-bit powershell executable and the 32-bit powershell executable. Make sure to open each version of powershell and run the command shown above.

Here are the locations of each executable.

  • If on a 64-bit computer
    • 64-bit: %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe
    • 32-bit: %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe
  • If on a 32-bit computer
    • 32-bit: %SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe

More information about PowerShell Execution Policy

How to enable scripts to run with PSF

In order to specify what scripts will run for each packaged exe you will need to modify the config.json file. To tell PSF to run a script before the execution of the packaged exe add a configuration item called "startScript". To tell PSF to run a script after the packaged exe finishes add a configuration item called "endScript".

Script configuration items

The following are the configuration items available for the scripts. The ending script ignores the following configuration items: waitForScriptToFinish, and stopOnScriptError.

Key name Value type Required? Default Description
scriptPath string Yes N/A The path to the script including the name and extension. The Path starts from the root directory of the application.
scriptArguments string No empty Space delimited argument list. The format is the same for a PowerShell script call. This string gets appended to scriptPath to make a valid PowerShell.exe call.
runInVirtualEnvironment boolean No true If the script should run in the same virtual environment that the packaged exe runs in.
runOnce boolean No true If the script should run once per user, per version.
showWindow boolean No false If the powershell window is shown.
waitForScriptToFinish boolean No true If the packaged exe should wait for the starting script to finish before starting.
timeout DWORD No INFINITE How long the script will be allowed to execute. If elapsed the script will be stopped.

Sample configuration

Here is a sample configuration using two different exes.

  "applications": [
      "id": "Sample",
      "executable": "Sample.exe",
      "workingDirectory": "",
      "stopOnScriptError": false,
		"scriptPath": "RunMePlease.ps1",
		"scriptArguments": "\\\"First argument\\\" secondArgument",
		"runInVirtualEnvironment": true,
		"showWindow": true,
		"waitForScriptToFinish": false
		"scriptPath": "RunMeAfter.ps1",
		"scriptArguments": "ThisIsMe.txt"
      "id": "CPPSample",
      "executable": "CPPSample.exe",
      "workingDirectory": "",
		"scriptPath": "CPPStart.ps1",
		"scriptArguments": "ThisIsMe.txt",
		"runInVirtualEnvironment": true
		"scriptPath": "CPPEnd.ps1",
		"scriptArguments": "ThisIsMe.txt",
    "runOnce": false
  "processes": [
    ...(taken out for brevity)

Enabling the app to exit if the starting script encounters an error.

The scripting change allows users to tell PSF to exit the application if the starting script fails. To do this, add the pair "stopOnScriptError": true to the application configuration (not the script configuration).

The combination of stopOnScriptError: true and waitForScriptToFinish: false is not supported

This is an illegal configuration combination and PSF will throw the error ERROR_BAD_CONFIGURATION.

Fixup Metadata

Each fixup and the PSF Launcher has a metadata file in xml format. Each file contains the following

  1. Version: The version of the PSF is in MAJOR.MINOR.PATCH format according to Sem Version 2
  2. Minimum Windows Platform the the minimum windows version required for the fixup or PSF Launcher.
  3. Description: Short description of the fixup.
  4. WhenToUse: Heuristics on when you should apply the fixup.

Additionally, we have the XSD for the metadata files. THe XSD is located in the solution folder.


Telemetry datapoint has been hooked to collect usage data and sends it to Microsoft to help improve our products and services. Read Microsoft's privacy statement to learn more. However, data will be collected only when the PSF binaries are used from Nuget package on Windows 10 devices and only if users have enabled collection of data. The Nuget package has binaries signed and will collect usage data from machine. When the binaries are built locally by cloning the repo or downloading the bits, then telemetry is not collected.

You can’t perform that action at this time.