If I was to deploy this version of your software with automation tools that use SYSTEM for the install with these new comamndl ines, would these launch the software in the SYSTEM context after install in Session 0 or would it be launched into the logged on user in Session 1? I would think if it eneded up being session 0 that would be bad.

No idea about concept of session 0 or of session 1.
It's launched under the accound of user.

I would strongly suggest that you do not allow a silent install to launch in the context of the user who installed it if the installation is SYSTEM. (like through tools such as SCCM, BIGFIX, Tanium or others) You end up leaving an open session that a user cannot access that has SYSTEM rights, nor can user see or interact with.

No idea about concept of session 0 or of session 1. It's launched under the accound of user.

https://techcommunity.microsoft.com/t5/ask-the-performance-team/sessions-desktops-and-windows-stations/ba-p/372473

Is there a way that /runNppAfterSilentInstall will only run if /closeRunningNpp is also called? I would like to automatically re-open npp only if the installation closed it, but if it was already closed it should not open it.

@schenardie

I would like to automatically re-open npp only if the installation closed it, but if it was already closed it should not open it.

In the upcoming N++ version, there will be new installer param /relaunchNppAfterSilentInstall for it (for details check the current PR #16626 which added option to auto-update N++ also at its exit)