Sometimes cannot dismount USB drives about vmub HOT 11 CLOSED

Hi,

Yes, the problem seems to be specific to Windows 10 and its updates.
It could be a newly added system process or an old one loaded in a different way.

'Ignore' is dismounting the drive "cutting" all connections to apps/processes accessing the drive.
It's not suppose to be used every time because sometimes it will generate system instability and file system corruption on the drive.
Instead the user should debug and find info about the system process preventing the dismount.

Well, let's try to debug: please use this utility
to find out which system process is the culprit.

And post the results here please.

from vmub.

Ah OK - I didn't understand that, now it makes sense why it ignore fixes it - so 'ignore' = 'force dismount'

I will try the utility, but as luck would have it, even though I have had this issue fairly consistently for a month or so, I don't seem to be getting the issue today!

from vmub.

I experienced sometimes the issue by plugging the drive in the USB port and not using it for a while.
This way Windows and/or some utilities (like an antivirus) will "think" they can start background processes on the files/folders (from the volumes on drive).
For example indexing and antivirus scan.

Anyway I always deactivate indexing by default and it's no problem ignoring/terminating the indexing process.
And the antivirus scan can be stopped from the antivirus GUI.

from vmub.

from vmub.

Have you tried finding the system process with that utility...?

I'm sure you already know but you can use main menu >> View >> Use Quick Filter
Then you can type the path to the volume (for example 'd:\').
You'll get something like this:

from vmub.

from vmub.

I can't see any image in your post (just like on your previous post I can't see any image too). In fact the only image I can see in this thread is the one I posted.

Have you uploaded the pictures here on github or have you used another host?

from vmub.

Are you upset somehow?

If I've done something wrong then sorry, although github not displaying any of your images is not my fault...
And sorry for not giving you a solution faster but as you realize:

1. The real problem is from Windows and that system process. All I can do is find a better workaround than forcing the dismount each time. But, if it exists, it would help me if:
2. I would have all available information so viewing the images too.

Thank you.

from vmub.

Hi
Sorry for not replying. Due to:

1. Very busy with other family matters at the moment
2. Trying to reproduce the problem (which comes and goes) and then running tests to kill processes to see if I can get a better grip on the problem. I really have no idea what is causing it. If I use OpenFileView and kill all processes shown for the USB drive (same as in your screenhot), Windows still will not Safely Remove the USB drive. So something is obviously locking it but I have no idea what!
   The screenshots I sent you don't really help as the OpenFileView snapshot of a 'dismountable' drive shows the same open files for a non-dismountable drive. So I have had no clues to give you about where the problem might lie. I am running Comodo AV and I may try uninstalling it for a few days... Please be patient and I will try to investigate more.

from vmub.

I use Comodo Internet Security Premium 10 now but no such problem.
Oh, the Auto-Containment is set to off - if I won't disable it it would virtualize VMUB every time I recompile and test the latest changes in code.
But it's a good idea trying to uninstall it too.

You should try this app too: https://safelyremove.com/index.htm
It may show the process preventing the dismount.

Sorry, I was inpatient just because I was upset I can't help you (yet)...

from vmub.

closing as I have not seen this issue for many months now.

from vmub.