Object Desktop - silent crash

from Stardock Forums

I just renewed my sub as I realised I let it lapse. However, I was unable to sign in to Object Desktop - checked firewall, not that. So I re-installed it completely, and now... it won't even launch.

Inspecting event viewer, I see the following:

Code: xml
  1. Application: ObjectDesktopManager.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at Object_Desktop_Manager.MainWindow+d__11.MoveNext() at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.b__6_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run(System.Windows.Window) at Object_Desktop_Manager.App.Main()

and

Code: xml
  1. Faulting application name: ObjectDesktopManager.exe, version: 4.1.7342.25505, time stamp: 0x5e3db612 Faulting module name: KERNELBASE.dll, version: 10.0.19041.3208, time stamp: 0xbc1cd7c0 Exception code: 0xe0434352 Fault offset: 0x0013d902 Faulting process ID: 0x15cc Faulting application start time: 0x01d9c94cd7f39427 Faulting application path: C:\Users\Chris\AppData\Local\Stardock\ObjectDesktop\ObjectDesktopManager.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report ID: 1f27e1d5-2bec-4972-8f90-a6e7a15d1722 Faulting package full name: Faulting package-relative application ID:

Only thing I did was uninstall, reboot, re-install. The previous not-logged-in version at least opened...

 

Ideas?

object desktop
17,001 views 8 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

+1 Loading…
Reply #2 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

Are you full up-to-date with your .Net installations? Generally, a Windows update will ensure that you are.

Sean Drohan
Stardock Product Lifecycle Manager

 

Start11 - Customize the Start Menu and Taskbar in Windows 10/11.
Reply #3 from Stardock Forums Top

Yep, also ran the .NET repair tool - finds no problems. Other .NET apps running fine too.

edit: also, sfc and dism repairs etc, no issues.

Reply #4 from Stardock Forums Top

Quoting chrisdowns, reply 3

Yep, also ran the .NET repair tool - finds no problems. Other .NET apps running fine too.

edit: also, sfc and dism repairs etc, no issues.

Well, something is killing it, however, that could take time to find and resolve.  I suspect you have instead gone to your account page to get your products, yes?

https://store.stardock.com/myaccount/products

Sean Drohan
Stardock Product Lifecycle Manager

 

Reply #5 from Stardock Forums Top

Quoting sdRohan, reply 4
Well, something is killing it, however, that could take time to find and resolve.  I suspect you have instead gone to your account page to get your products, yes?

https://store.stardock.com/myaccount/products

Yes, I think next I will try erasing all trace of it manually, and also removing Fences 4 (which has remained installed the whole time), then start fresh.

I will update here.

Reply #6 from Stardock Forums Top

Ok, so I removed all trace (incl settings!) of Stardock products and started again.

ObjectDesktop dies very fast, same fault as before - gets as far as drawing this window:

Fences 4 - individual install, went flawlessly. Works fine.

It appears I can use individual programs, just not the Object Desktop manager. I have no extra information in that regard. Perhaps if someone can make an older release available to me to try?

Reply #7 from JoeUser Forums Top

The applications are so easy to manage via the individual downloads that it may be more trouble than it's worth to try to get ODM working.  There is only marginal convenience in using ODM even when it works fine.  It has been problematic for many people for a long time now.  I think most of the individual apps have update notification toggles if that's important to you, but I just visit my SD account every once in a while to check for new versions.

0.02

Reply #8 from Stardock Forums Top

Quoting Daiwa, reply 7

The applications are so easy to manage via the individual downloads that it may be more trouble than it's worth to try to get ODM working.  There is only marginal convenience in using ODM even when it works fine.  It has been problematic for many people for a long time now.  I think most of the individual apps have update notification toggles if that's important to you, but I just visit my SD account every once in a while to check for new versions.

0.02

While there are issues with ODM that we are (over) due to address, this would not be a known one.  That said, this is sound advice as there are reliable sources that replicate most of what ODM offers.

Sean Drohan
Stardock Product Lifecycle Manager