Wholocks: incorrect reply for cmdGetLockedProcesses: PipeDoe
Posted: Apr 7th, 2012, 10:14 pm
Using USB Safely Remove 5.0.1.1164 and wholocks command (with -n XYZ) returns
Note that using the GUI I can see which processes lock the device.An error occured while searching for locking processes: The service returned inc
orrect reply for cmdGetLockedProcesses: PipeDoesNotExist