• FoxyBrown (10/10) Jul 21 2017 auto sss = "sc config \""~szSvcName~"\" start= disabled";
• FoxyBrown (7/17) Jul 21 2017 even spawnProcess isn't doing it

FoxyBrown <Foxy Brown.IPT> writes:

auto sss = "sc config \""~szSvcName~"\" start= disabled";
executeShell("sc config \""~szSvcName~"\" start= disabled");

but if I copy and paste the string in to an admin console, it 
works fine:

sc config "W32Time" start= disabled
[SC] ChangeServiceConfig SUCCESS

szSvcName is W32Time.

It's not an admin issue.

I *can't* set it to other states either. Does executeShell not 
run it's process with the same rights as the app?

FoxyBrown <Foxy Brown.IPT> writes:

On Saturday, 22 July 2017 at 02:31:45 UTC, FoxyBrown wrote:
 auto sss = "sc config \""~szSvcName~"\" start= disabled";
 executeShell("sc config \""~szSvcName~"\" start= disabled");

 but if I copy and paste the string in to an admin console, it 
 works fine:

 sc config "W32Time" start= disabled
 [SC] ChangeServiceConfig SUCCESS

 szSvcName is W32Time.

 It's not an admin issue.

 I *can't* set it to other states either. Does executeShell not 
 run it's process with the same rights as the app?

even spawnProcess isn't doing it

spawnProcess(["C:\\Windows\\System32\\sc.exe","config", 
szSvcName, "start=","disabled"]);

or

spawnProcess(["C:\\Windows\\System32\\sc.exe","config 
"~szSvcName~" start= disabled"]);