windows - how do I run an msi with SEE_MASK_NOZONECHECKS without restart -

i'm trying install driver remote framework lets me run shell commands spawned children of remoting/monitoring app on remote machine, run cmd /c "command". driver refuses install due security feature thinks driver may unsafe.

the driver has quotes(spaces in path) like

dim command: command =  "\\\\server\\driver\\folder\\autorun.exe" /passive   /norestart"; set retval = remote.shell(command) 

which runs

cmd /c " "\\server\driver\folder\autorun.exe" /passive /norestart" 

on remote machine

i've tried , have had trouble using setx see_mask_nozonechecks 1 /m in previous statement, i'm guessing subprocess don't see new global enviromental variables weren't around when it's parent started, , won't work without restart. i'd avoid restart.

i tried running

cmd /c " set see_mask_nozonechecks=1 & "\\server\driver\folder\autorun.exe" /passive /norestart"  

but doesn't seem work. ideas?

you got bit lost on way see_mask_nozonechecks used. not environment variable , cannot tinkered command prompt, option shellexecuteex(). winapi function indeed use start programs. isn't clear programming tools have access to, using in batch file or vbscript isn't going work. you'd need @ least, say, vb.net , pinvoke function. can required declarations pinvoke.net web site.

let's talk what's going on, might find simpler solution. when download file internet web site, windows adds stream file indicates file came from. states "this file did not come safe place" , makes driver installer balky. rather important feature if think it, user going install software can lot, pretty have free reign of machine if can driver installed.

if right-click file in explorer , click properties you'll see @ bottom of window:

all that's needed click unblock button. simple way user solve problem. document step in install instructions. advantage user took responsibility of allowing potentially unsafe code installed.

other ways file unblocked powershell's unblock-file command , sysinterals' streams utility, -d option.

and ought consider option of writing own installer. keep driver packaged in setup file won't tinkered windows. , user gets warning when starts installer instead. , can signed user has confidence in file came , didn't messed on way machine. there many utilities write installer, installaware, installshield, nsis, etcetera.