[BUG] Missing install location on package details

[Butterfly-Dragon]

Please confirm these before moving forward.

• I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
• This improvement refers to an existing feature. If you want to suggest a new feature, please use this template.
• This improvement is not a bug. If you want to report a bug, please use this template.

Describe the improvement

A highly valuable feature from previous versions, which allowed users to find a package's installation path directly in the UI (e.g., by pressing Enter on an item). This feature is no longer present for reasons unknown to me. This regression creates significant usability issues.

I suggest re-implementing this functionality, ideally in one of two ways:

• If technically feasible, please default all package installations to standard, predictable locations (C:\Program Files; C:\Program Files (x86)). This appears to be the standard behavior for tools like Winget, Rust, Chocolatey, and other package managers when invoked manually, but not when they are invoked via UniGetUI.

• If standardized paths are not possible (due to limitations unknown to me), please re-implement the feature where UniGetUI clearly and persistently displays the final installation path for every package within its UI details page.

Relying on the temporary CLI output during installation is an insufficient workaround. This output is cleared too quickly on success, and paths can change during updates (standard practice in the last few years is to add version numbers to installation directories), making persistent visibility in the UI essential.

Describe how this improvement could help users

This improvement would solve several significant usability problems that currently make the user experience cumbersome and inefficient.

• Simplifies PATH Configuration: The absence of a visible or predictable path makes it extremely difficult to locate executables, particularly for command-line (CLI) tools that users must manually add to their system PATH variable to function correctly.

• Removes Permission and Access Barriers: UniGetUI frequently installs packages into protected, non-standard directories (e.g., C:\Users\[USER]\AppData\Local\Microsoft\WindowsApps or C:\ProgramData). Even as an administrator, accessing or managing files in these locations often requires complex manual steps to take ownership or modify permissions, which is a hurdle. This behavior seems specific to UniGetUI's invocation, as manual installs via Winget or Chocolatey or other package managers typically use more standard directories or more accessible ones.

• Fixes Program Discoverability: These non-standard locations are often excluded from Windows Search indexing by default. Even when manually added to the index, search frequently fails to find the executables. This forces users to manually hunt for applications, defeating the purpose of a package manager.

By providing predictable paths or, at a minimum, a persistently visible path in the UI, you would significantly reduce user friction, save time, and make UniGetUI a much more reliable and efficient tool for managing all types of software.

[marticliment]

What do you mean? This feature has not been removed

[Butterfly-Dragon]

@marticliment Apologies if i sound rude, or if i apparently am misreading the information presented. But i cannot see it anywhere.

I could post more of these programs i have installed but i do not see this very critical info in any of them.

[marticliment]

Oh, I see what is happening. The install path was readable from the install options, and changes here hid the install path.
In order to open the install location, right-click a package -> Open install location (If greyed out it means it was not found).

I will try to fix this

[Butterfly-Dragon]

@marticliment apologies but honestly they are all greyed out, even stuff that i have put in the PATH variable is missing.

[Butterfly-Dragon]

update: the stuff i manually installed via a commandline batch i do on every new system has a path variable associated: