MSIX Values: Introduction to Package Support Framework (PSF)

While MSIX provides a modern, secure packaging model for Windows applications, compatibility with existing Win32 apps is a common concern. Many of these applications weren’t designed for containerized execution. The Package Support Framework (PSF) bridges this gap, enabling Win32 apps to run successfully within an MSIX package.

Running Win32 Apps

MSIX enforces a more isolated and predictable runtime. That delivers cleaner installs, safer upgrades, and better manageability — but it also restricts behaviors common to legacy installers and apps. Typical constraints include:

• Writes to the installation directory or current working directory are blocked or redirected.
• Hard-coded paths, first-run installer actions, and helper processes that rely on system-wide state can fail at runtime.

From an IT perspective that can look like a showstopper… until you apply the right compatibility layer.

What Package Support Framework (PSF) is, and How it Helps

The Package Support Framework (PSF) is an open-source toolkit from Microsoft that makes many Win32 apps work correctly inside MSIX without changing the app binary. PSF is built on Microsoft Detours technology and works by intercepting specific API calls at runtime and routing them to MSIX-friendly locations or behaviors.

How PSF Works

• MSIX replaces the app’s original EXE with the PSF Launcher.
• The Launcher reads a package configuration file (config.json) that lists one or more “fixups.”
• Each fixup is a small shim that intercepts targeted API calls (file I/O, environment lookups, process launches) and applies a runtime redirect or modification.
• The result: the app runs unchanged, but its read/write operations and environment are routed to locations compatible with MSIX.

For more detailed documentation on how PSF works, you refer to Microsoft’s documentation here.

Common Fixup Scenarios

• File redirection: redirect writes from Program Files to a per-user or package-local folder.
• Path remapping: rewrite hard-coded file paths so the app finds its resources.
• Process or environment injection: wrap helper processes or inject environment variables needed for first-run initialization.

The key limitation is that most compatibility problems only surface at runtime. There’s no static scanner that lists every possible runtime assumption. That’s why a test-driven approach — run, observe failures, apply targeted fixups, iterate — is the practical method for converting apps.

Community and maintenance

Microsoft has open-sourced PSF and maintains a growing catalog of community-contributed fixups. Over time, that shared library reduces conversion effort for common patterns, but for many enterprise apps you’ll still need custom configuration or bespoke fixups.

Final Thoughts

MSIX delivers major operational advantages, and PSF provides a pragmatic compatibility bridge for many Win32 apps. Combined with InstallShield’s packaging, validation, and automation capabilities, organizations can accelerate MSIX adoption without large rewrites — using PSF to unblock immediate needs while planning longer-term modernization where required.

Try InstallShield’s MSIX tools: start a free trial to convert your first package and see how PSF integration can simplify compatibility work.

Additional Resources

Microsoft’s Official Documentation on PSF

Package Support Framework on Github