WIN: PWSafe Config stores Username as case sensitive

[schnaggi]

I have different behaviours in an business environment. There is generic hardware (laptops, desktops) and vms. All devices using the same installation, there is no special config.

I noticed that on laptops and desktops the configuration is stored for host ANY and user . On some vms the configuration is set per computer, so in the preferences=>system, the computername is written.

Probably is has something to do with the screencapture blocking I had to disable because a special software blocked the appearence of the password safe window on some vms.

Additionally I noticed that the username is stored in the configfile but if you default user is "username" and you use "Username" after a while, the stored configuration for the "other" user is not used and a new username is created in the configuration file. On Windows username and Username are the same account.

My question is now: how to disable this computername saving and the username problem in the configuration file.

OS is Windows 10 and 11, installation is done by using the msi file. The latest version is used.

Solution: set a fixed computername and username by using -h -u an example is: -h ANY -u ANY

[schnaggi]

I noticed that on hardware the startmenu entry is modified and a parameter -h ANY was added. So it looks like this problem is solver. So now I just need a solution for USER1111 and user1111

[schnaggi]

Ok, I could workaround the problem by adding -u ANY to the startmenu entry. But there should be no difference between USERID and UsErId.

[ronys]

Glad you found a workaround. Good point about case-insensitivity. Actually, both hostname and username should be case-insensitive under windows. Keeping this ticket open until that's resolved.