I'm having a hard time imagining why you would get that error with Screenshot Captor.. and you're saying reverting to prior version works? That is bizarre. Anyone else?
Are you using some kind of network mapped drive? Or maybe some antivirus program doing something weird..
Thanks for responding.
I know what you mean. I sometimes have a hard time imagining that I will be able to get up in the mornings, but it usually all works out somehow.
There have been no recent changes to mapped drives or anything. The system remains relatively stable (or whatever passes for "stable" with Win10...).My drives:
(what I use most)
- The HDD.
- 3 x Cloud Drives (accessed fairly frequently).
- 1 x Cloud Drive (accessed occasionally).
- 1 x 2GB dynamically changing RAMdrive (set as the TEMP variable).
The only slightly unusual thing I do with drives (have done for ages) is set hard links to cloud storage volumes/folders. I use these hard links as virtual folders, some of which are my main "working folders".
The hard links are very stable and never cause any problems. The drives I use are unlikely to be causing the problem, because - and as you have also observed - the earlier version of SC consistently works OK, whereas it is only the latest version of SC which consistently does not.
The only "odd" thing I have found with folders is the mysteriously-appearing "QL folter temp"
, which I referred to in a Launch Bar Commander - Latest Version
thread. I wondered whether it might have something to do with the observed LBC long delays.