This is a true story, and a cautionary tale for Windows users, everywhere.
How would you feel, on booting Windows (XP Pro) one day, if you got no Windows? Instead, you got a strange, never-before-seen system error message “You probably are missing a necessary root certificate”.
The experience surprised me, but I really should not have been. As a user, I have many years of experience with Windows machines behaving like Windows machines. But this was different– I was unaware of the source of the message, and the message, itself, was less than helpful.
Immediately, I began a web search for the message text, hoping to find information. During that process, all FTP, SMTP and POP3 connections were normal but port 80 (HTTP) was not. I was unable to reach more than a single URL per session. Once I had searched a website for information, I had to reboot, and resume my web search.
Over the next few hours, I managed to restore everything to normal– but not before I learned about root certificates and fixed the problem for good.
Here is how I ‘fixed” my problem– and a brief background. Three or four years earlier, I had purchased the “Pro” version of a firewall product called ZoneAlarm, and unlike some applications, I had no immediate plans to update ZoneAlarm, so long as it served my needs. After all, a firewall is … a firewall. So, I modified until my firewall ran as smoothly as I could wish, and turned my attention elsewhere.
But in 2009, that did not make CheckPoint software very happy. CheckPoint had just bought ZoneLabs, and soon it was clear the ZoneLabs customer definitely came last. ZoneLabs continued to send so many nagscreen messages about updating– none of them with any features I needed– that I finally used ZoneAlarm, itself, to block the ZoneLabs messages. As a customer with a paid license, I wanted to be left alone, and should have been, if ZoneLabs had any chance at all of keeping me as a customer.
ZoneLabs’ continued harassment to upgrade was the next-to-last straw, but what became the last was when I finally discovered ZoneLabs, itself, had caused the problem that effectively crashed my system. ZoneLabs had revoked the root certificate for ZoneAlarm Pro– or that was what the message seemed to indicate. A later visit to the ZoneLabs website confirmed my suspicion, and a ZoneLabs rep confirmed the message “You probably are missing a necessary root certificate” came from ZoneLabs. He was sorry, of course, but he had no other information except that I would have to upgrade my product. I no longer could use my paid, unlimited-term license for Zone Alarm Pro.
Sales harassment by ZoneLabs of its paid customer base was bad enough, but what was worst for the company was it apparently used a back door in its code to disable my ZoneAlarm Pro– this, with no prior notice, or basis for doing so. In other words, while ZoneLabs assured prospective upgraders about security of its products, it routinely denied users complete control over their own systems.
So, having resolved the mysterious origin of the screen message, I immediately moved on to a better firewall and AV combination (paid license), and lived happily ever after. But now that it is clearer than ever Windows is a vending machine for software companies, what is the recommended approach to using software whose root certificate– for any reason, known or unknown– appears not to work?
Even after purchase and installation of a duly licensed product, is my Windows perpetually at the whim of every software vendor whose product runs on Windows? Meaning, if I do not in any way extend my license by an “update” or “upgrade”, could the same thing happen again?
I use Windows, not to be captive of a Windows software vendor, but aspire to better results– like controlling my own system. Is that too much to ask of a Windows machine?.
At this point, I would welcome reader suggestions about a good policy and standard operating procedure for all Windows users facing root certificate and other product control issues. Such user-to-user solidarity is important– you could find yourself in the same situation, or already have.