Elastic Agent service stops after launching but doesn't throw any error in command line

Hi,

In data/elastic-agent-*/logs/ folder there's only a log file with 2 entries, resulting from running install command. There is no default folder for filebeat and metricbeat logs either.

This is the content of elastic-agent-json.log

{"log.level":"debug","@timestamp":"2021-01-12T14:43:26.050+0100","log.origin":{"file.name":"kibana/client.go","file.line":170},"message":"Request method: POST, path: /api/fleet/agents/enroll","ecs.version":"1.6.0"}

{"log.level":"warn","@timestamp":"2021-01-12T14:43:26.051+0100","log.logger":"tls","log.origin":{"file.name":"tlscommon/tls_config.go","file.line":93},"message":"SSL/TLS verifications disabled.","ecs.version":"1.6.0"}

As @dgcapel said, this file does not change at all after restarting service, nor create new log files.

I noticed in other hosts a log file is created in C:\Program Files\Elastic\Agent\elastic-agent.log but no matter what it is not created in this host. It only shows up when running Elastic Agent from terminal (with run option).

For additional information I'm running Windows 10 Enterprise N, but this hasn't been an issue in other hosts.

Thank you.