OC v3 apparently "hanging" USB Eject requests...

[M R]

It appears that OC is hanging USB Eject requests by staying resident in memory in order to facilitate faster starts...With that said, I finally found a workaround:

1. Open the Event Viewer by typing “Event Viewer” in the Windows Start menu (you can also press Windows + R and type event.vwr and press Enter).
2. Navigate to Windows Logs and then to System.
3. Click on Filter current record.
4. In “Event IDs” type: 225 and click OK.
5. Done. This will display the kernel warnings indicating the name of the responsible process.
   
6. Terminate the OC process

Will OC v4 be continuing to do the same?

Please advise...

Thanks in advance...

[OneCommander Support]

In v3 you need to close active tabs showing contents of that drive (inactive tabs don't matter) so changes watcher and some other processes wouldn't prevent eject. The v4 is already listening for system eject commands and closes tabs automatically. The .50 has additional fixes for that. 

[M R]

Thanks for the swift reply...Most appreciated!