File Locksmith doesn't detect locked folders

[Camios]

File Locksmith doesn't detect locked folders

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Empty result in File Locksmith's Who is using this File. (#25510), similarity score: 0.84
• [FileLocksmith] Crashes for every folder that is locked by a particular process (#32663), similarity score: 0.78
• File Locksmith fails to recognize process locking files, but Windows 10 names the application that has the lock (#21896), similarity score: 0.78

Closed similar issues:

• File Locksmith not showing results window (nothing happens on selecting from right-click menu) (#29598), similarity score: 0.78
• File locksmith not working, just displays an animated circle. (#21682), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[Camios]

Also seen in older version 0.79.0

[jaimecbernardo]

Thinking we're only checking files 🤔 Not folders. That might be the issue here.

[PolarGoose]

@Camios, did you try to run File Locksmith as an Admin?

[Camios]

Oh, does it have a limited scope of only checking/showing un-elevated processes for the current user? That would be unfortunate.
What's the correct way to run File Locksmith as an admin - does PowerToys have to be elevated and then when Locksmith is run it is automatically elevated?

[PolarGoose]

By default, it only checks the handles from the current user because it doesn't have access to other handles.
You can use this button to make FileLocksmith show all handles:

[Camios]

That button and the behaviour are unintuitive.
It would be much more user-friendly if it defaulted to showing any process locking the folder, regardless of the user. That's because the user knows it is locked and needs to know what is locking it. The user never wants processes that are locking the file to be hidden.

[PolarGoose]

@Camios,
Valid point.
Then please create a feature request.
Is the bug still relevant? Can it be caused by the fact that the file was locked by an elevated process, which is why it wasn't shown by FileLocksmith?

[Camios]

Compared to other lock finders and general user expectations, I'd still class this as a bug.
If the devs implemented what they were asked to do then the "bug" is in the design or the requirements (product management).

Falls under the "unexpected behavior" definition of a Bug?

[PolarGoose]

Logical. However, for example, Sysinternals Handle works like FileLocksmith. It only shows all handles if you run it as an admin.

I'm not a FileLocksmith maintainer, so I won't judge whether it should be a bug or a feature request. However. I have implemented my clone ShowWhatProcessLocksFile. It must also be run as an admin to show all handles. I consider this behavior reasonable. However, your proposal is also valid.