Mumbling Microsoft Man and the Slow Repair
When learning a new language, you are bound to make mistakes. It’s expected and normal. But when you are in a world where you don’t understand a thing without an interpreter to help you find your way, you might become dazed, confused and a tad irritated after a while.
Such is the language of computer programming for me. Product Key IDs, Windows Installer corruption and the inability to update applications such as Skype, a lifeline for me in so many ways, are things that put me in a tailspin.
And so it was this week. That is, until Mumbling Microsoft Man came to the rescue. The support guy on the other end of the line spoke so quickly and unclearly that I literally only understood the first and last word of every sentence.
For the record, he told me I could use his last name here, but since we got on a first-name basis over the course of an intense three hour on-again, off-again mobile phone conversation, I decided to create a pseudonym for the purpose of this post.
It only seems fair.
After repairing what at first seemed like a minor missing link, Microsoft has gained enormous respect in my eyes. Admittedly, like a college student dabbling in drugs, sex and rock-n-roll, I have been known to dabble on the Dark Side (read: Apple products). Their graphics rock, the look and feel of them are appealing and the store itself makes me want to take my shoes off at the door and speak in hushed tones as I admire, well, everything. I love Apple products for their cutesy nature, their instantaneousness and their speed.
Yes, even in a blog about slow, speed is valued. But when push comes to shove and I really need to write, my PC stands like a lighthouse in the dark: solid, stark, simply there.
You can imagine my frenzy when my PC rejected any type of updates whatsoever. To make a long story short, an old registry sweeper application I stupidly downloaded had eventually erased an important product key that unlocked the mystery that is Microsoft-based computer programming.
Microsoft Man patiently began our session with a kind request for the Product Key ID. I gave him the wrong one. He patiently asked me to look on my computer tower, not my Home Office software packet. I got down on my hands and knees, owing him my own set of patience as I scanned all four dusty corners of it. Finally, with a shriek of delight, I found what he was looking for. After discovering how dirty my floor was, I pulled myself up from under my desk and waited for Microsoft Man’s next intelligent command. He logged into my computer via some secret remote program and I watched him whip around my computer screen like Super Geek trying to find the solution.
Forty minutes later, I was a liiiiiiittle less patient, understanding only half of what he was saying. What first came out of my mouth as, “I’m sorry. Might you please repeat that?” later morphed into, “Huh?” accompanied by a glazed look of the truly defeated.
But Microsoft Man would not be beaten. After an hour and ten minutes, we took a break. I headed for the kitchen, he to a colleague’s desk. I’m not certain whether he beat his head against it, but he came back to the second conversation sounding as even-keeled as ever.
I threw him a bone.
“Would you like to take a lunch break?” I suggested, secretly muting every time I took a bite of my Thai food.
“Not until this is over,” I heard him say.
He manually added some gibberish into an additional screen and by the third hour, we were speedily updating, reinstalling and generally smiling at the amazingness of Microsoft Man himself.
He kindly suggested I fill out the customer satisfaction evaluation form that would inevitably pop into my inbox in a few days.
You bet I will, MM. Somehow I feel like we speak the same language now.
What’s your computer repair story? If you have a PC, I know you have one. Now Apple, well, that’s another story!