# 8.4.2: "incompatible encodings: CP850 and UTF-8" - Issue sending DB records to Elastic after upgrade to Elastic 8.4.2 from 8.3.2

**URL:** https://discuss.elastic.co/t/8-4-2-incompatible-encodings-cp850-and-utf-8-issue-sending-db-records-to-elastic-after-upgrade-to-elastic-8-4-2-from-8-3-2/315697
**Category:** Logstash
**Created:** [October 3, 2022, 3:04pm UTC](https://discuss.elastic.co/t/8-4-2-incompatible-encodings-cp850-and-utf-8-issue-sending-db-records-to-elastic-after-upgrade-to-elastic-8-4-2-from-8-3-2/315697 "2022-10-03T15:04:53Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![simon137](https://avatars.discourse-cdn.com/v4/letter/s/71e660/32.png) [@simon137](https://discuss.elastic.co/u/simon137)
#### Post date: [October 20, 2022, 5:56pm UTC](https://discuss.elastic.co/t/8-4-2-incompatible-encodings-cp850-and-utf-8-issue-sending-db-records-to-elastic-after-upgrade-to-elastic-8-4-2-from-8-3-2/315697/2 "2022-10-20T17:56:20Z")

</div>

I seem to have the same issue, but only on all my windows desktops not on the windows server.  
And it somehow magically goes away if I redirect standard output of logstash, which just makes no sense at all.

[https://discuss.elastic.co/t/encoding-issue-depending-on-how-logstash-is-started/317136](https://discuss.elastic.co/t/encoding-issue-depending-on-how-logstash-is-started/317136)

---

_[View the full topic](https://discuss.elastic.co/t/8-4-2-incompatible-encodings-cp850-and-utf-8-issue-sending-db-records-to-elastic-after-upgrade-to-elastic-8-4-2-from-8-3-2/315697)._