AllSync & AllDup

AllDup is Slow To Close, clicking the 'X' close button to close the program.

Takes a good 3 seconds before the UI drops off.
Win10, Ryzen 5 2600G, 8 GB RAM.


Open Alldup (4.31)
Click the 'X' to close the program
1-1000, 2-1000, 3-1000...
(GUI disappears)


Do others see similar?
(I'm not really familiar with Win10 or the machine in particular.)

---

On my XP machine, when I tell AllDup to close, it does so - instantly.
Edit: ... As it does on my Win7 machine.

Here AllDup closes instantly using Win10 Pro x64 Version 1809 Build 17763.379 inside a VM!

Odd.

Just tried a Dell Laptop.

Win10 1803 x64
i3 4030u, 6 GB RAM (so no powerhouse, but still...)

Same slowness as noted above.

A third computer.

Dell Inspiron desktop.
i5-6400, 12 GB, Win10 1709.

I see the same.

I MB video, .wmv, https://drive.google.com/file/d/1C6Y2Fh ... sp=sharing.
(The clicks are faint, but are there. Looks like you'll have to download it.)

(Initially open, then I click 'X' to close it [00:00:09 - 00:00:12].
Then I reopen it, & again click 'X' to close it [00:00:18 - 00:00:21].)


(I'm 0 for 3 with Win10 computers. None are mine. All are what I would think a "typical" user might be using, with no special setups, just "out of the box" systems one uses.)

Same delay on portable edition on i7 3770 32GB Win10 64.

At our Win10 computer it took several seconds to exit AllDup.
We found out that the cause was the Windows Defender that delayed the access to AllDup config file.
The solution was to exclude the file config4.ini in AllDup's application data folder.

These virus/malscanner slow down everything...maybe it could speed up the whole search procress if you exclude the complete application data folder.

Exclude instructions:

Go to Start > Settings > Update & Security > Windows Security > Virus & threat protection. Under Virus & threat protection settings, select Manage settings, and then under Exclusions, select Add or remove exclusions. Select Add an exclusion.

Sounds similar in concept to, Discord detecting Everything as a Game, where the file name happened to make a difference.


So maybe if instead of "config4.ini" it were named "testme.txt" (or whatever) that might subvert the issue (without have to wrangle with Defender)?

There is no -I [configuration file name, .ini] command line switch, otherwise I could test that idea with something like:
C:\> alldup.exe -I testme.txt
(to load a configuration file named, testme.txt - rather then the default config4.ini)

The next update enables the user to add certain file types to the Windows Defender exclusion list to prevent the file types being scanned by the Windows Defender.