Jump to content

Sky Slate Blueberry Blackcurrant Watermelon Strawberry Orange Banana Apple Emerald Chocolate
Photo

Who Lock Me? - Shows processes accessing a file

Started by Thalon , Jul 06 2007 08:56 AM

  • Please log in to reply
7 replies to this topic
Thalon
  • Members
  • 641 posts
  • Last active: Jan 02 2017 12:17 PM
  • Joined: 12 Jul 2005
I'm shure you know that nasty error-message "Can't delte file, because it is already in use" when trying to delete a file or folder - but their is no usable information!

With Who Lock Me? you can find out which process does bug you so much!

Thalon

Btw: Does anybody know how this can be accomplished? (API)
Would be very usefull for some scripts or our developed software...
#1 - Posted 06 July 2007 - 08:56 AM
Sean
  • Members
  • 2462 posts
  • Last active: Feb 07 2012 04:00 AM
  • Joined: 12 Feb 2007

With Who Lock Me? you can find out which process does bug you so much!

I think Unlocker is more popular one these days. BTW, my favorite one is OpenedFileView, and the famous Sysinternal's Process Explorer. Handle.exe from the same one also can be handy.

Does anybody know how this can be accomplished? (API)

AFAIK, You have to write a driver as you need to access the kernel memory.
#2 - Posted 10 July 2007 - 10:56 AM
Thalon
  • Members
  • 641 posts
  • Last active: Jan 02 2017 12:17 PM
  • Joined: 12 Jul 2005
Thanks Sean. OpenedFilesView seems to be very interesting :)
The main-difference I can see is that "Who Lock Me?" does check a special file (can be done via Context-Menu from Explorer) and OpenedFilesView does have a search for all opened files...
So they may co-exist on my pc in love :)

Thalon
#3 - Posted 11 July 2007 - 07:07 AM
BoBo¨
  • Guests
  • Last active:
  • Joined: --

Locked Files Command-Line Information
-------------------------------------

* run lfcmd.exe witout parameters at a Command Prompt to learn about its syntax

* The source and target paths are optional if the /pending parameter is
specified otherwise at least the source path is required.

* If a source path is specified but not the target path then the source
file or folder will be deleted.

* Return codes (ERRORLEVEL)

Here is the list of possible returns code reported by the Locked Files
Command-Line version. The wizard always returns 0.

0 = success
1 = initialization failed
2 = syntax error
3 = failed to gather pending operations from the system
4 = the source path does not exist
5 = could not add item(s) to processing list
6 = source and destination paths must be on same drive
7 = source and destination cannot be the same
8 = unsupported operation
9 = downgrade not allowed
10 = operation failed
11 = reboot failed. Some pending operations are queued.

[More..]

8)
#4 - Posted 25 July 2007 - 05:52 AM
BoBo¨
  • Guests
  • Last active:
  • Joined: --

Inuse.exe provides individuals and administrators with "on-the-fly" capability to replace files that are currently in use by the operating system. Although this behavior is generally accomplished by running a program's setup program or a service pack's upgrade program, the setup and upgrade process tends to replace multiple files. However, for troubleshooting purposes, you may need to replace an individual file on your computer versus an entire set of files. The Inuse program provides this level of administrative flexibility.

You can obtain InUse from the following Microsoft Web site:
http://support.microsoft.com/kb/927229


#5 - Posted 25 July 2007 - 05:56 AM
BoBo¨
  • Guests
  • Last active:
  • Joined: --

Sometimes, you try to delete a file and receive access violation or file in use - errors. To successfully delete a file, you will need to identify the process which has locked the file. Kill the process first and delete the particular file. To know which process(es) has locked a file, you may use any of the third-party process viewers. One such utility is available in the Windows 2003 Resource Kit Tools collection, free download from Microsoft site. You can use this in Windows XP as well.

OH.EXE from Windows XP Resource Kit Tools
Download Windows Server 2003 Resource Kit Tools

Once installed, reboot Windows and use the Oh.exe (Open Handles) command-line tool. For exact parameters, open Help and Support center and type-in OH. The following example shows how to find the Process(es) which have locked the file "INBOX.DBX".

Open a Command Prompt window and type:

oh inbox.dbx >C:\Output.txt

Wait for few seconds for the command to complete and open the file C:\Output.txt using Notepad. There you can see the process names which are currently using the Inbox.dbx file.

[More..]

8)
#6 - Posted 25 July 2007 - 06:09 AM
BoBo¨
  • Guests
  • Last active:
  • Joined: --

Ever had an annoying message given by Windows?

It has many flavors:

Cannot delete file: Access is denied
There has been a sharing violation.
The source or destination file may be in use.
The file is in use by another program or user.
Make sure the disk is not full or write-protected and that the file is not currently in use.

Unlocker is the solution!

1. Simply right click the folder or file and select Unlocker
2. If the folder or file is locked, a window listing of lockers will appear
3. Simply click Unlock All and you are done!

[Unlocker]


#7 - Posted 25 July 2007 - 06:15 AM
yuricurri
  • Guests
  • Last active:
  • Joined: --
this is what i got after installing wholockme, from that link.
trojanclicker:win32/yabector.b
#8 - Posted 18 January 2010 - 09:32 AM
Back to Utilities
  1. AutoHotkey Community
  2. → General
  3. → Utilities