Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI does not reflect enabled elevation #350

Closed
bojordan opened this Issue Feb 26, 2019 · 12 comments

Comments

Projects
None yet
3 participants
@bojordan
Copy link

bojordan commented Feb 26, 2019

For some time now I have been able to run MaxTo with elevation enabled (I believe I have used all versions that enabled it). However, the UI does not reflect this:

image

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Feb 28, 2019

So if you check Task Manager, is MaxTo running elevated?

Under Details, you may have to right-click the column headers, click Select columns and toggle the Elevated checkbox on. Then you should be able to see the various MaxTo processes running. Only 3 of 5 should be running elevated (MaxTo.Core.exe, MaxTo.Companion.x64.exe and MaxTo.Companion.x86.exe).

@MalteHillmann

This comment has been minimized.

Copy link

MalteHillmann commented Feb 28, 2019

Same problem here. It says it's running as normal user. Task manager says:

Name - Elevated
MaxTo.Companion.x64.exe - Yes
MaxTo.Companion.x86.exe - Yes
MaxTo.Core.exe - Yes
MaxTo.Server.Exe - No
MaxTo.UI.exe - No

Seems to be correct?

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Mar 4, 2019

It does seem to be correct, yes.

Is your machine in any way locked down using group policy or similar?

@MalteHillmann

This comment has been minimized.

Copy link

MalteHillmann commented Mar 4, 2019

Is your machine in any way locked down using group policy or similar?

Only some privacy modifications by DoNotSpy10. Not in an active directory.

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Mar 4, 2019

Can you check your registry to see if this key is present, and check its value:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA

@MalteHillmann

This comment has been minimized.

Copy link

MalteHillmann commented Mar 4, 2019

EnableLUA is a REG_DWORD an is set to 1.

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Mar 4, 2019

OK, so that is the registry key MaxTo uses to determine if User Account Control is enabled on the machine. It appears to be in your case. The processes also seem to be started correctly, but MaxTo itself cannot detect it.

I can't say exactly what causes this, but I will be looking at this closely before 2.0 goes final.

@vegardlarsen vegardlarsen self-assigned this Mar 4, 2019

@vegardlarsen vegardlarsen added the bug label Mar 4, 2019

@vegardlarsen vegardlarsen added this to the 2.0.0 milestone Mar 4, 2019

@MalteHillmann

This comment has been minimized.

Copy link

MalteHillmann commented Mar 4, 2019

Okay. If you need any help, feel free to contact me.

@vegardlarsen vegardlarsen modified the milestones: 2.0.0, 2.0.0-rc.2 Mar 5, 2019

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Mar 6, 2019

@MalteHillmann Can you confirm that you are running 2.0.0-rc.1, not any of the beta versions?

@MalteHillmann

This comment has been minimized.

Copy link

MalteHillmann commented Mar 6, 2019

@vegardlarsen yes, i'm using "2.0.0-rc1".

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Mar 6, 2019

@MalteHillmann Can you contact me on the support e-mail so I can have you test a private build?

@vegardlarsen

This comment has been minimized.

Copy link
Member

vegardlarsen commented Mar 7, 2019

With @MalteHillmann's help, we have confirmed that our fix works on his machine, and the fix for this issue will be in 2.0.0-rc.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.