Thorsten

Is anything like this possible in the meantime? I'd like to disable update check for the whole organization.

OK, then the only solution so far is a script that runs on user login and changes the values in `%APPDATA%\KeePassXC\keepassxc.ini`. Thanks anyway for the info! EDIT: Run `(Get-Content $env:APPDATA\KeePassXC\keepassxc.ini)...

Thanks for the double enter hint, did not notice this, yet 👍

Just watched a video about this Grav git-sync and IMHO that's indeed even cooler than a self-made versioning: https://www.youtube.com/watch?v=3fy78afacyw Maybe something to consider 😉

I also need calendar sharing, so thumbs up for this feature request :+1: BTW: Sharing seems to work with symbolic links on the file system. Is there a reason why...

The symlinking method works for me with two users since my last post. I did not have problems so far.

As macOS and Linux also use the `keepassxc.ini` I actually would not use the registry on Windows. Usining a `keepassxc_enforced.ini` is a simple way to overwrite settings of a `keepassxc.ini`....

> Almost all policy enforcement on Windows is done via the registry. That goes for GPO and Intune management. It's just the way Windows "prefers" to handle security policies. As...

Is there any need, that `C:\ProgramData\Winget-AutoUpdate` is user writable? Having all scripts/EXEs in a directory, that is not writable by users, makes things much easier with AppLocker.

Users also have permissions to create files in ProgramData. So even if the Winget-AutoUpdate scripts are read only for users it is not save to create a simple AppLocker rule...