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

Unable to use Elevation Mode #296

Closed
srbs73 opened this Issue Dec 5, 2018 · 6 comments

Comments

Projects
None yet
2 participants
@srbs73

srbs73 commented Dec 5, 2018

As most of the apps I want to arrange are running in Admin mode, I wanted to enable Elevation Mode, however MaxTo just repeatedly crashes and doesn’t enable. I can therefore on manage apps running in Normal mode.

Tried right clicking on MaxTo Icon to initially run in Admin mode but it immediately crashes with “Unrecoverable error”. Log file for this time:
image
Error log.txt

Expectation is it can be configured to always start as Admin and manage apps in admin mode.

Running Windows 10 and MaxTo version 2.0.0-beta3

@vegardlarsen

This comment has been minimized.

Member

vegardlarsen commented Dec 5, 2018

Thank you for reporting this. The error log does not contain any relevant fatal errors; so it is really hard for me to debug this. Can you get me the contents of the file %LocalAppData%\MaxTo\machine.id? It contains a randomly generated machine identifier that lets me look up any crashes you may have encountered in our online crash reporting.

@srbs73

This comment has been minimized.

srbs73 commented Dec 5, 2018

@vegardlarsen

This comment has been minimized.

Member

vegardlarsen commented Dec 5, 2018

After a bit of looking, I think this may be an issue with "Start on logon". Can you try disabling that setting in your config.json file, and then deleting the "MaxTo" task in Task Scheduler?

@srbs73

This comment has been minimized.

srbs73 commented Dec 5, 2018

@vegardlarsen

This comment has been minimized.

Member

vegardlarsen commented Dec 5, 2018

If you open the log file when you receive that crash report, what does it say?

@vegardlarsen vegardlarsen added this to the 2.0.0-beta.4 milestone Dec 6, 2018

@vegardlarsen vegardlarsen self-assigned this Dec 6, 2018

@vegardlarsen vegardlarsen added the bug label Dec 6, 2018

@vegardlarsen

This comment has been minimized.

Member

vegardlarsen commented Dec 6, 2018

I can confirm that this issue exists; and that the error message should not have been shown. This will be fixed for beta.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment