Keylogger does not run correctly when started from Task Scheduler or as a Service (Windows)

[DerHeimataerde]

The program shows it is running in task manager, but it does not create a key log file when launched as a Task or service (using NSSM for the latter).

[GiacomoLaw]

Have you launched it manually before to create the log?

[DerHeimataerde]

Yes, it works just fine manually. To update, it also does not work if placed in the user startup folder nor the common startup folder

On Wed, Sep 12, 2018 at 3:37 AM Giacomo Lawrance notifications@github.com wrote:

Have you launched it manually before to create the log?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GiacomoLaw/Keylogger/issues/56#issuecomment-420561913, or mute the thread https://github.com/notifications/unsubscribe-auth/ApHbUWsE6zqlMlznOYARQa7pBHMXZXBvks5uaMe3gaJpZM4WgTPv .

[NathanJRollins]

The program stores the log file in the current working directory. This is something like system32, sysWOW64, or %userprofile% if you let Task Scheduler launch the program. Best solution (imo) is to specify the working directory manually within Task Scheduler - and it will respect it, as though you just double-clicked the program to launch it at its location (in which case it sets the working directory to the .exe's location on disk).

Modify the task -> Actions -> Edit -> "Start in (optional):" Set this to the program's directory's path (or wherever you'd like the log file to be saved). No quotation marks. Spaces are allowed. (:

Alternatively, the source could be modified to be more strict about where it saves the log file. The current solution allows a bit more flexibility, however.