Keepass2 gets installed in (wrong)different Folder than usual.

[ChristopherMahr]

Relevant area(s)

WinGet CLI

Relevant command(s)

winget install

Brief description of your issue

Hello,

I install Keepass2 on multiple different AVD Environments via Winget. I always use the exact same installationmethod and the same Winget Public package.

Winget Package: DominikReichl.KeePass

I now have a wierd behavior on a new Environment build exact teh same as another environment. I basically copied the code in Terraform to create a semilar image and do a rollout in another hostpool.

However. normally Keepass gets installed in C:\Program Files\KeePass Password Safe 2
On this specific environment it gets installed in C:\Program Files (x86)\KeePass2x

I tried several times with uninstall and install. older versions but always same result.

I would like to have it installed in the normal Folder like always, in C:\Program Files\KeePass Password Safe 2

This is the output when I install it.

winget install DominikReichl.KeePass
Found KeePass [DominikReichl.KeePass] Version 2.61.1
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://sourceforge.net/projects/keepass/files/KeePass%202.x/2.61.1/KeePass-2.61.1.msi/download
██████████████████████████████ 3.22 MB / 3.22 MB
Successfully verified installer hash
Starting package install...
Successfully installed

I do the very exact same thing on the one environment which i copied the new from and on the new environment where i copied it to with different result.

Why is this happening?

Steps to reproduce

winget install DominikReichl.KeePass

Expected behavior

winget install DominikReichl.KeePass installs Keepass in C:\Program Files\KeePass Password Safe 2

Actual behavior

winget install DominikReichl.KeePass installs Keepass in C:\Program Files (x86)\KeePass2x

Environment

winget --info
Windows Package Manager v1.29.280
© 2026 Microsoft. All rights reserved.

Windows: Windows.Desktop v10.0.26200.8655
System Architecture: X64

Windows 11 25H2 AVD

[Trenly]

What happens if you download and run the installer manually? Based on what I can see - this seems likely to be an issue with the environment or the installer rather than with WinGet; however, the only way to confirm that is to check what happens doing a manual install.

[ChristopherMahr]

Hello, it now happens on all our environments in each image. it seems to be changed within the winget package.?

[ChristopherMahr]

IT only seems to happen on new systems not on systems, where keepass already has been installed in the normal folder, It seems thatone gets remembered?

[Trenly]

@ChristopherMahr - That doesn’t really answer my question. What happens if you download and run the Keepass installer manually without using WinGet?

As far as I can tell, nothing has changed about the manifest that WinGet uses