As a final update here (please close this thread): the fact that both Brad and Sean have responded to my issue and complaints both here and external to this thread, give me reassurance that their customer service is alive and well, but might require a bit more patience than I generally offer! Anyway, thank you both for considering (and not simply disregarding) my feedback, and working with me to address my original issue! John
johncampanie
Sean, I believe I've documented in enough detail my frustrations, and assume you should be able to track down where the process broke down. Asking anything more of me is an unrealistic expectation of your customer. I, too, have a job and a personal life. If you're offering a consultancy role, then by all means lay out the requirements and I'm happy to set aside some time. As it is, your example from 2021 bears little on today's case. If it was something easily addresse
Brad, I've spent waay more time on Stardock today than I'd planned, but one final comment because I realize this thread is primarily me bashing Stardock: Apart from my displeasure with the state of affairs on the administrative side, I am very grateful that Stardock exists and continues to publish its own software. It has long shored up the many and varied indiscretions of misguided Microsoft product managers for me, and it fills a niche that IMHO has not been filled b
Brad, Well, I didn't realize your role, so it says something that you're responding to my issue yourself; kudos for that! I would take my comments as one big data point indicating dissatisfaction with your automated customer service. I'm well aware of the travails of dealing with the uninformed masses, but I wouldn't think that was your primary customer base. In fact, I'd think that your suite of applications is directly targeted at the power user. Balancing the desire
Brad, While it's very kind of you to attempt to assist here, and I'm sure you're not responsible for the direction Stardock has taken with customer service, I am rightfully annoyed when an hour of my day is wasted with what should be a 2-minute phone call. When I attempted to purchase a second Object Desktop license under my original email address, the dialog indicated an Object Desktop license already existed. I'm not going to try to re-trace my steps for you he
I'm a long-time (well over a decade) customer of Stardock. I absolutely love its product suite, but have had to go through the many, many hurdles instituted by changing product registrations. This has left me with dozens of purchases of Fences, Start(x) and other Stardock applications. I've went through both the time and monetary expenses through the years simply because I loved both the application quality and the small-outfit publisher experience of Stardock. Fast-forward ma
I have to agree with the general sentiment of this thread and regardless of what Frogboy says, the fact of the matter is that Stardock sees fit to change functional licensing policy mid-stream without notifying its users. And that on top of bundling Object Desktop (really?) and no release notes to reference, you'd think Stardock was a guy working out of his basement. I still haven't gotten the taste of that Impulse fiasco out of my mouth. I've also been using vario
Ditto on this. Love the product (and the previous version as well), but this is a particularly annoying issue when Remote Desktop sessions are involved (Win7 x64). Please be kind and update this forum entry with the patch in which the issue is fixed as I can't seem to find a mechanism to be notified on the thread itself. Thanks, John