# "Error loading project : Switch from current encoding to specified encoding not supported."
**URL:** https://www.finalbuilder.com/forums/t/error-loading-project-switch-from-current-encoding-to-specified-encoding-not-supported/2142
**Category:** Discussion
**Created:** [May 10, 2013, 10:49am UTC](https://www.finalbuilder.com/forums/t/error-loading-project-switch-from-current-encoding-to-specified-encoding-not-supported/2142 "2013-05-10T10:49:09Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@rafael](https://www.finalbuilder.com/forums/u/rafael)
#### Post date: [May 10, 2013, 10:49am UTC](https://www.finalbuilder.com/forums/t/error-loading-project-switch-from-current-encoding-to-specified-encoding-not-supported/2142/1 "2013-05-10T10:49:09Z")
Greetings!
I am using FB 7, 2228
On one of my main projects, when I try to open it, I get this error:
---------------------------
Warning
---------------------------
Unable to load project.
Error: Error loading project : Switch from current encoding to specified encoding not supported.
Line : 1
Char : 40
---------------------------
OK
---------------------------
Sometimes, not sure why, I can actually open it.
I notice that in a hex editor, the file is lacking the first byte declaration that it is utf-16, though the xml declaration says utf 16.
Please advise what to do!
---
### Author:  [@rafael](https://www.finalbuilder.com/forums/u/rafael)
#### Post date: [May 10, 2013, 10:52am UTC](https://www.finalbuilder.com/forums/t/error-loading-project-switch-from-current-encoding-to-specified-encoding-not-supported/2142/2 "2013-05-10T10:52:04Z")
I should add:
project was initially an FB6 project, was migrated to FB7 with an earlier build of FB7 (the release build of 4 weeks ago or so). I have played with the encoding options in Tools | Options, but get no joy...
---
### Author:  [@rafael](https://www.finalbuilder.com/forums/u/rafael)
#### Post date: [May 10, 2013, 11:01am UTC](https://www.finalbuilder.com/forums/t/error-loading-project-switch-from-current-encoding-to-specified-encoding-not-supported/2142/3 "2013-05-10T11:01:37Z")
I was able to work around this issue....