The CLI always supported both / and \ since the path is merely passed to the appropriate Windows API for processing, and Windows will accept either.

The "input parser" in the CLI requires you to escape the \ (that is, to use \\ where you want an actual \), but the actual path passed to the sqlite3_load_extension C API does NOT require the \ to be escaped. This is unchanged.

However, the sqlite3_load_extension C API prior to 3.34.0 did not recognize a backslash (\) as a path component separator -- it only recognized the / separator when generating the entry-point name. It now recognizes \ as a path separator as well when generating the entry-point name.

** Edited to escape the backslash character with another backslash **