v2025.01.02

Release 2025.01.02

Contains a fix for DynamicLibrary fixup for a situation where the app tries to load a dll by name but leaves off the ".dll".
Also a debug output message change in the debug build in MfrFixup.

v2024.10.26

Release includes the following:

• Added new option for PsfLaucher and PsfFtaCom to prevent MultipleInstances to prevent multiple instances of the same application from running in the user session.
• Return of support for RunInVirtualEnvironment for scripts. Default remains true, but now false is also supported again.
• Fix for different powershell versions installed on the client machine when used in PsfLauncher.
• Added a date oriented versioning to the exe/dll properties of Psf build components except PsfMonitor.

v2024.08.05

This release includes the following:

• Creation of a new launcher program, PsfFtaCom.exe. This launcher may be used to launch FTA Shell Verb commands, allowing for multiple target exes to be targeted by different verbs to the same file type. When added to the AppXManifest, it's Application can also become the placeholder for all FTA shell verbs, FTA shell extensions, and any application-level COM extension elements, thereby avoiding potential uniqueness limitations imposed by the manifest schemas.
• A fix for PsfLauncher Argument Virtualization.
• A fix to a crash involving a downrev version of windows.storage when adding a detour to it.

v2024.06.07

Patch for certain Windows10 systems where Windows.Storage.dll does not have an exported ShellExecuteW function.

v2024.03.04

• MFR: Add support for SetCurrentDirectory ILV-Aware mode to force path to be a
  package path when appropriate. When an app uses a file-picker dialog (which currently bypasses MFR), it might cause the app
  to request a file in the \?\UNC\server\share\path format. We now convert this to the normal form of \server\share\path
  before processing the request.
• RegLegacy: Don't let staterepository requests get into the container registry.

v2024.02.04

This release includes the following:

• Updated RegLegacyFixup to more certain intercepts from Kernel32.dll to the lower layer KernelBase.dll, and added a new intercept in KernelBase.dll.
• Updated MfrFixup to add additional intercepts in Ntdll.dll and Windows.Storage.dll. At this time these intercepts only add logging calls to detect when calls are made through these functions that have not yet been intercepted at a higher layer. Based on application evidence in the future, these functions could be updated to improve app compat to apps that use Microsoft libraries that bypass Kernel32.dll.
• Updated MfrFixup and FileRedirectionFixup to recognize file path in the category of Windows Storage Namespace ("\?\STORAGE#Volume").

NOTE: Developers that want to build the PSF from these sources will need to now add the Windows Driver Kit (WDK, latest version is fine) on their development system.

v2024.01.02

This release includes the following changes:

• Port of RegLegacyFixup "DeletionMarker" rule recently added to the Microsoft fork.
• New ReglegacyFixup "JavaBlocker" rule to simplify blocking newer versions of java inside a package.

v2023.08.28

Changes to using the PsfRunDll##.exe to support cross-architecture (bitness) launches of sub-processes when PSF components are not in the root folder of the package, as would happen with using PsfLauncher.

2023-08-13

August 2023 updates.

• More standard level debugging (_Debug) on RegLegacyFixup for calls to Delete things.
• PsfRuntime: Fix to call to SetDllDirectory with null path (to restore order), added SetDefaultDllDirectories for debugging too.
• MfrFixup: ShellExecute was being recursive and crashing.
• Cleanup on debug builds to remove ".dll" file.

v2023.07.03

RegLegacyFixup and MfrFixup fixes (plus tests)