You have closed Word, Excel, Outlook or whichever application was using a file, but Windows 11 still refuses to let you rename, move or delete it.

Windows might tell you:

• “The action can’t be completed because the file is open in another program.”
• “The folder or a file in it is open in another program.”
• “This file is in use.”
• “The process cannot access the file because it is being used by another process.”

The frustrating part is that the application Windows claims is using the file may be nowhere to be seen.

You have closed everything.

Task Manager doesn't show anything obvious.

You try again.

Still locked.

Usually, Windows isn't imagining things. A process somewhere on the computer still has an open handle to the file.

Rather than restarting the PC or randomly terminating processes, you can identify exactly what is holding the file open.

Two particularly useful Microsoft tools are:

1. PowerToys File Locksmith
2. Microsoft Sysinternals Process Explorer

And if you don't want to install anything, Windows also gives you another useful option that we'll cover later.

What Does “File in Use” Actually Mean?

When an application opens a file, Windows gives that application a reference to it known as a handle.

The application might use that handle to:

• read the file
• save changes
• generate a preview
• synchronise it
• scan it
• index it
• back it up
• monitor it for changes

Normally, the program releases the handle when it has finished.

But that does not always happen immediately.

You may close a Word document, for example, while another Microsoft 365 component continues running.

Or OneDrive might still be synchronising the file.

File Explorer could be generating a preview.

Security software could be scanning it.

A backup agent might be copying it.

Windows therefore sees the file as still in use, even though from your perspective nothing has it open.

Why Task Manager Doesn't Always Help

Task Manager is useful when you already know which application is responsible.

If Word is frozen, finding WINWORD.EXE isn't difficult.

File locks become more complicated when the responsible process is something unexpected.

It could be:

• File Explorer
• OneDrive
• Windows Search
• Microsoft Defender
• third-party endpoint protection
• backup software
• a PDF preview handler
• Outlook running in the background
• a Microsoft 365 component
• an application updater
• accounting software
• a database application
• a Windows service
• software running under another signed-in user

The process name may bear little resemblance to the application you recognise.

Instead of terminating processes until the file suddenly works, search for the handle itself.

Method 1: PowerToys File Locksmith

For most Windows 11 users, File Locksmith is the easiest place to start.

File Locksmith is part of Microsoft PowerToys and integrates directly with File Explorer. Microsoft describes it as a utility for identifying which processes are using selected files or directories.

Step 1: Enable File Locksmith

Open Microsoft PowerToys.

Find:

File Locksmith

Make sure it is enabled.

If you don't already have PowerToys, obtain it from an official Microsoft source.

Step 2: Find the Locked File

Open File Explorer and locate the file or folder Windows refuses to move, rename or delete.

Right-click it.

On Windows 11, you may need:

Show more options > Unlock with File Locksmith

Microsoft confirms that File Locksmith can examine individual files as well as directories and their contents.

Step 3: See What's Using It

File Locksmith scans accessible running processes and displays those currently using the selected item.

Depending on the process, you can see information including its name, PID and user.

You might immediately discover something obvious such as:

WINWORD.EXE

EXCEL.EXE

OUTLOOK.EXE

OneDrive.exe

explorer.exe

But don't assume an unfamiliar process is malicious or unnecessary.

Find out what it is first.

Step 4: Try “Restart as Administrator”

Sometimes File Locksmith reports nothing even though the file remains locked.

That doesn't necessarily mean the lock has disappeared.

By default, File Locksmith cannot inspect every process running with different or higher privileges.

Microsoft therefore provides:

Restart as administrator

This allows File Locksmith to inspect processes it couldn't access initially.

This can matter when the file is being used by:

• an elevated application
• security software
• a backup service
• a Windows service
• software running as another user

Try the elevated scan before concluding that File Locksmith can't find the culprit.

Step 5: Don't Immediately Press End Task

Finding the process is only half the job.

Suppose File Locksmith says:

OneDrive.exe

That doesn't necessarily mean OneDrive is broken.

It may simply be synchronising the file.

Likewise, security software might be performing a legitimate scan.

Your first response should therefore be:

Why does this process have the file open?

Try to close or stop the activity normally.

For example:

• close the document properly
• allow synchronisation to finish
• exit the application
• close File Explorer's Preview pane
• wait for a backup to complete
• close the application from its notification-area icon

Only terminate the process when you understand the consequences.

