back in the XP days, I used a software called "Unlocker" just for this problem. It probably still exists, I don't know, because since Windows 7, the easiest way to find out what process locks a file is to open Resource Monitor (Start search: resmon) and on the CPU tab, using the "Associated handles" list, you can search for the file name and see the process in question (and kill it).

So yeah, Resource Monitor is a useful tool on Windows.

[–] rockerface@lemmy.cafe 48 points 1 week ago (19 children)

There's a collection of free little utilities called Microsoft PowerToys, including the file unlocker thing. Why would they not include these into base kit Windows is beyond me.

[–] Redex68@lemmy.world 9 points 1 week ago (1 children)

I feel like it's a testing ground for new features for them, but not sure why some aren't yet integrated. Best guess: the PowerToys team has less red tape and checks to go through than the Windows team to allow for faster iteration, but that means that integrating the features wouldn't be just the click of a button since they'd have to adapt it to fit the Windows style. But this is just a wild guess.

[–] some_kind_of_guy@lemmy.world 6 points 1 week ago (1 children)

I think you're right on the money. There seems to be a component of enticing power users to stick with Windows as well. The app is still "in beta" despite the first release being in 1996 (!). I had to look that up, because I'd only heard about it in the early windows 10 days.

[–] Deebster@infosec.pub 3 points 1 week ago

The first version of PowerToys was released for Windows 95 on 17 November, 1996 as a download on Microsoft's FTP server at the time.

Well wadaya knows?

I like that it wasn't a proper installed thing, just a bunch of executables in a zip file.

load more comments (17 replies)

load more comments (19 replies)