cm0002@sh.itjust.works to Programmer Humor@programming.dev · 20 hours agoDeleting Filesimagemessage-square157fedilinkarrow-up11.26Karrow-down111file-textcross-posted to: programmerhumor@lemmy.ml
arrow-up11.25Karrow-down1imageDeleting Filescm0002@sh.itjust.works to Programmer Humor@programming.dev · 20 hours agomessage-square157fedilinkfile-textcross-posted to: programmerhumor@lemmy.ml
minus-squareLandless2029@lemmy.worldlinkfedilinkarrow-up29·9 hours 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-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up1·47 minutes agoRight? I get that it’s “alarming” to users to see weird stuff, but just hide it under a little expandable thing.
minus-squarePiafraus@lemmy.worldlinkfedilinkarrow-up2·7 hours 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·5 hours agoGawd forbid users get some transparency.
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.
Right? I get that it’s “alarming” to users to see weird stuff, but just hide it under a little expandable thing.
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.