From: not@all.invalid   
      
   Paul wrote:   
   >On Sun, 2/1/2026 5:11 AM, Apd wrote:   
   >> Paul wrote:   
   >>> On Sat, 1/31/2026 6:10 AM, Apd wrote:   
   >>>> csc://{S-1-5-21- ... -1001}   
   >>>>   
   >>>> That's some weird URI with an unknown scheme (csc) and a SID, presumably   
   >>>> for a user account.   
   >> [...]   
   >>   
   >>> CSC is apparently "Client Side Caching", whatever that means.   
   >>   
   >> That sounds like a reasonable interpretation. Presenting what appears to   
   >> be an internal implementation detail to the user is a bad idea (or a   
   >> bug)!   
   >   
   >If you asked me where that was, I doubt I could find it.   
   >   
   >Googling, says it is here.   
   >   
   >   C:\Windows\CSC   
      
   Apparently it's the cache for offline (network) files which is disabled   
   here. I can see it in Explorer but couldn't read or get in so took admin   
   ownership (it belonged to system) and set permissions. I don't know why   
   the indexer would want to include such a directory that can't normally   
   be accessed, especially labelling it or its content with an   
   incomprehensible URI.   
      
   >I can see it in an NFI output from Windows 10.   
   >   
   >   File 101681   
   >   \Windows\CSC\v2.0.6\NAMESP~1    [probably NAMESPACE]   
   >   
   >There don't seem to be any files in there.   
      
   Just two files (pq, sm) of a few bytes, empty namespace and temp   
   directories in mine. Thanks for helping to clear this up.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)