Thanks, but this gives the exact same error. If you just do "type file.sql" on Windows 10, the UTF-8 BOM remain visible in the output. Then sqlite3.exe will still complain about it. This problem is sqlite3.exe not filtering the 2 UTF-8 BOM bytes in the beginning of the file.