You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two "receive only"-folders on a removable USB disk. The folder watcher is disabled for both folders. However, even with the folder watcher disabled, it is impossible to safely remove the drive while SyncTrayzor is running.
To reproduce:
Create a folder on an USB drive
Set the folder as "receive only" (not essential to demonstrate the problem)
Disable the folder watcher in SyncTrayzor for the folder on the USB drive
Using the Windows 10 tray icon "Safely Remove Hardware and Eject Media", try to eject the USB drive with the Syncthing folder
Error message titled "Problem Ejecting USB Composite Device": "This device is currently in use. Close any programs or windows that might be using the device and then try again."
Terminate SyncTrayzor
Try ejecting the USB drive again --> Success
I suspect that SyncTrayzor needs to use some Windows api to register to receive a notification when a user tries to eject hardware. SyncTrayzor can then close all its relevant file pointers, if the user tries to eject a drive that SyncTrayzor is using, to allow Windows to eject the drive.
The text was updated successfully, but these errors were encountered:
ARF1
changed the title
SyncTrayzor prevents ejecting removable drives
SyncTrayzor prevents ejecting USB drive
Sep 21, 2023
I have two "receive only"-folders on a removable USB disk. The folder watcher is disabled for both folders. However, even with the folder watcher disabled, it is impossible to safely remove the drive while SyncTrayzor is running.
To reproduce:
I suspect that SyncTrayzor needs to use some Windows api to register to receive a notification when a user tries to eject hardware. SyncTrayzor can then close all its relevant file pointers, if the user tries to eject a drive that SyncTrayzor is using, to allow Windows to eject the drive.
The text was updated successfully, but these errors were encountered: