Unable to start PostgreSQL service after pgAgent installation

I had Postgre running just fine on my Windows 10 (64-bit). Then I tried to install pgAgent via the stackbuilder for postgres. I got some error that it was not able to create a .conf file under %\user\appdata\postgres. (Note That folder has never existed. I had my data under C:\Program Files\PostgreSQL\11\data) After that is asked me to restart my PC, so I did. Now I am not able to start pgAdmin, not able to start postgre from microsoft services. I am not either able to run the stack builder for postgres, it simply suggest that it might help to reinstall postgres. Can one stackbuilder install really corrupt my entire database? I got these messages in the logger:

2019-09-10 15:33:03.300 EEST  ERROR:  could not open extension control file "C:/Program Files/PostgreSQL/11/share/extension/pgagent.control": No such file or directory
2019-09-10 15:33:03.300 EEST  STATEMENT:  CREATE EXTENSION pgagent;
2019-09-10 15:35:23.957 EEST  ERROR:  could not open extension control file "C:/Program Files/PostgreSQL/11/share/extension/pgagent.control": No such file or directory
2019-09-10 15:35:23.957 EEST  STATEMENT:  CREATE EXTENSION pgagent;
2019-09-10 15:43:44.944 EEST  ERROR:  schema "pgagent" does not exist
2019-09-10 15:43:44.944 EEST  STATEMENT:  SELECT has_schema_privilege('pgagent', 'USAGE')
2019-09-10 15:48:53.247 EEST  ERROR:  schema "pgagent" does not exist
2019-09-10 15:48:53.247 EEST  STATEMENT:  SELECT has_schema_privilege('pgagent', 'USAGE')
2019-09-10 15:51:53.369 EEST  ERROR:  schema "pgagent" does not exist
2019-09-10 15:51:53.369 EEST  STATEMENT:  SELECT has_schema_privilege('pgagent', 'USAGE')
2019-09-10 15:59:04.716 EEST  ERROR:  schema "pgagent" does not exist
2019-09-10 15:59:04.716 EEST  STATEMENT:  SELECT has_schema_privilege('pgagent', 'USAGE')
2019-09-10 16:17:15.856 EEST  LOG:  could not receive data from client: An existing connection was forcibly closed by the remote host.
2019-09-10 16:17:15.857 EEST  LOG:  could not receive data from client: An existing connection was forcibly closed by the remote host.
2019-09-10 16:17:26.569 EEST  LOG:  received fast shutdown request
2019-09-10 16:17:26.575 EEST  ERROR:  canceling statement due to user request
2019-09-10 16:17:26.576 EEST  ERROR:  canceling statement due to user request
2019-09-10 16:17:26.580 EEST  LOG:  aborting any active transactions
2019-09-10 16:17:26.580 EEST  ERROR:  canceling statement due to user request
2019-09-10 16:17:26.609 EEST  LOG:  background worker "logical replication launcher" (PID 18252) exited with exit code 1
2019-09-10 16:17:26.609 EEST  LOG:  background worker "TimescaleDB Background Worker Launcher" (PID 18188) exited with exit code 1
2019-09-10 16:17:26.610 EEST  LOG:  background worker "TimescaleDB Background Worker Scheduler" (PID 20960) exited with exit code 1
2019-09-10 16:17:26.732 EEST  LOG:  shutting down
2019-09-10 16:17:26.898 EEST  LOG:  database system is shut down

**EDIT:** When I try to execute pg_ctl start -D C:\Program Files\PostgreSQL\11\data, I get this error:

The code execution cannot proceed because LIBPQ.dll was not found.
Reinstalling the program may fix this problem.

The code execution cannot proceed because libiconv-2.dll was not
found. Reinstalling the program may fix this problem.

I do have postgres in windows path **EDIT2:** I ended up reinstalling the PostgreSQL server. Now I got it working again. The source of the original problem was probably that pgAgent was installed in a folder where already existing postgre files were