# \[Filebeat 7.12\] \[Windows\] Failed to open store 'filebeat' after incorrect Windows reboot

**URL:** https://discuss.elastic.co/t/filebeat-7-12-windows-failed-to-open-store-filebeat-after-incorrect-windows-reboot/270145
**Category:** Beats
**Tags:** windows, filebeat
**Created:** [April 14, 2021, 8:21pm UTC](https://discuss.elastic.co/t/filebeat-7-12-windows-failed-to-open-store-filebeat-after-incorrect-windows-reboot/270145 "2021-04-14T20:21:57Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![akelio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akelio/32/87060_2.png) [@akelio](https://discuss.elastic.co/u/akelio)
#### Post date: [April 14, 2021, 8:21pm UTC](https://discuss.elastic.co/t/filebeat-7-12-windows-failed-to-open-store-filebeat-after-incorrect-windows-reboot/270145/1 "2021-04-14T20:21:57Z")

</div>

Hi!  
Filebeat 7.12 (x86) on Windows machine cannot start after incorrect OS reboot (possibly after power supply lost).  
Log shows that registry data files are corrupted. The only way I found to manually start filebeat is deleting registry data dir.

```auto
2021-04-08T18:50:04.462+0300	INFO	instance/beat.go:468	filebeat start running.
2021-04-08T18:50:04.472+0300	INFO	[monitoring]	log/log.go:117	Starting metrics logging every 30s
2021-04-08T18:50:05.125+0300	ERROR	beater/filebeat.go:351	Could not init registrar: failed to open store 'filebeat': corrupted data file: invalid character 'v' after object key
2021-04-08T18:50:05.191+0300	INFO	[monitoring]	log/log.go:152	Total non-zero metrics	{"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":280,"time":{"ms":280}},"total":{"ticks":763,"time":{"ms":763},"value":763},"user":{"ticks":483,"time":{"ms":483}}},"handles":{"open":128},"info":{"ephemeral_id":"e45fc94e-c59b-44f9-b521-df368d79062a","uptime":{"ms":8311}},"memstats":{"gc_next":14358272,"memory_alloc":12650408,"memory_sys":24988668,"memory_total":42061160,"rss":42430464},"runtime":{"goroutines":14}},"filebeat":{"harvester":{"open_files":0,"running":0}},"libbeat":{"config":{"module":{"running":0}},"output":{"events":{"active":0},"type":"elasticsearch"},"pipeline":{"clients":0,"events":{"active":0}}},"registrar":{"states":{"current":0}},"system":{"cpu":{"cores":2}}}}}
2021-04-08T18:50:05.192+0300	INFO	[monitoring]	log/log.go:153	Uptime: 8.3344767s
2021-04-08T18:50:05.192+0300	INFO	[monitoring]	log/log.go:130	Stopping metrics logging.
2021-04-08T18:50:05.258+0300	INFO	instance/beat.go:474	filebeat stopped.
2021-04-08T18:50:05.273+0300	ERROR	instance/beat.go:971	Exiting: failed to open store 'filebeat': corrupted data file: invalid character 'v' after object key

```

---

<div class="post-metadata">

### Author: ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)
#### Post date: [April 15, 2021, 8:19am UTC](https://discuss.elastic.co/t/filebeat-7-12-windows-failed-to-open-store-filebeat-after-incorrect-windows-reboot/270145/2 "2021-04-15T08:19:27Z")

</div>

That's interesting. Would you mind opening a GH issue for this problem?

---

<div class="post-metadata">

### Author: ![akelio](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/akelio/32/87060_2.png) [@akelio](https://discuss.elastic.co/u/akelio)
#### Post date: [April 19, 2021, 12:01pm UTC](https://discuss.elastic.co/t/filebeat-7-12-windows-failed-to-open-store-filebeat-after-incorrect-windows-reboot/270145/4 "2021-04-19T12:01:32Z")

</div>

Done! [[Filebeat 7.12] [Windows] "Failed to open store 'filebeat': corrupted data file" after incorrect Windows reboot · Issue #25135 · elastic/beats · GitHub](https://github.com/elastic/beats/issues/25135)

---

<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: [May 17, 2021, 2:02pm UTC](https://discuss.elastic.co/t/filebeat-7-12-windows-failed-to-open-store-filebeat-after-incorrect-windows-reboot/270145/5 "2021-05-17T14:02:07Z")

</div>

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