On 6 Jul 2018 01:58:04 GMT, Arlen Holder wrote:

Add the custom "App Paths" registry entry:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\
vipw.exe
Default = c:\app\editor\passwd\keepass\KeePass.exe

In the previous post, the App Paths key was set to the executable.
In this post, I tested setting the App Paths key to the passwd file.

Add the custom "App Paths" registry entry:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\
vipw.exe
Instead of a default to the KeePass executable:
Default = c:\app\editor\passwd\keepass\KeePass.exe
I changed the default to the passwd file itself:
Default = c:\data\private\passwd.kdbx

Both methods work fine, where the latter method means that I can probably
set up the location of the master passwd file so that a single ciphertext
passwd file can be accessed by all machines on the network.

For example, something like this network path might work?
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\
vipw.exe
Default = \\machine\share\path\passwd.kdbx

I readily admit that I don't know Windows (SMB?) networking well, so if
someone has advice for setting up that capability to store a single
ciphertext passwd file on a network share, please advise so that this
"vipw" command will work on all the systems, whether Android, iOS, Windows
or Linux to access the single master passwd file on the LAN.