Microsoft's File Locksmith does provide an End task option, but ending a process can also release unsaved work or interrupt whatever operation it was performing.

Method 2: Microsoft Sysinternals Process Explorer

When File Locksmith doesn't provide enough information, move to Process Explorer.

Process Explorer is part of Microsoft's Sysinternals suite.

Microsoft describes it as a utility for seeing which handles and DLLs processes have opened or loaded. The current Process Explorer release continues to provide exactly this functionality.

Step 1: Run Process Explorer as Administrator

Download Process Explorer from Microsoft and extract it.

Run the appropriate Process Explorer executable.

For a thorough investigation, right-click it and choose:

Run as administrator

This gives Process Explorer greater visibility into processes running with elevated privileges.

Step 2: Search for the File

Press:

Ctrl + F

or select:

Find > Find Handle or DLL

Enter a distinctive part of the filename.

For example, if Windows refuses to move:

C:\Users\Carl\Documents\Customers\Budget 2027.xlsx

searching for:

Budget 2027.xlsx

may be enough.

For a locked folder, try searching for a distinctive part of the folder path.

Process Explorer searches its handle information and shows matching processes.

Step 3: Examine the Process

Double-click a search result.

Process Explorer takes you to the relevant process.

Now investigate it.

Look at information such as:

• process name
• PID
• user
• parent process
• executable location
• description
• company
• digital signature

This is much better than seeing an unfamiliar executable in Task Manager and guessing what it does.

File Explorer Is Holding the File

One common culprit is:

explorer.exe

File Explorer can interact with files while reading metadata, creating thumbnails or displaying previews.

Try disabling the Preview pane:

File Explorer > View > Show > Preview pane

Close the File Explorer windows accessing the location and try again.

If necessary, Windows Explorer itself can be restarted through Task Manager rather than rebooting the entire PC.

OneDrive Is Holding the File

Another common result is:

OneDrive.exe

If the file is stored in OneDrive or a synchronised SharePoint library, check the OneDrive status icon.

It may be:

• uploading the file
• downloading it
• processing changes
• resolving a synchronisation conflict

Allow the operation to finish where possible.

If necessary, briefly pausing synchronisation may allow a file operation to complete.

But don't make repeatedly killing OneDrive your standard solution.

If OneDrive constantly locks the same files, investigate why.

Word or Excel Is Still Running

Closing the visible window does not always guarantee the process has completely exited.

Process Explorer might reveal:

WINWORD.EXE

or:

EXCEL.EXE

still running.

Before terminating it, make sure another document isn't open and that the user doesn't have unsaved work.

This matters particularly on shared or Remote Desktop environments where several applications may be running under the same session.

Security Software Has the File Open

Microsoft Defender or another endpoint-security platform may temporarily open a file while scanning it.

Usually the sensible solution is:

wait.

A security scan normally finishes and releases the file.

Do not routinely terminate endpoint-security processes just to move a document.

On a managed business PC, doing so could weaken security controls or trigger alerts.

Backup Software Has the File Open

Backup applications may similarly access files while creating or verifying backups.

If the process is legitimate, let the job finish.

If a backup application constantly holds files open and interferes with normal work, investigate the backup configuration rather than continually killing the process.

Windows Search Is Using It

Windows Search may inspect new and changed files so their contents can be indexed.

This is usually temporary.

If Windows Search repeatedly interacts with the same location, investigate the indexing behaviour rather than permanently disabling Windows Search as a first response.

Bonus Method: Use Resource Monitor Without Installing Anything

If you don't have PowerToys or Process Explorer available, Windows includes another useful diagnostic tool:

Resource Monitor

Press:

Windows + R

Enter:

resmon

and press Enter.

Open the:

CPU

tab.

Find:

Associated Handles

Use the search box to enter part of the locked filename or folder name.

If a matching handle is found, Resource Monitor can help identify the process and PID responsible.

Resource Monitor isn't as powerful as Process Explorer, but it is useful because it's already part of Windows.

Once you identify the process, use the same rule:

Understand what it is doing before terminating it.

Advanced Method: Sysinternals Handle

Administrators who prefer command-line tools have another Microsoft option.

Handle is a Sysinternals utility specifically designed to display information about open handles and identify which programs have files open.

After opening an elevated Command Prompt or PowerShell window, Handle can be used to search for a filename or part of a path.

For example:

handle "Budget 2027.xlsx"

This is particularly useful for:

