Installer Bug: Can't write to the "System\es" folder

This is the second time in a row the Logos installer for an update (4.1 and 4.2) has failed because it says it can't write DLLs to the System\es folder. Once again, I had to find the folder where the .exe / .msi files had been dropped and run them as Administrator. (This is on Windows 7 x64.)

This wouldn't be so bad if I had control of the update to start - I'm used to downloading updates and installing them as admin. But everything acts like it's going to work right up until that error happens. I'm sure it's because I don't install Logos in the default location under C:\Users\{me}.

More fallout from the *HORRIBLE* decision to violate all of Microsoft's standards about where to install applications (yes, I'm going to keep harping on this... ...

Donnie

Find more posts tagged with

Comments

Dave Hooton

This wouldn't be so bad if I had control of the update to start - I'm used to downloading updates and installing them as admin. But everything acts like it's going to work right up until that error happens. I'm sure it's because I don't install Logos in the default location under C:\Users\{me}.

If you install to C:\Program Files, or any other system protected folder then you must also expect to "Run as Admin" for updates to succeed ie. you must run L4 or the setup program elevated. I have a custom installation to another drive/partition and have no problems with updates.

Donnie Hale

https://community.logos.com/discussion/comment/198430#Comment_198430

I don't have it installed under C:\Program Files[(x86)] - just a folder I created called "C:\Other Programs". The first time I tried to install L4, it wouldn't even let me install it to C:\Program Files. I manually changed the install location to that folder, and the installer griped about not being able to install to a protected folder. The absurdity of that still gets my blood pressure up.

Anyway, I don't know why the update installer has this problem. Running it elevated works, and I haven't had to ever run the program itself elevated.

Donnie

Dave Hooton

https://community.logos.com/discussion/comment/198435#Comment_198435

I don't have it installed under C:\Program Files[(x86)] - just a folder I created called "C:\Other Programs".

As an Admin user you should have Full Control of that folder. The other possibility is that you performed the initial installation with "run as Admin"?

Donnie Hale

https://community.logos.com/discussion/comment/198441#Comment_198441

The other possibility is that you performed the initial installation with "run as Admin"?

That's a possibility. I don't recall for sure, but I typically run an installer elevated reflexively.

Can you look at the permissions on your Logos4 folder and see what permissions on them would let it be updated by an installer without elevated rights?

Donnie

Dave Hooton

https://community.logos.com/discussion/comment/198445#Comment_198445

Can you look at the permissions on your Logos4 folder and see what permissions on them would let it be updated by an installer without elevated rights?

I have Full Control of my installation folder (as is the case for a default installation), but here's the situation:

L4 is designed to install** and run in a Standard user environment (it does not require Admin privilege)
Admin accounts run as Standard user accounts (Admin privileges are disabled until required)
so if you force the installer to "run as administrator" it can set file permissions that require that level of access!

** Prerequisites requires Admin privilege for protected folders like Fonts!

So it is very difficult to fix this problem with Permissions. The workaround is to run elevated or delete the installation folder and re-install (some quick methods are available).