Attn: Dave Hooton (or others that can help!) - question on Run as Administrator

One of my installations requires it to be run as administrator to do updates. So I have that property set all the time, as sometimes updates come without notice (to me), then they error out and I have to run them again as Admin. It has just been easier to keep the Run as Admin set all the time.

Now I see Smart Tag support will not work when Run as Admin is set. Is there a way I can clear something so updates will work without being Admin, so I can turn off the Run as Admin setting?

Thanks!

Find more posts tagged with

Comments

TCBlack

Dom,

Dave stated here http://community.logos.com/forums/p/19651/148452.aspx#148452

That the only way to change was to uninstall and reinstall. [:(] not what you want to hear I know.

Mark Barnes

https://community.logos.com/discussion/comment/167566#Comment_167566

Not having ever installed Logos in Admin mode, I can't test this, but I would have guessed that resetting the file permissions on the Logos 4 folder might do the trick. What are you permissions at the moment? (Right-click on the folder, choose properties and select the security tab.)

TCBlack

https://community.logos.com/discussion/comment/167584#Comment_167584

That got me thinking too, if you right click the L4 Icon and go to properties, is it set there to run as admin? Uncheck it.

NetworkGeek

https://community.logos.com/discussion/comment/167588#Comment_167588

Mark, permissions are Full Control for my account, SYSTEM, and the machine Administrators group.

Thomas, I know where to change it not to Run as Administrator. Maybe I'll just turn it off and see if I can debug what breaks when the next update comes.

Unless anyone else has an idea, it's not worth a reinstall to me...

Dave Hooton

https://community.logos.com/discussion/comment/167601#Comment_167601

Unless anyone else has an idea, it's not worth a reinstall to me...

Sorry Dom, but so many users have tried to correct Permissions without success that a fresh install is the best way to fix it.

Mark Barnes

https://community.logos.com/discussion/comment/167609#Comment_167609

As far as I can work out, it can only be permissions on the files or registry that would cause a future problem. It may be that by running it as a normal user, attempting the upgrade and figuring out where it fails (upload the MSI logs?) we might be able to compare installations and work out what the permissions ought to be.

Or, if it's been tried before, perhaps Dave could point us to those logs, and we can experiment?

NetworkGeek

https://community.logos.com/discussion/comment/167609#Comment_167609

Sorry Dom, but so many users have tried to correct Permissions without success that a fresh install is the best way to fix it.

Thanks Dave and Mark, I think I am going to try and debug through it on the next update (these 2 machines not running beta 4.1, which I will jump on soon as it's getting close to stable enough for my normal work). I guess I am a glutton for punishment, or stubborn, or ignorant of advice! But it should be a fun little exercise to see what happens.

I'll keep all posted...

Dave Hooton

https://community.logos.com/discussion/comment/167677#Comment_167677

Or, if it's been tried before, perhaps Dave could point us to those logs, and we can experiment?

The typical message "insufficient privileges" tells you the file but changing its permissions or that of the containing folder have met mostly with failure. It's a lot simpler/certain to perform a fresh install with one of the Quick Methods (Method 3 for sure as 1 or 2 depend on installing the same version).