# Winlogbeat speeding the clock

**URL:** <https://discuss.elastic.co/t/winlogbeat-speeding-the-clock/185641>\
**Category:** Beats\
**Tags:** winlogbeat\
**Created:** [June 13, 2019, 12:27pm UTC](https://discuss.elastic.co/t/winlogbeat-speeding-the-clock/185641 "2019-06-13T12:27:49Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vijayakumar\_Kannan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakumar_kannan/32/34873_2.png) [@Vijayakumar\_Kannan](https://discuss.elastic.co/u/Vijayakumar_Kannan)\
**Post date:** [June 13, 2019, 12:27pm UTC](https://discuss.elastic.co/t/winlogbeat-speeding-the-clock/185641/1 "2019-06-13T12:27:49Z")

</div>

Dear all,

In our environment we installed winlogbeat 6.3.2 version . Found in only windows 2008 R2 servers clock speeding up. Is it a known issue? From which version this issue resolved?

Regards,  
Vijay

---

<div class="post-metadata">

**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\
**Post date:** [June 14, 2019, 8:11am UTC](https://discuss.elastic.co/t/winlogbeat-speeding-the-clock/185641/2 "2019-06-14T08:11:40Z")

</div>

Hi @Vijayakumar_Kannan,

This seems to be a known issue related to the Go runtime, more details here: [https://github.com/elastic/beats/issues/7308](https://github.com/elastic/beats/issues/7308)

---

<div class="post-metadata">

**Author:** ![Vijayakumar\_Kannan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijayakumar_kannan/32/34873_2.png) [@Vijayakumar\_Kannan](https://discuss.elastic.co/u/Vijayakumar_Kannan)\
**Post date:** [June 16, 2019, 9:10am UTC](https://discuss.elastic.co/t/winlogbeat-speeding-the-clock/185641/3 "2019-06-16T09:10:34Z")

</div>

In which version of winlogbeat this issue resolved for windows 2008 R2 ?

---

<div class="post-metadata">

**Author:** ![martinr\_ubi](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@martinr\_ubi](https://discuss.elastic.co/u/martinr_ubi)\
**Post date:** [June 16, 2019, 10:14am UTC](https://discuss.elastic.co/t/winlogbeat-speeding-the-clock/185641/4 "2019-06-16T10:14:51Z")

</div>

If you’re a client of Elastic the company, I would recommend you open a support ticket to see if they have an official stance or custom solution for their clients because Winlogbeat is still listed as supporting win2008r2, surprisingly I guess?

My understanding of this issue and I don’t think anything changed, is that this is not fixed in any newer version of Winlogbeat AND will likely not/never be fixed.  
That would be because the issue is in the Go language used by the Beats software and the maintainer of the language have announced they would accept a fix but will probably never make one themselves because only very old windows OS are affected.

Windows 2008r2 have only a few months of life left so I hope you’re already planning the upgrade to a newer Windows version since you don’t really have a choice, that will fix your issue.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 14, 2019, 10:14am UTC](https://discuss.elastic.co/t/winlogbeat-speeding-the-clock/185641/5 "2019-07-14T10:14:54Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.