Winget installs a new separate install when RetroArch is installed via Steam

[Icyfiremario]

Description

Whenever I update apps using Winget the stand-alone version of RetroArch gets installed because the Steam version is detected but not its version.

Expected behavior

Winget does not detect the Steam version at all or it detects the installed version and updates via Steam. (idk if Winget can tell Steam to update apps)

Actual behavior

A new install of RetroArch is installed completely separate from Steam.

Steps to reproduce the bug

1. Have RetroArch installed via Steam.
2. Update apps with Winget using the command winget update --all --include-unknown

Bisect Results

I do not know how long this has been going on I only just noticed it.

Version/Commit

• RetroArch: 1.17.0/ad8975cb5a

Environment information

• OS: Windows 11 64x 23H2

[RobLoach]

Did you install RetroArch with Winget in addition to Steam? Or just Steam, and then use Winget? Because this sounds like a Winget problem.

[Icyfiremario]

Did you install RetroArch with Winget in addition to Steam? Or just Steam, and then use Winget? Because this sounds like a Winget problem.

Just steam

[RobLoach]

Sounds like Winget needs to ignore Steam-installed files. Likely run into the same problem with other Steam applications like Blender and Aseprite.

[Icyfiremario]

That's prob the best answer to this. However, it could be my fault. I can't remember if it was on my current computer or my older one but I did have RetroArch installed standalone and through Steam to compare them. Winget picked up on the standalone but when I uninstalled the standalone version it could still find the Steam install and assumed it was a broken install of the standalone.

[Icyfiremario]

That's prob the best answer to this. However, it could be my fault. I can't remember if it was on my current computer or my older one but I did have RetroArch installed standalone and through Steam to compare them. Winget picked up on the standalone but when I uninstalled the standalone version it could still find the Steam install and assumed it was a broken install of the standalone.

Never mind this I just had a friend of mine who owns aseprite on Steam test it and it doesn't do it with aseprite. He also has Retroarch installed through Steam and it detects as unknown as well he's never used the standalone version so it's not some weird leftover files from an old install.