javaw.exe will start anytime that ZAP starts (not just daemon mode), because ZAP is a java app.
There shouldn't be any need for ZAP to run as administrator.
If there's an issue with the user account being used to launch it you should look into "Run as" (CreateProcessAsUser
, etc). If you're currently running code from within an IDE like Visual Studio or whatever then it's probably picking the username of whatever account launched the IDE. (Or from the properties of the project you're working on.)
You could also look into:
public static Process Start(
string fileName,
string userName,
SecureString password,
string domain
)
https://msdn.microsoft.com/en-us/library/sxf2saat(v=vs.110).aspx
You could try to narrow down the cause of the issue by launching something else, like calc.exe.
Is there something specific that makes you think this is a ZAP issue and not a C#/Visual Studio/Windows issue?