Thank you, Basj.

I tried what you suggested but it didn't help with the problem.
Do you want me to upload a fresh crash dump?

Please note that when I ran the purge utility for the second time (as I didn't take a screenshot the first time) it showed some syntax errors:

C:\Windows\System32>echo off

ERROR: The process "objectdock.exe" not found.

ERROR: The process "objectdocktray.exe" not found.

SUCCESS: The process "explorer.exe" with PID 13248 has been terminated.

ERROR: The system was unable to find the specified registry key or value.

HKEY_CURRENT_USER\Software\Stardock\ObjectDock not found

ERROR: The system was unable to find the specified registry key or value.

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Stardock\Misc\ObjectDock not found

ERROR: Invalid syntax.

Type "REG QUERY /?" for usage.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ObjectDock Plus not found

ERROR: Invalid syntax.

Type "REG QUERY /?" for usage.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ObjectDock Plus 2 not found

The directory is not empty.

Press any key to continue . . .

No, i just accepted the terms and let it install in the default location.

Hi rsadecky,

Sorry to hear about the trouble.  If you're still experiencing this, I have what maybe somewhat of a shot-in-the-dark suggestion.

One thing is I'm curious if you might still have a preexisting older version of ObjectDock installed somewhere. 

To try fixing:

Can you make sure you've completely uninstalled anything associated with "ObjectDock" before re-downloading the latest ObjectDock file from your account page?

When you reinstall, do this from a fresh download of the individual file link for ObjectDock 3 at https://store.stardock.com/myaccount/products , and not from the Object Desktop Manager.

Please let me know if that helps.

Adam McGuinness
Stardock Customer Support Specialist

Thanks for checking that.  Now that we know your software is current, the next fix you can try will help to isolate what has changed in the past week or so when you started experiencing the crashing. 

Please try the following:

• Navigate to C:\Users\YourUsername\AppData\Local\Stardock 

(*replace YourUsername with your Windows account username)

The folder located here named ObjectDockPlus contains all of your settings for ObjectDock. 

If you rename this folder to something else and start the program again, the next time you launch ObjectDock it will create a new folder with any changes you've made restored to their defaults, as I've done in the image below by renaming it to ObjectDockPlus.old

Now you can verify that the program works under these default settings. 

• Once you've confirmed that the program now runs normally, you can go back to check that renamed ObjectDockPlus.old folder.
  • Open up the file named CurrentTheme

Notice any sections here in your old file that include programs recently and added to your Dock? 

To demonstrate what I mean by this, I've provided a side-by-side comparison here, where I had Notepad pinned to my Dock in my old settings, and not in my new/default settings:

In your case, you can now try setting up your ObjectDock the way you had it using the above method. 

Close and reopen the software each time, and note which change makes the software crash.  We'll be interested to know what the result is and encourage you to reply with your findings.  Needless to say, however, for now you'll probably want to keep this off your Dock to avoid continuous crashes.

Adam McGuinness
Stardock Customer Support Specialist

Hi Adam, please note that I sent my previous reply before I read your most recent note.
Let me read it and follow the instruction there and I will come back with an update.

After reading the instructions, I identified the problematic dock item immediately.
It was the Pale Moon browser, but the issue was not with the application but with the arguments passed.
This is the killer line in the ini file (some values changed for privacy reasons):

Args="https://myapp.mydomain.com/sso/auth?site2pstoretoken=v1.4~B598DCD7~387E597D772E7C9C32C0159386E7802F67FC016DD64598F6791A3FA70E7F6F7FC7CA3530F2AACE5F8653FCDA26256DBB98E2B42538F812D4A14A4DA618CD028475F9D07BE041E3734D864851DCCEB94D344738883EA594689F34B4FC32DE40286592CB2F4A61E840006AD04C4789F3C8EA58792A83DBB6B1BB7D8781E844E6C8DF331205CC93E93F6C51BD2F19B3279B37F9F8C87CC81CC9ECB5374A815AFB23B1E641A47650B4F191F82AAA6175ED0016DF1507C7EB799DF67F2A9EBAAAB22BF840E07EA82FF859236672A0D2E628BA44081EA4F5EC1AE92AE852B9AD0E24873406B02091709621995322262C85AB3AEFDE6228AB4096A1C664A75AB7D3B317CA97EFB170FFC74C&ssousername=myusername&password=mypassword"

Previously, I had that those arguments in a batch file and my ObjectDock shortcut was pointing to the batch file.
I didn't like that a command window remained open every time I launched Pale Moon, so I added the arguments directly to the dock item properties.
The shortcut then worked as expected, until the next time I restarted Windows (after an update), at which point ObjectDock would no longer run.

Thanks for leading me to this.
I love your propducts and I was missing object dock badly for all those years running Windows 10.
The previous version was not working well on Win 10, but StarDock never claimed Win 10 support.
I was so happy to see v3 and its support for Win 11, so I could finally stop using the other dock/shelf solution that I never learned to like.

Best regards,
Rasto

P.S. You don't need to fix this for me