Hello,
I have forward 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

Hello,

I saw your issue on my system. But, I was informed, I just need to close/exit Object Desktop Manager (ODM) by right click it on the taskbar tray. Once it was closed, no more ODM icon inside the taskbar tray area, restart ODM. It should restart/reset and refresh itself. It should by than display the correct version installed.

Thank you,

Basj,
Stardock Community Assistant

I had closed/exited ODM. I found the issue was solved after I had completely shut down the computer (not just reboot) for the night. The next day, I opened the ODM to check and it had corrected. At the time, that was what was bothering me. I had closed all programs and rebooted a couple times, and the anomaly persisted. In case anyone else has any problems...A shut down may help them. 

    Ugh!

    I'm having this exact problem right now! Your fix is to just "completely shut down the computer" Ladysarajane? Well, at least there is a fix. Thank you for letting other users know! If it doesn't work... I'll be back.

Hello,

Do know there is known issue on some Stardock products upgrade version shown not correctly in ODM. And I believe, they are working on it.

Thank you,

Basj,
Stardock Community Assistant

    This is good to know because just shutting it down did not work. Still reads 'update'. I will wait patiently. Thank you basj!

Or you can turn off update check temporarily.

Thank you,

Basj,
Stardock Community Assistant

I have the same problem, but I also suddenly can't install anything via the Object Desktop GUI as the program always says "Cannot find the install file. Please close and reopen Object Desktop and try again."
Nothing works to resolve that problem. I tried to install something else and there I have the same problem. Even restarting the computer doesn't change something.
I've installed the Start 11 Update manually now, but at the moment I would need to install every package manually. I can't find the download cache for Object desktop. Where can I find it, I would like to clean it.

Please refer here for the location where your downloads were saved.

https://forums.stardock.com/479831

Thank you,

Basj,
Stardock Community Assistant

I am experiencing this issue with Start11 and WindowBlinds 11. I will re-attempt installation after removal, but I wonder why newly-installed apps need updating. Shoudln't OD download the latest version automatically?

I just noticed different version numbers in the ToolTip that appears when I hover over the Update button in Object Desktop Manager.

Same issue on Windows 11. 

I as well am having this same issue with both Start11 as well as WindowBlinds11 in the Object Desktop console. I have tried to do everything I could think of to resolve the issue, such as deactivating the license, uninstalling, clearing the registry files, deleting temporary files, then reinstalling it with "Run as Admin" and I still can't seem to solve this issue. I am working on a Windows 11 machine with 12th Gen Intel Core i7-12700 processor and 32 GB of DDR4 ram. The issue is the same as mentioned above with Start11 wanting to update from v1.3.6 to v1.36 and WindowsBlinds 11 wanting to update from v11.0.1 to v11.01.00.

It's probably best to check the version number and download your software here: https://store.stardock.com/myaccount/products

You can compare the version installed on your system inside the app itself for comparison.

For testing I deinstalled Start11, deinstalled Object Desktop, deleted all Object Desktop downloads. Reinstall Object Desktop and then reinstalled Start 11 from Object Desktop.

It immediately tells me to update Start 11 from 1.3.6 to 1.36

For testing purposes I've installed the new beta and now Object Desktop states I should update Start 11 from 1.3.7 to 1.36
When I look into Start 11 and click there on info it states to be version 1.37 and not 1.3.7 so I checked the files. There I see that the Start11Config.exe has the file version 1.3.7.0 and not 1.37 as it should be as this is also the version in the program and also in the download list. 

So I assume Object Desktop reads the version number from the files. Those version numbers are all x.y.z and none of them is x.yz
Either Object Desktop needs to read the version number from the same spot the program itself or you need to change the version numbers of your files to solve this problem.

Object Desktop Manager is buggy on some (maybe a lot of) systems.  Simplest, most straightforward solution is per DrJBHL above.  Just download the individual apps & install/run them from there.  That has the additional advantage of preserving your access to them should you choose to let your subscription lapse at some point.  Trying to 'fix' ODM is almost always futile.  I would just uninstall it if it gives those false update prompts - you don't need it to use any of the Object Desktop apps.  0.02

An afterthought -

I love SD's stuff and have been here and a continuous user since 2001, but their system of versioning has never made sense.  I'm sure it does to them, but not to me.

Post deleted because my solution is apparently not approved by Stardock.

This has not been approved as a solution by Stardock Support.

Could you please be more specific as to why it is not an approved solution?  Thank you.

[quote who="dhawkins0331" reply ="19" id="3876690"]
Could you please be more specific as to why it is not an approved solution?  Thank you.
[/quote]

Simply because they haven't approved it. That doesn't mean you're right or wrong. It just has to do with the responsibility Stardock incurrs when it says, "Do it this way and not that way".

That isn't personal...it's simply a warning to folks who might have little or no experience in editing the Windows registry, which might cause them problems, or might alter/damage the software or their computer. 

Incidentally, even if one has experience and decides to edit the registry, it's a good practice to backup the registry and create a restore point before doing so.