When will this be fixed?! I just saw other posts with the same problem from over 3 moths ago and this bug still occurs.

Same issue here. I emailed Customer Care and only 10 days later I received a very "encouraging" answer: my report was forwarded to their Development Team, but "a timeline for a response or resolution" cannot be provided. In other words, since you already paid for the program we don't care if it works properly or not. It seems that this is a problem signaled months ago, yet Stardock is too busy to solve it. And they have the nerve to continue to advertise Objectdock 2.2 as a program compatible with Windows 10. People should know that IT IS NOT, that this particular bug is very annoying, and that Stardock  doesn't care to fix it.  

Sorry, is this the alternate version for 'Sorry, we won't support you when you are using the current version of the world's most installed OS which we originally designed software for, and charged for it'? I see so many bugs and so little activity in actually fixing it. Maybe it's just me?

If that is so, you should clearly point out to ObjectDock not being ready for Windows 10. If you are still selling it, you should make customers aware of the possible and even likely buggyness of it on Windows 10, so no-one can complain in the end. I understand that you did not build it for Windows 10, but I would believe that when building software and charging for it (as opposed to 'free' and open-sourced software), you would either expect future OS support or - as you did with WindowBlinds - just declare non-compatibility and sell version n+1 as an upgrade. Or how would you think us, the ones having issues with ObjectDock, and there are several issues with Windows 10, as users report, to behave and act in the light of some forum replies, but no real solutions or sometimes even replies to issues described here, being given? Should we just learn to be more patient or to eventually say good-bye since we are using a 'Beta' OS?

I for one often get a freeze of ObjectDock which I can only escape through the process manager of a third-party program since ALL other windows are inaccessible, even newly launched ones including the usual Task Manager, and I got it on an aged upgraded Windows 10 as well as a freshly installed one, within the first few hours of operation. I could possibly live on for a while with ghost icons as described here or ObjectDock constantly forgetting about hiding the Taskbar or even forgetting the screen it is placed on (all problems described here already by others on this forums), but it is frustrating to have so many bugs (and one so severe) with an OS you more or less explain not to support, thus don’t make me believe you’re interested in fixing in a timely manner. Or am I just doing you wrong?

Okay, I understand that, and also know that not everybody has (the same) problems like some of us obviously do (not counting in the ones who do not complain, but still have it though). Still I think the best move would be for Stardock to warn users on the product page to be aware of possible/common problems when running OD+ (are you using plus?) on Windows 10 BETA ( ).

Yes, again you are 'doing us wrong'.

ObjectDock  IS supported in Windows 10 and, in spite of the OS itself potentially breaking things, particularly with forced updates without an option to refuse them, the program works for MOST people quite well.

The reason there is a SUPPORT Forum for Stardock's software is for people experiencing issues to seek assistance, not to do little more than troll their dissatisfaction with what may be [and likely is] a very specific and isolated issue with their particular OS configuration.

Instead they can open a support ticket with Stardock Support and obtain help with their particular issue/s.

It's again important to note that the correct procedure is to contact Stardock Support and open a ticket as although issues you have may appear to be similar to others the causes are not always the same.  Specific issues need specific response.

These Forums are for general feedback and/or assistance from the Community which might not always result in a solution...

I think Jafo's answers speak volumes about Stardock attitude toward its paying customers.

Start10 works fine with Windows 10. Many, many other programs far larger and more complex than ObjectDock work also fine with Windows 10. Clearly it is not Windows 10 causing the problems ObjectDock has. It is ObjectDock which is sold as "compatible with Windows 10" when IT"S NOT.

I opened a support ticket with Stardock Support a month ago: did I obtain any help with my "particular issue"? NOT AT ALL. Once they get your money you are on your own. Great company, great support. And if you get mad, they call you names instead to solve the problems.

I don’t know if it was one of yours, but there has been one comment here at the end of last year that was similar to yours that seems to have been deleted from the conversation about the fact that OD stopped working properly long before Windows 10, starting with 64bit, with no fix or even a statement provided up to date. My memory was a bit dull, but yes, my problems started long before Windows 10 as well, they only became more when Windows 10 arrived (and clearly I am not the only one with problems). 

Since Stardock began telling me I was trolling them and I should open up support tickets for issues existing since years (x64 problems) and already being widely covered here (while I believe in general direct support is really more helpful than posting on forums, especially when Stardock staff does not cover all the threads and issues reported here), I just moved forward to the only one real alternative to ObjectDock that has a yearly subscription, but one guy eager to care for his customers AND his product. I encountered a few minor bugs with it and had some suggestions and got the bugs fixed within days (!), without him whining about Windows 10 or, in one matter being the culprit, Google Chrome. Plus he enganged in a small discussion about usability of features and personal preferences. No dreadful hanging of docks, no ghost icons, no forgetting about screen positions or taskbar hiding settings, (and no accusing of trolling,) it just basically works. 

This only goes to say: Through a product as seemingly minor to you as ObjectDock and your non-forthcoming way of handling communications about missing bug fixes for the bespoke, you just lost a once more or less satisfied customer who had bought from you quite some licenses and license upgrades in the past, and I would not be so sure to assume I would still recommend you to friends and colleagues. Possibly you don’t care as much. 

If you feel that a product isn’t worth much effort anymore, you should rather discontinue it than handle it this way. If you think you don’t need paying customers, offer your software for free, so no-one can complain . 

PS: If you would accuse me of once again not being relevant to solving the problem, my post has two distinctively practical tips to help out:

1. Use another software
2. Save time and effort spent on Stardock (not) solving long-known and new problems and invest a few bucks for peace of mind. 

I would believe this is as practical and goal-oriented as it gets . 

Please elaborate on this alternative. I am running RocketDock (free) but find it lacking compared to ObjectDock. I'm open to alternatives. I pay for Object Desktop almost exclusively for ObjectDock, but find OD causing problems lately, especially Win 10 64.

If Stardock isn't reading here anyway, it can't hurt to mention the alternative. I, for one, won't renew ObjectDesktop unless I hear somewhere that OD is "fixed."

Tom

My mistake, I checked and I do have a separate ObjectDock license. So if they do fix it, I'm good!!

Now, for this alternative??

Somewhat ironically I got an email from Stardock about Object Dock just yesterday, rekindling my interest. Thought maybe it was a new version update, but alas, no. At least they know it exists. 

So really, what are all the alternatives to Object Dock?

Thanks, I'm already gone, but RocketDock leaves much to be desired so I've been toying with going back to OD and living with the admittedly minor annoyances!!