AllSync & AllDup

I was finally able to reproduce the issue and fix the memory leak! Thanks a lot for you feedback!

Dies ist mit AllDup nicht möglich.

I created a search result with 1086 groups of pictures. After arrow-keying down more than half the list the GDI-handles are only at 1543 and the value never reaches 1600 all the time.

The Unicode menu uses the KuShellExtension and the Non-unicode menu the FastExplorer ShellExtension.

Change the context menu option to "Context menu without Unicode support". (Options > General)

AllDup 4.5.52, Win10x64 GDI-Handles (Windows Task-Manager > tab details > column GDI-Objects): 1. after starting Alldup: 1079 2. after the scan is done: 1472 3. clicking on a group with 47 BMP-files: 1563 4. clicking on a group with 2 JPEG-files: 1500 5. clicking on a group with 10 PCX-files: 1518 6...

I do see that AllDup is still using 20-30% processor power while in that state. Could it be that it's actually calculating something? Yes. But without access to the progress window we dont know what AllDup currently is doing... You can use Sysinternals Process Monitor to check what the AllDup.exe p...

Hi. I'm having this same issue. After the search is completed, the AllDup window goes missing. ... I cant reproduce this using Win11: 1. I minimized the search result window while the scan is running 2. I restored the search result window by clicking on the AllDup icon in the windows task bar (afte...

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 ...

With the next update the focus will go back to the last highlighted node after closing the preview pane with the log.

AllDup documentation:

"If you delete files from archives and the file to be deleted is the only file in the archive, then the archive file is always deleted."

The focus is not lost when you show the log. The first node in the search result tree named "Search Result" is connected with the log. That's the reason why the first node will be activated when you show the log.

The name of the loaded search result is already shown at the title bar:

AllDup 4.5.50 - Search Result 'Hawaii Pics' ...

The 100% issue with the xHash will be fixed with the next update:

It looks like you have to restart your compter to fix this problem...