cm0002@sh.itjust.works to Programmer Humor@programming.dev · 26 days agoDeleting Fileslemmy.mlexternal-linkmessage-square165fedilinkarrow-up11.42Karrow-down113file-textcross-posted to: programmerhumor@lemmy.ml
arrow-up11.41Karrow-down1external-linkDeleting Fileslemmy.mlcm0002@sh.itjust.works to Programmer Humor@programming.dev · 26 days agomessage-square165fedilinkfile-textcross-posted to: programmerhumor@lemmy.ml
minus-squareLandless2029@lemmy.worldlinkfedilinkarrow-up34·25 days agoYeah there’s a Microsoft sysinternals utility where you can drag a file into to fetch that info for you. Makes zero sense there isn’t a >Details in the error notification that tells you the damned process in Windows.
minus-squarePiafraus@lemmy.worldlinkfedilinkarrow-up5·25 days agoNot only that, but you can actually search all active processes to see which handles they keep references to. Just search the name of your file and it will show you the processes which use it
minus-squareLandless2029@lemmy.worldlinkfedilinkarrow-up1·25 days agoGawd forbid users get some transparency.
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up2·25 days agoRight? I get that it’s “alarming” to users to see weird stuff, but just hide it under a little expandable thing.
Yeah there’s a Microsoft sysinternals utility where you can drag a file into to fetch that info for you.
Makes zero sense there isn’t a >Details in the error notification that tells you the damned process in Windows.
Not only that, but you can actually search all active processes to see which handles they keep references to. Just search the name of your file and it will show you the processes which use it
Gawd forbid users get some transparency.
Right? I get that it’s “alarming” to users to see weird stuff, but just hide it under a little expandable thing.