Version 2.0.0.1002 with x64 Windows 7
System Cleaner Flush and Empty gets an internal error message loop after "No" to a "Can be dangerous" message. By design in Debug Mode for safety. (Therefore should not loop in a future build when Debug Mode is not always active?). Tested without Debug Mode in v.2.0.0.1002. There were no warnings. Should there be? Why were the *.sys files not cleared?
Observations (and some issues (red)):
When the targeted directory structure contained *.sys files and some others:
*** The task ended normally. Everything in the target was cleared except the *.sys files and their paths.
*** There were no warning messages at all.
When the targeted directory structure contained folders and files with name matches to the Global Ignore List, and some others, but no *.sys files:
*** The task ended normally. Everything in the target was cleared except the GIL matches.
When the targeted directory structure contained folders and files with name matches to the Global Ignore List, and some *.sys files, and some others:
*** The task ended normally. Everything in the target was cleared except the GIL matches, and the *.sys files.
*** There were no warning messages at all.
All cases:
*** There were no "Can be dangerous" messages, and no internal error message loop.