Here are the known issues regarding FileSieve. See the complete list at the FileSieve GitHub issues page.
- Interface Stays Disabled After Processing
If you find that you cannot use the FileSieve interface after it has finished processing, then go to the Settings
window, select the Advanced tab and set the EnableTaskbarProgress option to False.
The problem appears to be related to displaying the current progress within the Windows taskbar for the FileSieve window if there are items to be processed by FileSieve but they have all been skipped.
- Memory Usage After Processing
After processing, memory usage will not reduce to pre-processing levels for a few minutes. This only happens on systems with a lot of free, unused memory.
- Losing Settings for a Missing Plugin
If you have previously configured a Method or Modifer plugin and its settings have been saved. Removing that plugin from your installation (eg. reinstalling Windows but forgetting to then install the plugin before running FileSieve) and then running FileSieve while the respective Profile still contains the plugin's settings will result in that plugin's settings (but not the Profile itself or any other settings) being cleared from the Profile.
To prevent this issue, please ensure you install all Method and Modifier plugins you typically use before running FileSieve.
- Tooltips contain a | Pipe Character
There are some tooltips in the main window that contain a title and description which are being delimited by a | character. This is due to a (currently-removed) feature that displayed enhanced tooltips. The tooltip had true header (title) text and a description below it but due to the tooltip not being finished, it was disabled.
The title|description format is still kept as it is unknown when the feature will be completed and reinstated.
If you have discovered what may be a legitimate issue, please use any of the contact methods within the Contact section to report it.