• IT administrators
• remote troubleshooting
• servers
• scripted investigations
• machines where a GUI tool isn't convenient

Handle requires administrative privileges.

Should You Force-Close an Individual Handle?

Process Explorer and Handle expose considerably more power than ordinary Task Manager.

That does not mean you should use all of it.

An advanced user might think:

Instead of terminating the program, I'll just force the individual handle closed.

That can be risky.

The application that created the handle expects it to remain valid until it closes it normally.

Forcing it closed underneath the application can lead to:

• crashes
• corrupted files
• lost changes
• unexpected application behaviour
• system instability

Microsoft's Sysinternals documentation for Handle explicitly warns that closing handles can cause application or system instability.

So use this escalation order:

Identify the process → understand why it has the file → close the application normally → wait for legitimate activity to finish → terminate the process only when justified → force-close an individual handle only when you fully understand the consequences.

What If Another User Has the File Open?

On a shared PC, Remote Desktop server or other multi-user system, the process holding the file may belong to somebody else.

That is another reason an ordinary File Locksmith scan might initially miss it.

Before terminating the process, check whether another user is actively working with the file.

Killing their application could destroy unsaved work.

In a business environment, determine who owns the process first.

What If the Lock Keeps Coming Back?

A one-off file lock is normal.

A file that becomes locked repeatedly deserves investigation.

Ask:

• Is OneDrive repeatedly failing to synchronise it?
• Is security software repeatedly rescanning it?
• Is an application crashing without closing properly?
• Is a preview handler malfunctioning?
• Is backup software repeatedly accessing the location?
• Is a database application deliberately maintaining the lock?
• Is another user or service accessing the file?
• Is the application poorly designed?

Repeatedly killing the locking process treats the symptom.

Find the reason the handle keeps returning.

When Restarting Windows Is Reasonable

Restarting the PC often clears a file lock because Windows terminates the processes that own the handles.

But restarting should not always be your first diagnostic technique.

If the problem happens once and you need to get moving, restarting is perfectly reasonable.

If it happens repeatedly, restarting every time hides the evidence you need to diagnose the actual problem.

Use File Locksmith or Process Explorer before rebooting so you can see what is causing it.

What Not to Do

Avoid:

• terminating random Windows processes
• repeatedly killing OneDrive
• disabling antivirus protection
• permanently disabling Windows Search
• deleting files from Safe Mode without understanding the lock
• using unknown “unlocker” utilities from download sites
• force-closing handles without understanding the consequences

Microsoft already provides excellent tools for identifying file locks.

There is rarely a good reason to install an unknown third-party “file unlocker” simply to discover which process has a document open.

The Quick Troubleshooting Order

When Windows says a file is in use but you cannot find the program:

1. Close the application that was using it.
2. Wait a few seconds and try again.
3. Close File Explorer's Preview pane.
4. Check OneDrive or other cloud synchronisation.
5. Check whether a backup or security scan is running.
6. Use PowerToys File Locksmith.
7. Restart File Locksmith as administrator if necessary.
8. Use Resource Monitor if you want a built-in option.
9. Use Process Explorer for deeper investigation.
10. Use Sysinternals Handle for command-line troubleshooting.
11. Close the responsible application normally.
12. Terminate processes only when you understand the consequences.
13. Restart Windows if necessary.
14. If the problem keeps returning, investigate the underlying application or service.

Why This Matters More in a Business

A locked Word document is annoying.

A locked accounting database, shared company document or business application file can be considerably more serious.

Forcing a process to close without understanding what it is doing could interrupt:

• database writes
• backups
• file synchronisation
• security scanning
• document saves
• line-of-business applications

That is why the correct question isn't:

“How do I force Windows to unlock this?”

It is:

“Which process owns the lock, and why?”

Once you know that, the correct fix is usually much clearer.

How Hamilton Group Can Help

Hamilton Group helps businesses diagnose Windows problems without relying on guesswork or repeatedly rebooting computers.

We can assist with:

• Windows 11 troubleshooting
• locked files and folders
• Microsoft 365
• OneDrive and SharePoint
• Windows performance problems
• Microsoft Intune
• endpoint security
• backup issues
• business application problems
• remote and onsite IT support

If a locked file is a one-off problem, Microsoft's tools can usually identify it quickly.

If the same file, folder or business application continually becomes locked, the better solution is to investigate why the process keeps holding it open.

Visit or call 0330 043 0069 to speak with Hamilton Group about Windows and business IT support.