When the file is occupied, first check and close the relevant programs and try to restart the computer; if it is invalid, use the task manager, resource monitor or Process Explorer to locate the occupied process, and forcefully terminate it by ending the task or taskkill command; for prevention, you need to develop good operating habits, avoid previewing or directly operating on mobile/network drives, and keep software updated.

When you encounter a prompt that "the folder or file has been opened in another program", this usually means that a running application or system process is occupying the file or folder, preventing you from deleting, moving, renaming, etc. The core of solving the problem is to find and close that "occupant".

When dealing with this problem, I usually start from the simplest and most direct way and gradually go deeper. The most direct way is to think about whether you have just opened a program, such as a document editor, image viewer or player. Many times, we just forget to close it. If there is no obvious procedure, I will try the following steps:

1. Close all related applications: For example, if you are trying to delete a Word document, then make sure that the Word program is completely closed.
2. Wait for a moment: After some programs are closed, their background process may take a few seconds to completely release the file handle. Give it some time.
3. Restart the computer: This is the most violent but also the most effective "panacea". Restarting will clear all processes in memory and usually solves most file occupancy issues. But it is not the most elegant solution.

How to quickly identify and close a file-occupying program?

My experience is that most of the time, file occupation is not a complicated virus or malware, but a "little negligence" in daily use. But if restart is not the first choice, or problems occur repeatedly, then we need some more refined tools.

The Task Manager (Task Manager) that comes with Windows is the first line of defense. You can pass

 Ctrl Shift Esc

• Processes tab: Here are all running applications and background processes. You can try to find programs related to your target file here, such as if it is a picture file, and see if there is any image viewer or editing software running. Select it and click "End Task". However, this method is a bit like finding a needle in a haystack, especially when the process name is not as intuitive.
• “Details” tab: This one is more professional. You can click on "Image Name" or "PID" to sort it and then search carefully. But again, it doesn't tell you directly which process occupies which file.

The Resource Monitor is the Resource Monitor . Enter in the search box of the Start Menu

 resmon.exe

• Under the CPU tab, find the Associated Handles section. Enter the full path or file name of the file you are occupied in the search box (e.g.

   C:\Users\YourName\Documents\myfile.docx

  ).
• All processes holding the file handle are listed. Once found, note its PID (process ID) or image name.
• Return to the Task Manager, switch to the "Details" tab, find the corresponding process, and right-click to select "End Task Tree" or "End Task". Please note that ending the task may cause unsaved data to be lost, so please think twice before operating.

Faced with stubborn file locking, what are the advanced methods besides restarting?

Sometimes, files are occupied very stubbornly, and ordinary methods don't work at all. At this time, my thinking will turn to more underlying system tools.

Process Explorer (from Microsoft Sysinternals suite) is my first choice. It is much more powerful than the task manager and provides more detailed process information.

1. Download and run Process Explorer (it is a portable tool that is installed without installation).
2. In the main interface of Process Explorer, click "Find" -> "Find Handle or DLL..." in the menu bar (or use it directly

    Ctrl F

   ).
3. Enter the full path or file name of the occupied file in the search box.
4. Process Explorer lists all processes that occupy the file handle. Select the corresponding row, and the window below will show which process is occupying it.
5. Right-click the process and select "Kill Process" or "Kill Process Tree". Again, this forces the process to terminate, make sure you understand the consequences.

If you can't even process Explorer directly, or if you want to try a more "technical flow" solution, you can consider using command line tools .

• Open the command prompt (CMD) or PowerShell for administrator permissions.
• Assuming you have found the process ID (PID) that occupies the file through Resource Monitor or Process Explorer, you can use

   taskkill

  Command to terminate it:

   taskkill /F /PID [process ID]

  For example:

   taskkill /F /PID 1234

• If you know the image name of the process (e.g.

   notepad.exe

  ), it can also be like this:

   taskkill /F /IM [Image Name]

  For example:

   taskkill /F /IM notepad.exe

   /F

  Parameters indicate forced termination. This trick is usually very effective, but it also comes with risks.

How to effectively prevent files from being accidentally locked by programs?

Instead of solving problems every time you encounter them, it is better to reduce the occurrence of such situations from the source. This is not only a technical issue, but also a habit of use.

• Develop the habit of closing programs in time: After using up a file or folder, make sure to close all relevant applications. This sounds simple, but many people often forget. For example, after editing the document, shut down the computer directly, instead of saving it first and then closing Word.
• Understand background processes: Some programs, even if you ostensibly shut down, their background services or processes may still be running, especially some cloud synchronization tools (OneDrive, Dropbox, Google Drive) or antivirus software. They may temporarily lock files for synchronization or scanning.
• Use the file preview feature with caution: Turning on the file preview pane in the file manager can sometimes cause the file to be locked because the preview program needs to read the file content.
• Avoid direct operation on mobile hard drives or network drives: especially when the network environment is unstable, opening or editing files directly in these locations will be more likely to cause the problem of untimely release of file handles. My suggestion is to copy it to the local area first, and then pass it back after editing.
• Regular updates to systems and applications: software bugs can sometimes cause file handles to not be released correctly. Keeping the system and commonly used software updated can reduce the occurrence of such problems.

After all, it is a common "little trouble" to be locked, but through some tools and good usage habits, we can completely "tamed" it. It reminds us that in the computer world, everything has its own rules, and understanding these rules can better control it.

The above is the detailed content of The folder or file has been opened in another program. For more information, please follow other related articles on the PHP Chinese website!