Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[swinster]

Hi All,

I believe that this bug exists in MC 16 as well.

If an update is available and launched within MC from the task area, if the current user is set up as a standard User (which, for ALL tidy set-ups this should be true - of course it often isn't), then the user will be presented with the UAC prompt to supply an administrator password. After the password is supplied correctly, the install will proceed as expected, but as the install finished, the user will be presented with the following Error dialogue:
Update
Thee was a problem installing the update.
Please retry the update and ensure that it UAC permission when prompted.

Retry Update                       Cancel Update
If the user presses retry, the update will be reapplied, but at the end the same prompt will be see - ad nauseum

However, if the user presses cancel they will find that MC starts yet the update HAS been applied successfully (as reported in the Help-->About box).

I can confirm that this problem exist on Windows 7 (32 and 64 bit) and I believe a similar issue is seen on my Windows 2003 server.

Chris

[Matt]

I've never seen this.

Are you running a second copy as a service, or do anything else that might run two copies at once?

[swinster]

I USED to run the MC server as a service on my 2003 server (!), but I relented and created a low privilege user account to auto login an start MC server.

The desktop clients I use ALL exhibit this behaviour. None of them run the server. In fact, I'm currently writing this on a new laptop running Windows 7 Pro 64 bit. New install of MC17 - same issue - no server running, just the client linked to a server.

It never really bothered me but it will confuse some users.

[Matt]

So when you get a UAC prompt, you log in as a different user instead of an elevated version of the same user?

If so, this explains the issue.  The user values in the registry (HKCU) that the installer sets won't show up to the program.

I'll have to think about how we can better handle this.

[swinster]

If the user is a standard user there is NO elevated privilege for that user. The only elevated privilege for that user is use the credentials of a user that was created as an Administrator of that machine - i.e. a different user.

Finally, Microsoft has got a decent user security system in place, problem is we've all become sloppy over the years.

[swinster]

And don't even think of saying "why not raise the privileges of the user to an administrator". I'm just not going there 

Linux users would be spinning on there desk chairs.

[Matt]

And don't even think of saying "why not raise the privileges of the user to an administrator". I'm just not going there 

With UAC, it is much more common to run as user but elevate under the same account. 

That's not to say we won't fix this (we will), just that this is the reason it's not a common problem.

[Matt]

Coming in 17.0.32 and later:
Fixed: When installing an update on a non-administrative account the prompted for a different username and password to run the install, the program could report an error when starting after the update.

Please let us know how it works for you.

[EdBrady]

I've never seen this.

I reported this when it first appeared in MC16, but my posts were igonored.

http://yabb.jriver.com/interact/index.php?topic=64020.msg428347#msg428347