Object Desktop doesn't start

Do you mean the Object Desktop Manager icon? Can you post a screenshot of the icon?

Hello,
Sorry to hear you are having issues. Also, need to know your Windows 11 full version and OS Build number. Please use Winver.exe.

Thank you.
Basj,
Stardock Community Assistant.

Version 23H2 (OS Build 22631.4249)

Please try this, uninstall Object Desktop, reboot, re-download ObjectDesktop from your account download page: https://store.stardock.com/myaccount/products. Install it, reboot again, retest and report back.

Thank you,

Basj,
Stardock Community Assistant

Unfortunately, following the above instructions, and in the exact order as above, Object Desktop still fails to start.

I assume, there was no error show up when you installed Object Desktop, yes? If no error and you do as the video show below. You don't get the Object Desktop configuration windows open?

Thank you,

Basj,
Stardock Community Assistant

Thank you. But there was no error message when Object Desktop installed. Doing as the video shows does not open the Object Desktop configuration windows or anything else:  nothing at all.

That is strange. If you have a Windows 11 Pro edition. Please try installing under Windows sandbox and see if the ODM open as expected in Windows Sandbox environment. https://forums.stardock.com/486084/fences-support-faq#sandbox.

Thank you,

Basj,
Stardock Community Assistant

I have only WIndows 11  Home.

If you go to "C:\Users\xxxxxx\AppData\Local\Stardock\ObjectDesktop"

replace "xxxxxx" with "Windows your account name" and look for "ObjectDesktopManager.exe". Double click on it. Does that open up ODM?

Thank you,

Basj,
Stardock Community Assistant

Again, thanks, Basj, for the suggestion. But I went there. Clicked on it. And, no, it didn't open up ODM.

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

Hi riggsappeal,

Sorry to hear you're having trouble. 

As basj had specified the file-path for the application in reply #12, please try going back there and right-clicking the ObjectDesktopManager.exe application.  From here, I'd like to know if selecting "Run as an Administrator" makes any difference.  A bit of a shot in the dark, but here's to hoping and leaving no stone unturned.

If this issue remains, please right-click the same application and instead select "Properties".  From here, go to the "Details" tab, and see if you can verify the File version for us. 

It will look like this:

Also, while this gets worked out, please keep in mind your access to all individually included software is also available through your Stardock account's products page.  You can try downloading and running one of these products, and it would be useful to know if you're having similar issues with using any other of the included software.

I hope this helps, please let us know.

Thank you and best regards,

Adam McGuinness
Stardock Customer Support Specialist

Thanks Adam.

First, running as administrator did not start Object Desktop.

Second, the version shown on my computer is the same one shown above.

Third, I did get Fences 5, Start11, and Groupy 2 to run on downloads from the Stardock website. So that will be helpful. I didn't try any others. Object Desktop still won't start and doesn't show up on the Windows Task Manager.

Brent Riggs

Well, at least you've got working software. You'll have to check versions manually against what's listed in you're account.

Wondering if there was ever a resolution to this issue,I've been having the same issue for month's and just living with it out of frustration.

Hello,
Sorry to hear you are having issues. I still can not reproduce this issue on my system. Need to know your full Windows Version and OS Build number. Please use Winver.exe to get it.

Thank you.
Basj,
Stardock Community Assistant.

Currently having the same problem described above.  

Edition Windows 11 Pro

Version 24H2

Installed on ‎7/‎7/‎2025

OS build 26100.4351

Experience Windows Feature Experience Pack 1000.26100.107.0

 I have tried everything outlined above and no luck.  I am also unable to locate objectdesktopmanager.exe in appdata/local.

Hello,
Sorry to hear you are having issues. Refer screenshot below. This is what you should see in that mentioned directory. If you don't see that when you finished installing ObjectDesktop. Something in your system or security system is blocking from it to get install properly.

Please refer to this guide: https://support.stardock.com/space/SHC/1419378826/The+Stardock+installer+failed 

Thank you,
Basj,
Stardock Community Assistant.

i am having a issue with OD too . It launches and there is no apps that show on it .  Using windows 10. my subscription doesn't expire until 2030 something. Shouldn't something show up here ? I wound be grateful for any help.

Hello,
Sorry to hear you are having issues. Please check if ObjectDesktop is listed in your product account page: https://store.stardock.com/myaccount/products. If so, try uninstall ObjectDesktop, reboot, re-download ObjectDesktop again from your account page. Install it, reboot and login ObjectDesktop into your account. Report back.

Thank you,
Basj,
Stardock Community Assistant.

it is in my products there are two one says classic Subscription and one that doesn't say that. Can you explain the difference?? ? I purchased several subscriptions a few years back until and mine expires in Expires on 2032-04-13. so i should be good. 

Please refer here for classics subscriptions description : https://support.stardock.com/space/SHC/1496285185/What+is+an+Object+Desktop+&+Subscription+Software.

For account question, it best if you raise support ticket using the link below, use the "Ask a Question" option. Include all information details. Remember to record down the ticket number for future reference if needed. Do not raise multiple ticket, that will make your ticket back to the end of the line. Send once and wait. Ticket will be answer by the order they send in.