On 22/02/18 00:12, ?ubom?r Carik wrote: > The application requires higher run privileges to be able modify > network settings. With this change, there is no need to start > the tool explicitly in console with administrator rights. I have not tested this patch (and I am no Windows expert, either)... so take the following with a pinch of salt. Does this improve the user-experience? The last time I checked, requiring admin privileges this way led to the following behaviour: 1) User run command from unprivileged command-prompt 2) User gets UAC-prompt, confirms elevation of privileges 3) New CMD-window appears, ouput scrolls by 4) New CMD-window closes once command is finished 5) User returns to prompt in original unprivileged command-prompt without any output visible there. But maybe that does not matter that much and it does indeed improve the user-experience because the user gets asked for credentials anyways, so the new window stays open. Still any error-messages would be invisible to the user. Or maybe the behaviour is not like I described above...
