Jöran Malek

Not entirely sure what's wrong, as I don't see this behavior here. Steps are exactly? - Download files one-by-one until reaching the warn threshold (`20`) - Dialog isn't responsive anymore

Maybe related: Microsoft Store diagnostics: ``` application_hang_endtask_hungthreadisidle_cfffffff_cyberduck.exe!xamlgeneratednamespace.generatedapplication+__c._offthread_b__0_0 ``` |Frame|Image|Function|Offset| |-|-|-|-| |0|win32u.dll|ZwUserGetMessage|0x0000000000000014| |1|user32.dll|GetMessageW|0x0000000000000022| |2|-|-|0x000000000018326D| |3|-|MS.Win32.UnsafeNativeMethods.GetMessageW|0x0000000000000012| |4|-|System.Windows.Threading.Dispatcher.GetMessage|0x0000000000000068| |5|-|System.Windows.Threading.Dispatcher.PushFrameImpl|0x00000000000000AF| |6|Cyberduck.exe|XamlGeneratedNamespace.GeneratedApplication+__c._OffThread_b__0_0|0x00000000000000CD| |7|-|System.Threading.ExecutionContext.RunInternal|0x0000000000000108| |8|-|System.Threading.ExecutionContext.Run|0x0000000000000015| |9|-|System.Threading.ExecutionContext.Run|0x0000000000000055| |10|-|System.Threading.ThreadHelper.ThreadStart|0x0000000000000060| |11|clr.dll|CallDescrWorkerInternal|0x0000000000000083| |12|clr.dll|CallDescrWorkerWithHandler|0x0000000000000047| |13|clr.dll|MethodDescCallSite::CallTargetWorker|0x00000000000000FA| |14|clr.dll|ThreadNative::KickOffThread_Worker|0x00000000002186D9| |15|clr.dll|ManagedThreadBase_DispatchInner|0x0000000000000033| |16|clr.dll|ManagedThreadBase_DispatchMiddle|0x0000000000000083| |17|clr.dll|ManagedThreadBase_DispatchOuter|0x0000000000000087| |18|clr.dll|ManagedThreadBase_FullTransitionWithAD|0x000000000000002F| |19|clr.dll|ThreadNative::KickOffThread|0x00000000000000E1|...

That's great and bad news. With the sample files, you are transferring smaller quantities of files at a time, right? How many more files per transfer does the real set...

Previous stack trace is probably not causing this issue here, more likely to cause [above](https://redirect.github.com/iterate-ch/cyberduck/issues/16442) issue.

If you want, there is a chance that the curent snapshot has this fixed. Can you update to the latest snapshot, and verify this please?