# Winlogbeat 8.13.0 dont start service

**URL:** https://discuss.elastic.co/t/winlogbeat-8-13-0-dont-start-service/356671
**Category:** Beats
**Tags:** winlogbeat
**Created:** [April 3, 2024, 11:33am UTC](https://discuss.elastic.co/t/winlogbeat-8-13-0-dont-start-service/356671 "2024-04-03T11:33:01Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)
#### Post date: [April 3, 2024, 6:50pm UTC](https://discuss.elastic.co/t/winlogbeat-8-13-0-dont-start-service/356671/5 "2024-04-03T18:50:53Z")

</div>

He already said no details. However, it should be something in Event System log.

As Leandro said, try winlogbeat from console. This is always the first step to make sure that everything is OK.

Have you use the zip or msi package? There might be an issue with the data directory. Check [this](https://discuss.elastic.co/t/winlogbeat-service-unable-to-start-error-1053-service-did-not-responded-to-start/231629) or [this](https://discuss.elastic.co/t/error-1053-the-service-did-not-respond-in-a-timely-fashion-when-attempting-to-start-winlogbeat-service-with-msi-package/255802) and of course add logging in winlogbeat.yml

---

_[View the full topic](https://discuss.elastic.co/t/winlogbeat-8-13-0-dont-start-service/356671)._