Several of us have, in our file context pull down menu, an option to "freeze" a file on the fileserver, that is, it simply re-arranges the bytes so that it is un-editable / un-loadable in Excel or Autocad, and will put the file back together when needed. This little app is located on the local computer in the path.

Most of us access the fileserver using a mapped drive, some have created a shortcut using \\<fileserver_name>. If we run this app against a file on a mapped drive, it happens right away. If the app is run against a file using the shortcut, i.e., \\<fileserver_name>\<share>\<filename>, it has to think about if for about ten seconds before anything happens. The util is written in D and compiled with dmd.

Any help solving this would be appreciated, I'm sure it's a simple thing or setting, but I don't even know where to start looking. All of our boxes are on 22H2 / 19045.4291 currently.