cm0002@sh.itjust.works to Programmer Humor@programming.dev · 8 天前Deleting Fileslemmy.mlimagemessage-square163fedilinkarrow-up11.38Karrow-down113file-text
arrow-up11.37Karrow-down1imageDeleting Fileslemmy.mlcm0002@sh.itjust.works to Programmer Humor@programming.dev · 8 天前message-square163fedilinkfile-text
minus-squareLandless2029@lemmy.worldlinkfedilinkarrow-up34·7 天前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.
minus-squarePiafraus@lemmy.worldlinkfedilinkarrow-up5·7 天前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
minus-squareLandless2029@lemmy.worldlinkfedilinkarrow-up1·7 天前Gawd forbid users get some transparency.
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up2·7 天前Right? 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.