From: nospam@needed.invalid   
      
   On Sun, 12/14/2025 6:48 AM, T wrote:   
      
   >   
   > Cobian is written in  Delphi.  I presume he is using a   
   > library provides by such.  It would be the library that is   
   > at fault by your reasoning.  Although Windows is not the   
   > sharped tack in the box.   
   >   
   > Upping the sockets did fix the issue.   
   >   
   > Oh get this, it happened on the customer old W10 machine   
   > and then on this new W11 machines with his profiles migrated   
   > over.  The error only happened on his documents directory.   
   >   
   > The fix I used is also recommended over on   
   >   
   >     
   > https://hstechdocs.helpsystems.com/manuals/globalscape/archive   
   secureserver3/Windows_Registry_keys_for_TCP_IP_Performance_Tuning.htm   
      
   Just out of curiosity, have you ever captured an *entire*   
   backup session with Process Monitor ?   
      
   The trace is huge. I've done that, but the only reason   
   I *could* do that, is the breakage I was looking for was   
   close to the end of the backup, so it was relatively easy   
   to find the problem. The post-trace search on ProcMon used   
   to be decently fast, but today it is like molasses to find   
   anything in there. In that particular case, I needed 6GB   
   of storage to store the trace file for later.   
      
   Maybe there is a circular item (like a Reparse Point) that   
   Cobian is walking down, and that is doing it. (It walks   
   the looping structure until it gets "Path Too Long" as   
   a response.)   
      
   It could be that Cobian isn't really fully compatible with   
   the horrible mess that is NTFS on W10/W11.   
      
   Just some of the command line options in Robocopy, should   
   give some idea what "holes" exist for directory traversal   
   softwares to trip over.   
      
   And one place for a software to trip in, is the actual   
   SChannel socket folder. Hashdeep, if it gets in there,   
   it finds sockets which are not being used, and it   
   won't let them go (because there is no EOF to ever   
   be expected from the socket while "reading" it). Any software   
   doing traversal, has to be constructed for all the "traps"   
   on the C: drive.   
      
   I bet if your Cobian session was backing up D:   
   on the customer machine, this socket issue doesn't happen.   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)