Forum Discussion
Add Environment Variable to MSIX package using PSF Fixups in Packaging Tool - what am I missing?
Your syntax looks OK to me.
I will mention that you will not see the environment variable by using any tools running outside of the container. Also, with userregistry = false you would also not see it in a process run inside the container if that process was not launched by PsfLauncher, which would be any process other than randomapp.
Hi Timothy, appreciate to see you reach out!
I got sidetracked with packaging other apps, but have returned to investigate this particular app requiring environment variables. Something very strange is occuring here.
In short, I manually modified the config.json file (biggest change being process match PSFLauncher) and changed out every PSF-file to their Debug-counterparts as retrieved from https://github.com/TimMangan/MSIX-PackageSupportFramework/blob/develop/ZipRelease.zip-v2025-8-2.zip. Therefore enabling me to use DebugView and follow what's going on "under the hood".
If the output is to be trusted, it seems that the EnvVarFixup .dlls aren't found as expected.
Both variants of the EnvVarFixup .dll's are of course in the root of the package.
Do you have any ideas on how to progress here?Ahah! As the dll is present in the root, this procmon error usually indicates missing dependencies of the PSF component. MfrFixup, RegLegFixup, and EnvVarFixup all have documented dependencies.
If you are manually adding PSF dlls, most likely you are missing the dependent VC Runtimes. Tooling generally adds these to the VFS\SystemX86 and VFS\SystemX64 folders, so I can't see if they are present.
Alternatively, and this is usually preferred, the VC Runtimes are supplied to the end-systems externally - meaning the latest Microsoft VC Runtimes 2015-2022 redistributables Latest supported Visual C++ Redistributable downloads | Microsoft Learn. In that case install both the 32 and 64 bit versions on end-user systems.
