fix: resolve Known Folder GUID paths before launching apps#110
Merged
Jeomon merged 1 commit intoCursorTouch:mainfrom Mar 16, 2026
Merged
Conversation
Start Menu shortcuts may use GUID-based paths (e.g.
{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\msinfo32.exe) that
Start-Process cannot handle directly. Resolve them via
SHGetKnownFolderPath before passing to PowerShell.
Member
|
gr8 work and thanks for pointing it out |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Apptool failing to launch apps whose AppID uses a Known Folder GUID path (e.g.{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\msinfo32.exe)resolve_known_folder_guid_path()utility that callsSHGetKnownFolderPathto resolve GUID prefixes to real filesystem paths before passing them toStart-ProcessProblem
When using the
Apptool inlaunchmode to start certain applications (e.g. System Information, Bandizip, ...), the following error occurs:On Windows, certain app entries may contain a path-like string prefixed with a Known Folder GUID, for example:
This value is not a normal filesystem path, so passing it directly to
Start-Processwill cause startup failures.Solution
Resolve the GUID prefix via the Win32
SHGetKnownFolderPathAPI before invokingStart-Process. For example:{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\msinfo32.exeC:\Windows\System32\msinfo32.exeIf the path does not match the
{GUID}\...pattern or the GUID is unrecognised, the original value is returned unchanged, so existing behaviour is unaffected.