digitalcreations / MaxTo

Public issue tracker for MaxTo
https://docs.maxto.net
76 stars 5 forks source link

Unable to use Elevation Mode #296

Closed srbs73 closed 5 years ago

srbs73 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

Hi there, here you go: 5d3c3c2f5fe94d71bd459f345c0b0b47

vegardlarsen commented 5 years ago

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 commented 5 years ago

I don’t have a task in Task Scheduler for maxto and config.json already has start on logon disabled:

{ "$schema": "https://maxto.net/config.schema.json", "language": "en", "startup": { "startOnLogon": false, "runElevated": true }, "updates": { "enabled": true, "channel": "Beta" }, "behavior": { "snap": { "to": [ "Screen", "Window" ], "distance": 10 }, "transparentWindowsWhenMoving": true }, "shims": { "toggled": {} }, "license": { "firstStart": "2018-12-05T10:59:32.1173118Z" }, "recipes": [ { "name": "Move window left", "hotkey": "Windows+NumPad4", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Left" } } ] }, { "name": "Move window up", "hotkey": "Windows+NumPad8", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Up" } } ] }, { "name": "Move window right", "hotkey": "Windows+NumPad6", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Right" } } ] }, { "name": "Move window down", "hotkey": "Windows+NumPad2", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Down" } } ] }, { "name": "Swap window left", "hotkey": "Windows+Control+NumPad4", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Left", "swap": true } } ] }, { "name": "Swap window up", "hotkey": "Windows+Control+NumPad8", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Up", "swap": true } } ] }, { "name": "Swap window right", "hotkey": "Windows+Control+NumPad6", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Right", "swap": true } } ] }, { "name": "Swap window down", "hotkey": "Windows+Control+NumPad2", "ingredients": [ { "command": "window:move", "parameters": { "direction": "Down", "swap": true } } ] }, { "name": "Center window", "hotkey": "Windows+NumPad5", "ingredients": [ { "command": "window:center", "parameters": {} } ] } ], "monitor": { "idSelection": "SerialNumber", "virtualDesktop": false }, "errorReporting": { "anonymityLevel": "MachineIdentifier", "enabled": true }, "presets": [ { "type": "split", "splits": { "orientation": "Vertical", "distance": 0.5, "child1": null, "child2": null }, "name": "Two-way vertical" }, { "type": "split", "splits": { "orientation": "Horizontal", "distance": 0.5, "child1": null, "child2": null }, "name": "Two-way horizontal" }, { "type": "split", "splits": { "orientation": "Horizontal", "distance": 0.694473409801877, "child1": null, "child2": null }, "name": "General Office" } ] }

vegardlarsen commented 5 years ago

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

vegardlarsen commented 5 years ago

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