AutoHotKey not completing installation about winget-pkgs HOT 6 OPEN

That switch will not be used unless you specify the install destination by using the -l or --location switches from WinGet.
In user scope the program will be installed to %LOCALAPPDATA%\Programs\AutoHotkey by default.

from winget-pkgs.

from winget-pkgs.

Shouldn’t the application still end up on $PATH though?

WinGet doesn’t have the ability to add programs to PATH unless they have the installer type portable - which are loose binaries that don’t have an installer. In all other cases, it is up to the application's installer to update PATH.

from winget-pkgs.

@Trenly Question. If the installer's default action is to create C:\Program Files\AutoHotkey\ and put the relevant files there, why wouldn't installing the application with winget do the same thing?

from winget-pkgs.

@Trenly Question. If the installer's default action is to create C:\Program Files\AutoHotkey\ and put the relevant files there, why wouldn't installing the application with winget do the same thing?

As @SpecterShell mentioned, the installer puts the files in different locations depending on if itsinstalling in user scope or machine scope. If you don’t specify --scope machine, the installer will generally be executed in user scope. If you're an admin, running the installer you downloaded yourself will likely default to the machine scope

from winget-pkgs.

I tested this with #153765 and wasn't able to verify this behavior. This package installs normally (into \Program FIles) on a Windows 10 VM:

The application reports missing a configuration file, but this might be normal program operation:

Should this be tested in another way?

from winget-pkgs.