Extension Manager will not open and Adobe doesn't care

Question

Just search on “extension manager will not open” in the Adobe Forums or Google and pages of hits come up going back to CS4. This is a serious problem that Adobe is simply ignoring.
I have Windows 7 Professional 64-bit with Design Premium CS5 installed. Nothing happens when I click on Manage Extensions from within any Adobe application, nothing happens when I click on Adobe Extension Manager CS5 on the start menu, and nothing happens when I double click on a .mxp file. No error messages – nothing.
So I had a free couple of hours and decided to call Adobe. Six hours later, after talking with Raj, Peenal, Tushar, Madhur, and Sandeep (get the picture?), after noting that none of them had ever even heard of the problem, after my call was dropped during one 30 minute wait, and after a complete uninstall and reinstall of the complete CS5, I have exactly the same problem I started with.
For my purposes, Design Premium CS5 is literally useless without extensions and Adobe has left me holding a $1500 boat anchor. Do you think anybody at Adobe cares?  I don’t.
Bottom line - DO NOT BUY Design Premium CS5 if you need extensions. They very possibly will not install and Adobe won't/can't help you.

Answer 1

Thanks to Carl Sun and Zhiqianq Liu, my problem with Extension Manager is resolved (the problem with Adobe support is not).
I followed Carl's Sun's instructions to the letter. I created a ExManLog.YES file and then manually ran Adobe Extension Manager CS5.exe via "Run as administrator" as Carl suggested and the Extension Manager ran for the first time.
In other words, either creating the ExManLog.YES file (unlikely) or manually running the .exe file as administrator (most certainly the solution) solved the problem.
Running, rerunning, rebooting and rerunning all work now – all without right clicking on Adobe Extension Manager CS5.exe before running Extension Manager. That is, it was apparently sufficient to right click on Adobe Extension Manager CS5.exe and then run the Extension Manager as administrator one time.
Now what's diabolical about this is that my user has full administrator privileges. Still, Extension Manager wasn’t actually running as administrator until I physically located the .exe file and manually ran it as administrator one time.
And what’s doubly diabolical is that all those guys at Adobe didn’t have a clue and Carl and Zhiqianq solved it right away.
Thank you, thank you.
Now – Adobe – if you are reading this, five of you guys caused me six hours of untold grief (case # 182188172) when the solution was actually very simple. I won’t be forgetting that anytime soon and I hope others who read this will get the message that Adobe support is seriously dysfunctional.