No MSFT_Volume objects found with property 'DriveLetter' equal to 'Z' about winfsp HOT 5 CLOSED

I believe Get-Volume is used to enumerate "disks/partitions" and not file systems. WinFsp only implements file systems that may not have an underlying "disk".

For example, on my laptop Get-Volume lists all partitions:

billziss@xps ⟩ ~ ⟩ get-volume

DriveLetter FriendlyName FileSystemType DriveType HealthStatus OperationalStatus SizeRemaining Size
----------- ------------ -------------- --------- ------------ ----------------- ------------- ----
            Recovery     NTFS           Fixed     Healthy      OK                       515 MB ...B
C                        NTFS           Fixed     Healthy      OK                      1.08 TB ...B
                         NTFS           Fixed     Healthy      OK                      85.1 MB ...B

from winfsp.

Is it possible to configure WinFsp's file system to be enumerated under this command?

I am also using Adobe applications, and the WinFsp filesystem does not show up under that application's explorer (The C drive is visible). This renders the WinFsp filesystem unusable for many applications. Get-Volume is another case where I would expect to see the filesystem but cannot, and seemed like a simpler way to investigate however the issue appears in more cases than this command in powershell.

Aside: Would Get-Disk or Get-Partition be used to enumerate disks/partitions? How does Get-Volume differ from these?

from winfsp.

Which Adobe application does not work with WinFsp? Can you demonstrate the problem with Adobe against MEMFS?

Also try mounting as a network file system (e.g. using the -u \Server\Path switch in MEMFS).

from winfsp.

The Adobe Premiere application, for instance, does not see the disk file system.

Interestingly, the disk filesystem is recognized when running passthrough-dotnet. I will continue to dive into any differences in our implementation and the passthrough implementation, but I did notice that passthrough-dotnet uses the WinFsp Launcher.

Does the choice to use the WinFsp launcher or not influence this behavior?

Regarding switching to a network drive mount: If I mount as a network drive the application can see the file system, but for many other reasons (Mainly around compatibility with network drives) it is not a viable option for us to mount as a network file system. We need to present the filesystem as a local disk.

from winfsp.

The Adobe Premiere application, for instance, does not see the disk file system.

Does this problem happen with MEMFS? MEMFS is the reference file system for WinFsp, so if you can demonstrate a bug against MEMFS there is a much higher chance of getting it fixed.

Does the choice to use the WinFsp launcher or not influence this behavior?

The Launcher starts file systems as network drives by default, so it is likely why this worked.

from winfsp.