|
Post by rb on Mar 3, 2020 20:42:47 GMT 1
I downloaded the new build of vDos 1 March 2020. I run it on a Win10 Pro system. Every time I start vDos I get the message "vDos should not run elevated". I tried to start the program using AdvancedRun with the setting "Run as... Current user - without UAC elevation". This results in the same error-box: "vDos should not run elevated". Please help!
Regards, Ronald
|
|
|
Post by Jos on Mar 3, 2020 20:55:36 GMT 1
Something seems off with your system, all programs would run elevated w/o you knowing. You’ll have to look into that. To allow vDos to run elevated, you have to add the ADMIN=ON directive to config.txt. It’s not documented since there should be no need for that, except when running under Wine on Linux.
Jos
|
|
|
Post by rb on Mar 3, 2020 20:58:50 GMT 1
Thanks, that worked. I can now start testing the new version. Regards, Ronald
|
|
|
Post by rowcroft on Mar 6, 2020 16:14:37 GMT 1
FYI- I'm getting the same error in some systems. Right now looks like just in Server 2019 if that helps.
|
|
|
Post by Jos on Mar 6, 2020 16:30:05 GMT 1
Well, it’s not an error, but a warning: vDos just shouldn’t be run elevated. That doesn’t harm, but indicates something is wrong since you most likely didn’t intend to run vDos elevated. You’re running vDos directly at the server, or mids RDP/RDS? If the latter, that would suggest a security issue. You won’t want remote users to have administrator rights.
Jos
|
|
|
Post by garlovel on May 22, 2020 16:31:34 GMT 1
I am getting this error when running vDos on Winflector server. I do not see an option to change this, but ADMIN = ON worked.
|
|