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
Komac correctly detects the ALLUSERS installer switch but sets the manifest wide scope to user even though ALLUSERS=1 forces a per-machine install (AllUSERS Property)
I've only seen this behavior for Pandoc, therefore I'm not sure whether it's a specific problem with its installer. (microsoft/winget-pkgs#197015, microsoft/winget-pkgs#165049)
Maybe a detection of ALLUSERS=1 could be used as fallback to set the installer scope to machine even when komac would usually detect it otherwise?
The text was updated successfully, but these errors were encountered:
Thanks for reporting! This is because the ALLUSERS value is missing in the MSI property table which usually indicates a per-user install scope. However, Pandoc lets you modify this in the installer:
Therefore, we can check the MSI control table for anything that controls ALLUSERS:
As this is present in Pandoc, we can consider the scope to be agnostic.
Is there an existing issue for this?
What happened?
When creating an update for Pandoc the scopes aren't correct
Komac correctly detects the
ALLUSERS
installer switch but sets the manifest wide scope touser
even thoughALLUSERS=1
forces a per-machine install (AllUSERS Property)I've only seen this behavior for Pandoc, therefore I'm not sure whether it's a specific problem with its installer. (microsoft/winget-pkgs#197015, microsoft/winget-pkgs#165049)
Maybe a detection of
ALLUSERS=1
could be used as fallback to set the installer scope to machine even when komac would usually detect it otherwise?The text was updated successfully, but these errors were encountered: