If you try the same URL shown in the error message from your web browser on the Windows machine running Winlogbeat do you get back a status response from Kibana?
I also notice that your config is showing two output.elasticsearch.hosts settings. You should remove one of them. But this should be affecting the setup connection to Kibana.
PS F:\Winlogbeat\winlogbeat-7.2.0-windows-x86_64> .\winlogbeat.exe test output -c .\winlogbeat.yml -e
2019-07-12T09:23:49.283+0200 INFO instance/beat.go:606 Home path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86_6
4] Config path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86_64] Data path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86_6
4\data] Logs path: [F:\Winlogbeat\winlogbeat-7.2.0-windows-x86_64\logs]
2019-07-12T09:23:49.360+0200 INFO instance/beat.go:614 Beat ID: 3a696b66-ed6e-41ba-97ec-93e0ed5fd49f
2019-07-12T09:23:49.360+0200 INFO [index-management] idxmgmt/std.go:178 Set output.elasticsearch.index t
o 'winlogbeat-7.2.0' as ILM is enabled.
2019-07-12T09:23:49.360+0200 INFO elasticsearch/client.go:166 Elasticsearch url: http://192.168.1.X:9200
elasticsearch: http://192.168.1.178:9200...
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: 192.168.1.X
dial up... ERROR dial tcp 192.168.1.X:9200: connectex: Une tentative de connexion a échoué car le parti connecté n
'a pas répondu convenablement au-delà d'une certaine durée ou une connexion établie a échoué car l'hôte de connexion n'a
pas répondu.
I delete one output.elasticsearch.hosts, its inaccessible
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.