Timeline for How can I find out what's blocking my device? (Sysinternals Process Explorer didn't help)
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 20, 2017 at 10:04 | history | edited | CommunityBot |
replaced http://superuser.com/ with https://superuser.com/
|
|
| Jan 14, 2014 at 21:57 | answer | added | Ryan Barton | timeline score: 0 | |
| Feb 29, 2012 at 16:30 | comment | added | Oliver Salzburg | Using Process Explorer you can easily determine what services are run by that service host by simply hovering with your mouse over the process with that PID (1020). | |
| Feb 29, 2012 at 16:28 | vote | accept | Amelio Vazquez-Reina | ||
| Feb 29, 2012 at 16:21 | comment | added | EBGreen | Try Handle -c 1020 | |
| Feb 29, 2012 at 16:07 | history | edited | Amelio Vazquez-Reina | CC BY-SA 3.0 |
added 697 characters in body
|
| Feb 29, 2012 at 15:32 | comment | added | EBGreen | eSATA is not USB also. | |
| Feb 29, 2012 at 15:09 | answer | added | Alan B | timeline score: 2 | |
| Feb 29, 2012 at 15:04 | history | edited | Amelio Vazquez-Reina | CC BY-SA 3.0 |
added 257 characters in body
|
| Feb 29, 2012 at 14:22 | comment | added | Oliver Salzburg |
Maybe it's not being accessed through the drive letter, but through the unique device identifier. Use mountvol to determine it.
|
|
| Feb 29, 2012 at 14:18 | history | asked | Amelio Vazquez-Reina | CC BY-SA 3.0 |