The most common MSIX limitations and how to fix them with the Package Support Framework (PSF)

How to set the current working directory using the MSIX Packaging Tool

To go around this limitation, here are the steps you need to follow:

1. Create a new config.json and insert the following code into it:

{
    "applications": [
    	{
            "id": "",
            "executable": "",
            "workingDirectory": ""
    	}
	]
}

2. Open the MSIX package in MSIX Packaging Tool – Package Editor.

3. Open the AppxManifest.xml file.

4. Copy the value in the “Id” field within the AppxxManifest.xml file to the Applications “id” field in the config.json file.

5. Copy the value in the “Executable” attribute of the “Application” element within the AppxManifest.xml file to the Applications “Executable” field in the config.json file.

6. Set the “working directory” field in the config.json file to the folder where you will start your process.

7. Save the config.json file and copy it into the MSIX package (directly in the Package Root Directory).

{
    "applications": [
        {
            "id": "MYAPP",
            "executable": "MyApp.exe",
            "workingDirectory": "MyApp Subfolder"
        }
	]
}

8. Depending on your application architecture, add the corresponding PSF files into your MSIX package (directly in the Package Root Directory, next to the config.json file).

• PsfLauncher32.exe/PsfLauncher64.exe
• PsfRunDll32.exe/PsfRunDll64.exe
• PsfRuntime32.dll/PsfRuntime64.dll

9. Edit the manifest file – change the value of the “Executable” attribute of the “Application” element to point to the PsfLauncher executable instead of the original executable of your application.

Set the current working directory with Advanced Installer

With Advanced Installer, you don’t need to do any of the above. It’s all done automatically in the background for you. Just go to the “Application Details” page, scroll down to “Start Point” section and set the “Working directory” you need.

How to set command line arguments with MSIX Packaging Tool

To bypass the command line arguments limitations in MSIX, follow these steps:

1. Create a new config.json and insert the following code into it:

{
    "applications": [
    	{
            "id": "",
            "executable": "",
            "arguments": ""
    	}
	]
}

2. Open the MSIX package in MSIX Packaging Tool – Package Editor.

3. Open the AppxManifest.xml file.

4. Copy the value in the “Id” field within the AppxxManifest.xml file to the Applications “id” field in the config.json file.

5. Copy the value in the “Executable” attribute of the “Application” element within the AppxManifest.xml file to the Applications “Executable” field in the config.json file.

6. Set the “arguments” field in the config.json file to the value you need to be passed to the executable at runtime.

7. Save the config.json file and copy it into the MSIX package (directly in the Package Root Directory).

{
    "applications": [
        {
            "id": "MYAPP",
            "executable": "MyApp.exe",
            "arguments": "/k cd %MsixPackageRoot%/MyApp Subfolder "
        }
	]
}

%MsixPackageRoot% is a pseudo-variable that can be used inside of the MSIX packages and points to the root folder of the MSIX package.

8. Depending on your application architecture, add the corresponding PSF files into your MSIX package (directly in the Package Root Directory, next to the config.json file).

• PsfLauncher32.exe/PsfLauncher64.exe
• PsfRunDll32.exe/PsfRunDll64.exe
• PsfRuntime32.dll/PsfRuntime64.dll

9. Edit the manifest file – change the value of the “Executable” attribute of the “Application” element to point to the PsfLauncher executable instead of the original executable of your application.

How to set command line arguments with an application packaging tool - Advanced Installer

Just like setting a current working directory, setting a command line argument for the StartMenu application entry is a smooth and straightforward operation using Advanced Installer.

All you need to do is to go to the “Application Details” page, scroll down to “Start Point” section and set the “Parameters” you need.

How to set a non-executable as the target application using the MSIX Packaging Tool

Any shortcut to non-executable files is ignored by the MSIX Packaging Tool during the capture. That’s the reason why the corresponding entry needs to be manually added to the “Applications” element within the AppxManifest.xml file.

To overcome this limitation, you need to follow these steps:

1. Create a new config.json and copy the following code into it:

{
    "applications": [
    	{
            "id": "",
            "executable": ""
    	}
	]
}

2. Open the MSIX package in MSIX Packaging Tool – Package Editor.

3. Open the AppxManifest.xml file.

4. Create a new entry.

5. Point the “Executable” attribute of the “Application” element to the PsfLauncher executable.

6. Copy the value in the “Id” attribute of the “Application” element within the AppxManifest.xml file to the Applications “id” field in the config.json file.

7. Save the config.json file and copy it into the MSIX package (directly in the Package Root Directory).

{
    "applications": [
        {
            "id": "MYAPPREADME",
            "executable": "MyAppLauncher.txt"
        }
	]
}

8. Depending on your application architecture, add the corresponding PSF files into your MSIX package (directly in the Package Root Directory, next to the config.json file)

• PsfLauncher32.exe/PsfLauncher64.exe
• PsfRunDll32.exe/PsfRunDll64.exe
• PsfRuntime32.dll/PsfRuntime64.dll

How to set a batch file as a target in Advanced Installer

To set a batch file as a target for your application in Advanced Installer, just:

1. Go to the “Application Details” page.

2. Scroll down to the “Start Point” section.

3. Set the “Executable” field to point to the batch file.

You can see how these settings look in the image below.