Wholocks: incorrect reply for cmdGetLockedProcesses: PipeDoe

Post Reply
nobody
Posts: 2
Joined: Apr 2nd, 2012, 9:07 pm

Wholocks: incorrect reply for cmdGetLockedProcesses: PipeDoe

Post by nobody »

Using USB Safely Remove 5.0.1.1164 and wholocks command (with -n XYZ) returns
An error occured while searching for locking processes: The service returned inc
orrect reply for cmdGetLockedProcesses: PipeDoesNotExist
Note that using the GUI I can see which processes lock the device.
User avatar
Igor
Developer
Posts: 602
Joined: Nov 1st, 2007, 12:44 pm
Location: Saint Petersburg
Contact:

Re: Wholocks: incorrect reply for cmdGetLockedProcesses: Pip

Post by Igor »

nobody wrote:Using USB Safely Remove 5.0.1.1164 and wholocks command (with -n XYZ) returns
An error occured while searching for locking processes: The service returned inc
orrect reply for cmdGetLockedProcesses: PipeDoesNotExist
Note that using the GUI I can see which processes lock the device.
Please refer to this topic
Post Reply