Using VolumeID versus Drive Letter

Content Authoring
1

(imported topic written by Nem0)

I want to read the permissions from a file on a volume with no drive letter. In Windows or dos, I can substitute the drive letter for the volumeid which works well however, when I try this using relevance I get an error.

As an example;

q: security descriptor of file “\?\Volume{a0f971c4-8bf7-11e0-b066-806e6f6e6963}\bootmgr”

E: Singular expression refers to nonexistent object.

q: security descriptor of file “c:\bootmgr”

A: D:PAI(A;;0x1200a9;;;SY)(A;;FA;;;BA)(A;;FR;;;BU)(A;;FA;;;S-1-5-80-956008885-3418522649-1831038044-1853292631-2271478464)

T: 0.755 ms

2

(imported comment written by BenKus)

Yes… I don’t think our file inspectors support that format… You will need to somehow translate the volumeid into a drive letter (maybe with wmi?)

Ben

3

(imported comment written by Nem0)

Thanks Ben