# Spending tokens to repair UTF-16 that should have been UTF-8 **URL:** \ **Category:** Bug Reports\ **Tags:** windows, hooks, rules\ **Created:** [April 24, 2026, 3:35am UTC](https://forum.cursor.com/t/spending-tokens-to-repair-utf-16-that-should-have-been-utf-8/158902 "2026-04-24T03:35:02Z")\ **Posts on this page:** 1\ **Showing post:** 30
**Author:** ![153653](https://avatars.discourse-cdn.com/v4/letter/1/c6cbf5/32.png) [@153653](https://forum.cursor.com/u/153653)\ **Post date:** [May 27, 2026, 9:28am UTC](https://forum.cursor.com/t/spending-tokens-to-repair-utf-16-that-should-have-been-utf-8/158902/30 "2026-05-27T09:28:14Z")
Marc and Sam from Cursor helped with these workarounds that worked for me at least, until the bug is fixed. 1. In Control Panel\> Region\> Administrative\> Change System Locale - check the box for “_Beta: Use Unicode UTF-8 for worldwide language support_”. For me this overrides the bug with regards to file edits, but not new file creation. The next step after that if that didn’t help with edits (which I didn’t use since the first step worked), was '_Open Workspace Settings (JSON) and add these two settings between the curly braces’_: 2. They also provided this Cursor Rule language which avoids the buggy write tool. --- _[View the full topic](https://forum.cursor.com/t/spending-tokens-to-repair-utf-16-that-should-have-been-utf-8/158902)._