Please attach the crash report.

• On Windows. Please attach the file cyberduck.log and the crash reports saved in a folder named CrashReporter in the ​application support directory.
• On Mac. Please attach the crash report displayed when the application crashes.

Crash reporer

Top-level Exception
Type:        System.Runtime.InteropServices.COMException
Message:     The current process has used all of its system allowance of handles for Window Manager objects. (Exception from HRESULT: 0x80070486)
Source:      Cyberduck.Core.Native
Stack Trace: at Ch.Cyberduck.Core.TaskDialog.UnsafeNativeMethods.TaskDialogIndirect(TASKDIALOGCONFIG& pTaskConfig, Int32& pnButton, Int32& pnRadioButton, Boolean& pfVerificationFlagChecked)
   at Ch.Cyberduck.Core.TaskDialog.NativeTaskDialog.PrivateShow(IntPtr hwndOwner, Boolean& verificationFlagChecked, Int32& radioButtonResult)
   at Ch.Cyberduck.Core.TaskDialog.NativeTaskDialog.Show(IntPtr hwndOwner, Boolean& verificationFlagChecked, Int32& radioButtonResult)
   at Ch.Cyberduck.Core.TaskDialog.TaskDialog.ShowTaskDialog(TaskDialogOptions options)
   at Ch.Cyberduck.Core.TaskDialog.TaskDialog.Show(TaskDialogOptions options)
   at Ch.Cyberduck.Core.TaskDialog.TaskDialog.Show(Boolean allowDialogCancellation, TaskDialogCallback callback, Object callbackData, String[] commandLinks, TaskDialogCommonButtons commonButtons, String content, String[] customButtons, Icon customFooterIcon, Icon customMainIcon, Nullable`1 defaultButtonIndex, Boolean enableCallbackTimer, Boolean expandedByDefault, String expandedInfo, Boolean expandToFooter, TaskDialogIcon footerIcon, String footerText, TaskDialogIcon mainIcon, String mainInstruction, IntPtr owner, String[] radioButtons, Boolean showMarqueeProgressBar, Boolean showProgressBar, String title, Boolean verificationByDefault, String verificationText)
   at Ch.Cyberduck.Core.CrashReporter.Write(Exception e)
   at Ch.Cyberduck.Ui.Controller.MainController.ExceptionHandler(Object sender, ThreadExceptionEventArgs e)
   at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
   at System.Windows.Forms.Control.WndProcException(Exception e)
   at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
   at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
   at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
   at Ch.Cyberduck.Ui.Controller.MainController.Run(ICollection commandLineArgs)
   at Ch.Cyberduck.Ui.Controller.MainController.Run()
   at Ch.Cyberduck.Ui.Controller.MainController.Main()

What do I do to fix this? Replying to dkocher:

Can you please try if still see this issue with the current snapshot build by updating from within Cyberduck in Preferences → Update → Automatically check for updates in → Snapshot Builds.

I have applied the update. The program continues to crash. I will attach the report later today.

​https://docs.microsoft.com/en-us/windows/win32/sysinfo/user-objects

User interface objects support only one handle per object. Processes cannot inherit or duplicate handles to user objects. Processes in one session cannot reference a user handle in another session. There is a theoretical limit of 65,536 user handles per session. However, the maximum number of user handles that can be opened per session is usually lower, since it is affected by available memory. There is also a default per-process limit of user handles. To change this limit, set the following registry value:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\USERProcessHandleQuota

This value can be set to a number between 200 and 18,000.