I thought the screenshots and repros demonstrated the cause.
They showcase the symptoms, not the cause.
I've worked in the industry as a QA / SDET for over a decade.
Then I appeal to your analytical and observational training / experience. Regardless of the cause, there is a root system failure here that is not going to be addressed by working on any individual app at this point.
Could you please bounce this one off the dev's and QA's so they can attempt a repro debug the code?
Again, at this point, it's not the app we seem to be dealing with. If you cant run cmd.exe elevated, there is an OS issue, not an app issue.
Other people have had some similar issues, here are just a few results:
Was for WindowBlinds, from 2010 and the user never responded to the lead dev for that product.
Also for WB and from 2012. The user solved the problem on his own.
His report: 'Seems turning off UAC and my nortons made the problem go away!!! '
A web search of any app is going to showcase individual issues over time.
BTW, I never heard a response on how to Safely remove Object Desktop.
Because Object Desktop is not an app on its own, it's a collection of apps - there is no removing Object Desktop, there is only removing the individual apps.
qatestwck, I feel for your plight here, I really do, I just don't know that it was IP that caused it nor do I think focusing on it, as an app, is the right direction at this point.
Stardock Customer Service Manager