File Locksmith | PowerShell

[MFKDGAF]

Description of the new feature / enhancement

Properly report when a file is open in PowerShell 5.1 and 7.x window instead of reporting that Windows Explorer has the file opened/locked.

Scenario when this would be used?

When trying to delete or move a file or directory that is open in PowerShell Window and you not relaizing it.

Supporting information

I had a PowerShell file opened in a PowerShell window (.\PowerShell-File.ps1) and when I went to delete or move the directory it couldn't. File Locksmith was saying Windows Explorer had the file locked. I restarted Windows Explorer but the file was still locked and File Locksmith was still reporting that Windows Explorer had the file locked (which makes sense why restarting Windows Explorer didn't unlock the file).

This happened on Windows 10 using PowerShell 5.1. I navigated to the directory that the script was in (C:\Temp). Then went to File > Open Windows PowerShell > Open Windows PowerShell. I'm not sure if the problem would have happen if the PowerShell script was ran in Windows Terminal.

[Aaron-Junker]

/dup #22315

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!