Quote:
Originally Posted by chirotor
Solved. I had to go to user accounts in the control panel. Click on change user account control settings and move the bar to never notify and then reboot. I plan to reset the account control settings back to default later.
|
Strange, so UAC was getting in the way. From what you described of the installation process, you were failing where you should've gotten a UAC prompt. How were you opening the MSI? Double-clicking it from Explorer? Somehow, you got into a state where UAC didn't elevate and thus it attempted to do the install using your non-admin credentials, which shouldn't have happened.
Was this a direct download from Kovad's site (or the sourceforge links from the calibre site)? Was it a .msi file or some .exe that you were running? Something else? The only times I've seen MSIs not elevate properly is when run from a non-admin command line window using msiexec. For example if you were trying to install using a batch file of some sort that called msiexec from within, that would fail to elevate. Simply double-clicking the MSI should not fail to elevate.
Cybmole, I disagree with your assessment. If you have applications that need to elevate and you need to run them at startup, either you or the application developers are doing something wrong. For one, very few apps should need to elevate at all. For another, if you need to run an app elevated at startup, it probably ought to be written as an NT Service (you can do this yourself using srvany.exe from the Windows Resource Kit, to make up for lazy developers). If an app that needs to elevate shows up as "unknown", the developer sucks and failed to build his manifest properly (or at all). If an app that shouldn't need to elevate won't run if it's not admin, the app was written incorrectly.
Turning off UAC in order to use broken apps only encourages bad developers to continue writing broken apps.