From e452f75c9cbd02f4e9b3f0b7e613a0b7d3da87d9 Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Sat, 20 Jan 2024 10:55:26 +0000 Subject: [PATCH] doc: SxsDir registry setting --- doc/WinFsp-Registry-Settings.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/WinFsp-Registry-Settings.md b/doc/WinFsp-Registry-Settings.md index 56bf2bca..fdca9313 100644 --- a/doc/WinFsp-Registry-Settings.md +++ b/doc/WinFsp-Registry-Settings.md @@ -65,6 +65,8 @@ Primary registry key used to store WinFsp settings. On a 64-bit system (x64 or A * `InstallDir (REG_SZ)`: Contains the WinFsp installation directory. +* `SxsDir (REG_SZ)`: Contains the WinFsp Side-by-Side (SxS) directory. The SxS directory allows for multiple versions of WinFsp to be active at the same time and among other benefits it enables reinstalling WinFsp without reboot. The SxS directory contains primarily executable files. + * `DistinctPermsForSameOwnerGroup (REG_DWORD)`: Directs how WinFsp-FUSE should consider UNIX owner and group permissions in the case when the Windows owner and group SID are the same (for example, this can happen when someone uses a Microsoft account as their primary login). When this setting is 0 and the Windows owner and group SID are the same, WinFsp-FUSE combines the UNIX owner and group permissions (for example, user permission `rw-` and group permission `---` combine to `---`), which can result in inadvertent "access denied" errors. When this setting is 1 and even if the Windows owner and group SID are the same, WinFsp-FUSE looks at the UNIX owner permissions and the UNIX group permissions separately. The default value is 1 since v1.11B1 and was 0 in earlier versions. * `MountBroadcastDriveChange (REG_DWORD)`: A value of 1 instructs WinFsp to broadcast an additional "drive change" message to all top-level windows during mounting and unmounting. The default value is 0. Normally the Windows infrastructure broadcasts a `WM_DEVICECHANGE` message whenever a drive gets added/removed. In some rare systems it is possible for this message to get lost or stalled. The workaround for these rare systems is to enable this registry setting, in which case WinFsp will broadcast the `WM_DEVICECHANGE` using a slightly different but more reliable method than the one Windows uses.