Error Beam Is Currently Busy Try Again When the Previous Transfer Completed

The scenario we're about to innovate is an unbeatable classic for anyone working with Windows. You need to move, rename or delete a file and - as soon as you try to do that - you lot're greeted by the following popup bulletin:

File in Use. The activity can't be completed because the file is open in another plan.

Or peradventure this one:

The action cannot be completed because the file is open in SYSTEM.

If you're an experienced Windows user you most certainly know that, when you see something like this, information technology usually ways that at that place is a running application which however has that file opened in an sectional mode - thus locking it from any IO write operations: no rename, no movement and certainly no delete. Whenever that's the example, the set up is right around the corner: you close the offending application - be it MS Word, MS Excel, MS Access, Photoshop and so on - and so go back to the file and do whatever yous desire with information technology. Problem solved!

What to practise when there are no active applications that seems to be locking that file? As soon as you are sure about it you can focus your attention to other Windows processes, such as some active services that could have it open: Antivirus software, Database services, Source Control Managers, Software Optimizers, Backup Tools, Firewall/security systems and then on. Again, if you're a seasoned Windows user, y'all volition have no problem to effigy it out before long plenty.

Nevertheless there is always a pocket-size take chances that, later on you lot spent a reasonable corporeality of time checking and/or temporarily shutting downward your resident software, you would still accept absolutely no idea of what process is actually keeping that file open. Whenever this happens, y'all're going to equip yourself with a few freeware tools that might really assistance you fixing your issue for expert.

Solution #i (bad): Unlocker

If we don't want to bother about what's happening to our system and just want to release that damn file we can retrieve near trying to employ Unlocker, a freeware awarding made by Cedrick Collomb that could automatically fix your issue... or not! I personally don't recommend using this software for at least ii reasons:

1. Y'all won't learn annihilation from using that, including what process (or process concatenation) will be abruptly shutdown with the intent to free your file.
2. The program is freeware, only it carries a huge corporeality of bloatware you lot demand to opt-out from: doing that will even require some attention, considering the setup program will try to guide you into installing them and I but really don't like it.

Every bit a viable alternative yous could also try IOBit Unlocker, which is basically the IOBit endeavor to capitalize the "unlocker" make because the original writer didn't brand it into a commercial hit (yet). The software is also freeware and it gets the job done but like the former one.

Solution #two (good): Process Explorer

With Sysinternals Process Explorer (or simply ProcessExplorer) things start looking good. This small, yet great portable utility (no setup, simply download and run) allows you lot to see all the currently active processes inside your system, including the names of their owning accounts and a total listing of handles (files) that the process selected in the top window has opened, including (if we switch it to DLL style) the system DLLs: this basically means that we can fully sympathise what's going on, and which process is holding our files.

The tool besides features a powerful search capability that will quickly show y'all which processes have particular handles opened or DLLs loaded. This will permit u.s.a. to use it to easily ready well-nigh unwanted file locks in a matter of seconds: nosotros just have to search for the locked file, call back the process which is keeping the handle and close (or kill) it appropriately.

Solution #iii (great): Handle

SolutionExplorer is a corking analysis tool, yet information technology lacks some useful options to actually ready our specific issue: altough we can employ it to kill a whole process, it doesn't provide a way to release a specific handle: whenever we're dealing with files locked past processes we cannot kill, such as SYSTEM, this tin be a trouble. In order to reach such surgical consequence we need to get our hands to another great Sysinternals utility that goes by the proper noun of Handle .

Handle is basically the console version of ProcessExplorer: think of it similar a ProcessExplorer with command-line options instead of the GUI. This could make it less intuitive when we demand to investigate our organisation, yet it has extremely powerful tools when information technology comes to fix the bug we constitute.

The nigh common usage of Handle - for our specific scenario - is the following:

• Download Handle and unzip information technology into a folder of your choice.
• Open a command prompt  window with administrative priviledges and input the following command:
  Handle64.exe > output.txt . The tool will so create a list of active processes/handles and write the (huge) outcome into the output.txt file.
• Practise not close the command prompt , as you will need information technology again. Open the output.txt file with your favourite text editor and search for a row containing your locked file name. Once you lot notice it, await for the HEX number to the left and write it down: this is the ID of thehandle y'all need to close. Correct subsequently that, become up through the file until you lot reach the parent row, which contains the informations nearly the process which is holding that handle. Again, look for the small HEX number to the left and write it down: this is the ID of the process you'll need to apply in the post-obit footstep. As a side annotation: Arrangement process ID is usually 4, although information technology could vary in the future.
• Get back to the command prompt and endeavor to close the handle by typing the post-obit:
  handle.exe -c <handleID> -p <processID> , replacing the placeholders with the values y'all establish in the previous footstep.

If everything goes correctly, you will fix your problem without killing the process and - more than chiefly - without having to reboot the organization.

That's information technology for now: happy "handling"!

reyesdonentolon57.blogspot.com

Source: https://www.ryadel.com/en/unlock-file-handle-locked-system-active-process-windows/