You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An MSIX repackaged application that launches an external process with command line arguments including native app data path will not be virtualized and tries to look into the native app data folder. For example, consider an application trying to launch notepad.exe process to open its settings.txt file (in per user per app data location) through createProcess API, it uses command line arguments "C:\Windows\System32\notepad.exe C:\Users\UserName\AppData\Local\AppName\settings.txt". This call fails to open setting file which is actually present in per user per app data folder.
This can be fixed through redirecting any createProcess call arguments from native appdata to per user per app data when the target file provided in arguments is actually present in per user per app data folder. When any child process that's not running in package context is triggered, detoured createProcess will check each argument passed and will convert it to corresponding path in per user per appdata folder.
For example, to convert CreateProcess with argument "C:\Windows\System32\notepad.exe C:\Users\UserName\AppData\Local\AppName\ settings.txt" to "C:\Windows\System32\notepad.exe C:\Users\UserName\AppData\Local\Packages\packageFamilyName\LocalCache\Local\ AppName\settings.txt"
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
An MSIX repackaged application that launches an external process with command line arguments including native app data path will not be virtualized and tries to look into the native app data folder. For example, consider an application trying to launch notepad.exe process to open its settings.txt file (in per user per app data location) through createProcess API, it uses command line arguments "C:\Windows\System32\notepad.exe C:\Users\UserName\AppData\Local\AppName\settings.txt". This call fails to open setting file which is actually present in per user per app data folder.
This can be fixed through redirecting any createProcess call arguments from native appdata to per user per app data when the target file provided in arguments is actually present in per user per app data folder. When any child process that's not running in package context is triggered, detoured createProcess will check each argument passed and will convert it to corresponding path in per user per appdata folder.
For example, to convert CreateProcess with argument
"C:\Windows\System32\notepad.exe C:\Users\UserName\AppData\Local\AppName\ settings.txt"
to"C:\Windows\System32\notepad.exe C:\Users\UserName\AppData\Local\Packages\packageFamilyName\LocalCache\Local\ AppName\settings.txt"
Beta Was this translation helpful? Give feedback.
All reactions