Find out which process is locking a file or folder in Windows

For Windows 7, 8 and 10 you can use the built-in Resource Monitor for this.

  1. Open Resource Monitor, which can be found by searching for resmon.exe in the start menu, or as a button on the Performance tab in your Task Manager.
  2. Use the search field in the Associated Handles section on the CPU tab
    pointed at by blue arrow in screen shot below.

In case it’s not obvious, when you’ve found the handle, you can identify the process by looking at the Image and/or PID column.

You can then close the application if you are able to do that, or just right-click the row and you’ll get the option of killing the process right there. Easy peasy!

Remark: The complete text and the picture above are taken from one of the answers to the question on
Some of the comments there claim that sometimes they could not find handles with Resmon but could find them with Process Explorer. Some others claim they could not find handles with Process Explorer but with Resmon.

I’d like to add, if you are looking for the directory C:\alpha\beta\gamma, you can enter in the search field
* gamma or GAMMA or \Gamma
* beta\gamma
* beta or \beta\
* C:\alpha\beta\gamma
* You cannot use slashes instead of backslashes.

Keywords: Block, Delete, Handle, Lock

Personal Kanban and Kanbanpad: Two Top Productivity Tools For Everybody

What are “Personal Kanban” and “Kanban”?

A Kanban is a special type of a to-do list. It has been invented by the japanese car-maker Toyota in the nineteen-forties to steer its production lines. It is truly time-tested.

0401-203731-Personal Kanban 101 _ Personal KanbanOver the years, the Kanban principle has trickled into the software development industry. And not long ago people found out that what they use in their bureaus or factory buildings could be used for their private tasks, too.

Hence Personal Kanban has been born. In its simplest form, a Personal Kanban looks like the image above. The image is from Jim Benson’s famous Personal Kanban site. Jim has probably written the first book about Personal Kanban and has held a talk about the system at Øredev.

What you see above is a to-do list with some special features.

  • Tasks are noted on Post-Its.
  • Every column denotes a certain state of the tasks in it.
  • The tasks or Post-Its travel from left to right.
  • You should be working only on tasks in the column Doing. This column is also often called Work in Progress.
  • The number of tasks in the column Doing or Work in Progress is limited. The limit number usually is well below ten.

That’s all.

Why Does Personal Kanban Help You?

Yeah, I know, this system looks very simple. It looks too simple. It looks like a to-do list and not much more. But great traits emanate from the easy rules.

  • By having a limit on Work in Progress, you need to think about prioritization automatically.
  • By limiting the number of your Work in Progress tasks, you are automatically focusing on finishing tasks before starting new ones.
  • Because many tasks are visible on the board, you are automatically identifying problematic spots. And you get a good overview of your workload in total.
  • In a strange way it is motivating to be able to move the tasks from left to right. The Done column helps you to feel good about having accomplished something.

All this will happen when you are using a Personal Kanban. You don’t even need to put special effort into it.


For three years now, I am doing my own Personal Kanban with a free web-based tool called Kanbanpad instead of a whiteboard and stickers. Some say that a web based kanban is lacking the visibility, touchability and realness of a whiteboard kanban.



Kanbanpad is shutting down in March 2015 ;-( For the moment, I am using Portable Kanban.

But there are these

Seven Advantages of a Web Based Personal Kanban Over a Whiteboard Kanban

  1.  You do not need to uglify some precious wall space in your flat with a whiteboard.
  2.  You can put stuff there that shall not be seen by everybody who enters your flat.
  3.  You can add as many notes as you need to a task.
  4.  When tasks are done, they are still available later. It is sometimes quite useful to re-check the notes of a task that’s already done.
  5. You can create as many tasks as you want.
  6. No blizzard of flying Post-Its after opening a window.
  7. And, obviously, you can access the board from every place where you have got a web connection.


This post has been on my list for a long time. Martin’s blog parade about My Best Hints for Productivity has triggered me to finally write it. Thank you, Martin.


What do you think of using a Personal Kanban? If you are already using a Personal Kanban, which type of tool do you use for it? I’d love to hear from you. Uuuund ich lese Kommentare auch gern in deutsch. 😉

Procdump: Creating Crashdumps Automatically

a) Sometimes, an application crashes on a test computer 😉  And sometimes this occurs immediately at startup, so that you don’t have time to attach windbg before to get a crashdump.

b) Sometimes, an application crashes, and immediately restarts on a test computer. This can be hindering the debugging. E.g. because it would be nice to look at the state of the databases at the time of the crash. And because you would like to have a crashdump.

There is a solution for both of these problems. Use the procdump.exe utility of Russinovich. You can attach it to your application immediately at startup and make creating crashdumps automatic.
I use a batchfile procdump.bat with this content:

procdump.exe -e -ma -x %1.exe %1.dmp

Then I open a commandline in the program folder where the app under examination resides (e.g. C:\Program Files (x86)\Xyz\App) and start the batch via

procdump.bat AppNameWithoutDotExe

When the application crashes now, a crashdump is written to the program folder, called AppNameWithoutDotExe_140304_161853.dmp or the like. The numbers contain date and time. At the same time, in the cmd window where you started it, there is written something like “The process has crashed. A dump has been written to …”

Procdump is something like a debugger and it attaches itself immediately to the app. Therefore debugging protection is triggered when you start to do something in your app that uses debugging protection.
Then, it may be that the app just silently closes. This is reflected in the cmd window by a line like “The process has exited.”

CPU Monitoring:
Before I forget it, procdump has another feature that may come in handy sometime. It can monitor an application for its CPU load and create a crasdump when the load gets too high.