Interesting, maybe. Perhaps stranger than either of us yet understands. I was using compiler version 19.27.29111 for x64, almost 4 months "old". My omission is closer to neglecting to say when in a given model/year's production run the vehicle was made. This is not to say that the revision level is unimportant. It may yet be shown to be critical. Updating to Visual Studio 16.8.3, (CL v19.28.29335 for the 64-bit toolset), followed by a restart, does not clear the OP's reported errors with my build options. With my hacky work-around, (to get an executable), I get this from the pragma_compile_options virtual table:<code> ┌─────────────────────────────┐ │ compile_options │ ├─────────────────────────────┤ │ COMPILER=msvc-1928 │ │ DEFAULT_FOREIGN_KEYS │ │ DEFAULT_SYNCHRONOUS=3 │ │ DEFAULT_WORKER_THREADS=3 │ │ ENABLE_BYTECODE_VTAB │ │ ENABLE_COLUMN_METADATA │ │ ENABLE_DBSTAT_VTAB │ │ ENABLE_FTS4 │ │ ENABLE_FTS5 │ │ ENABLE_GEOPOLY │ │ ENABLE_JSON1 │ │ ENABLE_MATH_FUNCTIONS │ │ ENABLE_PREUPDATE_HOOK │ │ ENABLE_RTREE │ │ ENABLE_SESSION │ │ ENABLE_STMTVTAB │ │ ENABLE_UNKNOWN_SQL_FUNCTION │ │ LIKE_DOESNT_MATCH_BLOBS │ │ MAX_TRIGGER_DEPTH=100 │ │ OMIT_DEPRECATED │ │ OMIT_SHARED_CACHE │ │ TEMP_STORE=2 │ │ THREADSAFE=0 │ │ UNTESTABLE │ │ USE_ALLOCA │ │ USE_URI │ └─────────────────────────────┘ </code>Will you please provide your compile options to aid my further investigation?