Need someone to lead product or development at your software company? I lead product and engineering teams and I'm looking for my next opportunity. Check out my resume and get in touch.

Winaso's terrible service

Freshness Warning
This blog post is over 12 years old. It's possible that the information you read below isn't current and the links no longer work.

As good as Dell was with their customer service, Winaso is bad. Dell offered support for a problem when I didn’t even go to to them for help and when the problem wasn’t their fault. Winaso won’t even respond to support requests from a paying customer.

My grandfather was a computing pioneer. He was one of HP’s early employees. He started building electronic calculators and moved on to writing software. He’s been having a problem with his computer where it reboots when he attempts to print anything from Outlook Express. His hardware tests fine, and he can’t find a solution for the problem, so he works around it.

Then he finds the exact same behavior when he’s using a windows system utility from Winaso. It’s scanning his system and in the exact same place each scan, his computer spontaneously reboots. So he sent them an email and asked what could be done.

After a few weeks, he heard nothing and asked again. A few weeks later, still nothing and he asked again. Still nothing. So I told him to forward his next message to them to me. At least we can warn people not to buy their products.

It’s possible this is a problem they can’t solve. After all, Microsoft support has no idea why Outlook would cause a computer to reboot. But he’s a paying customer—the least that Winaso could do is reply and tell him they don’t have a solution.

Gentlemen: This is the fourth time I’ve sent you a request for help for the same problem. You have not answered my previous requests and since I have paid for the Winaso program, I expect to at least hear from you about this problem.

A copy of the last email (number three) is shown below:

Gentlemen: I’m running WIN XP and IE6.0.

Winaso License Key: xxxxxxxxxxxxxxxxxxxx

I have e-mailed you about my problem twice and have not received a reply. I need to get this resolved.

When I’m in Outlook Express (6.0) and press the print icon or file/print keys, my computer reboots. I can print from the web, Microsoft Office, photo pgms, etc.

When I run Winaso Clean Registry the search will continue through each section until I get to either "Invalid ActiveX" or "Invalid Files Path". The program starts searching, the screen goes black, and the computer reboots. If I bypass these two sections I get a "No Errors" found.

Is there a way to isolate the file or files that cause your program to abort and reboot. Please help me solve this problem.

Jemaleddin
January 5, 2008 6:09 AM

I was really impressed with Dell in the previous post, but while Winaso's lack of any response is inexcusable, I have a hard time believing that these reboots are their fault. Given that he's getting reboots when printing from OE (You should really upgrade him to something better! For shame!), it's most likely a driver conflict. I mean, when Windows reboots for no good reason it's probably because it's a day ending in "y". Microsoft long ago traded stability for compatibility, and the answer to problems like this is to re-install windows and make sure your drivers are up to date. And obviously your dad knows that - that's why he's running a registry optimizer in the first place, to forestall the inevitable re-install. At some point he's going to make the same choice every other long-time geek is making: install Linux or buy a Mac.

Adam Kalsey
January 5, 2008 8:08 AM

He doesn't think these reboots are their fault either. He's hoping they can tell him what their program is doing at the moment it reboots. Apparently some text flashes on the screen near the progress meter in the moment before rebooting. He's hoping that he can find exactly what part of his system is causing this, since it's obviously not just Windows random instability. > OE (You should really upgrade him to something better! For shame!) I know. I've tried. He likes OE. And he's the unofficial tech support for most of his friends. They all use Windows and OE, so he does.

Jemaleddin
January 5, 2008 12:13 PM

Well, you just can't help people. But again, I'd be mad at MS for all of this - especially needing a program like WinASO to clean up their mess.

This discussion has been closed.

Recently Written

Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.
Developer Experience Principle 5: Easy to Trust (Oct 9)
A developer building part of their business on your product needs to believe that you're going to do the right thing for them and their customers.
Developer Experience Principle 4: Easy to Get Help (Oct 8)
The faster you can unblock a stuck developer, the better their experience will be.
Developer Experience Principle 3: Easy to Build (Oct 5)
A product makes it Easy to Build by focusing on productivity for developers building real-world applications.
How to understand your product and your market (Sep 30)
A customer development question you can ask to find out who your product is best for and why they'll love it.
Developer Experience Principle 2: Easy to Use (Sep 28)
Making it Easy to Use means letting the developer do everything without involving you.
Developer Experience Principle 1: Easy to Understand (Sep 25)
To create a great developer experience, you must strive for a product that is Easy to Understand. Reduce the amount of thinking that someone needs to do. Make their first encounter with your product clear and easy.

Older...

What I'm Reading

Contact

Adam Kalsey

+1 916 600 2497

Resume

Public Key

© 1999-2020 Adam Kalsey.