Hybrid (Windoze) - How to run as Admin?

[FredThompson]

The last few builds of Hybrid won't run with admin rights.

Is there a reason for this or is it a bundled app crashing?

[Havokdan]

@Selur said the Hybrid is made to work without administrative rights, if you have to run it with these rights, something is wrong. I myself have never had to use these rights and I have used the Hybrid quite a lot and it has been years.

[FredThompson]

I think you misunderstood my question.

Older releases of Hybrid could be run by all users.
Recent releases will NOT run for admin users.

Is there a legitimate reason admin users would NOT be allowed to run hybrid? Probably not. So...how to remove this restriction.

RUnas, ShellRunAs, and psexec can be used to force Hybrid to run for an admin user but removing the problem would be better than adding more complexity.

[Havokdan]

I think you misunderstood my question.

Older releases of Hybrid could be run by all users.
Recent releases will NOT run for admin users.

Is there a legitimate reason admin users would NOT be allowed to run hybrid? Probably not. So...how to remove this restriction.

RUnas, ShellRunAs, and psexec can be used to force Hybrid to run for an admin user but removing the problem would be better than adding more complexity.

In fact I got it wrong, however I'm using windows 10, I'm an administrator and program runs normally. But in his forum there are several topics from people who have had this same problem.

Sure, create a misc.ini file inside the Hybrid folder with the following content:
[General]
runAsAdmin=true
see: https://forum.selur.net/showthread.php?tid=10

Cu Selur

[FredThompson]

Yes, that is the solution. Thank you.

My copy of that page is from 2011. That setting didn't exist then.

[Selur]

Is there a legitimate reason admin users would NOT be allowed to run hybrid? Probably not. So...how to remove this restriction.
Just for clarification the restriction was added because:
1. Hybrid is developed assuming it is running as a restricted user.
This means:
a. it will behave differently if this is not the case.
b. I do not make any checks to hinder Hybrid or the tools it uses from unintended messing up a system. (Since I'm not the author of most of the tools Hybrid uses and a bunch of them are not always 'stable' I wouldn't try to guarantee for anything when running them with administrator rights.)
2. I think it's just plain unnecessary (sometimes even stupid) to run tools with elevated rights when they don't need them.
3. I got tired of having to debug problems of folks who run it with administrator rights which didn't tell me they ran it with such rights. (Worst case is users start running it with and without admin rights and Hybrid sometimes can and sometimes can't change it config files or looses access to folders,...)

-> So if you run it with administrator rights, don't complain to me if Hybrid or any of the tools is uses messes up something.

Cu Selur

Ps.: Better solution might probably be to try wrapping all tools and making sure they can't really mess stuff up too badly, but I neither have the time or motivation to do so.