This may be an edge case but, only on Windows due to how files work there, if you:

1. Have a driver loaded with a driver manager
2. Run dbc uninstall ${driver}

dbc will act like it failed but will actually have partially removed the driver. For (1), technically anything that locks the driver DLL or probably parent dir down will cause this.

C:\Users\Bryce>dbc uninstall duckdb
Error: failed to uninstall driver: failed to delete driver shared object: error removing driver duckdb: remove C:\Users\Bryce\AppData\Roaming\ADBC\Drivers\duckdb_windows_amd64_v1.4.0\duckdb.dll: Access is denied.

C:\Users\Bryce>dir C:\Users\Bryce\AppData\Roaming\ADBC\Drivers\duckdb_windows_amd64_v1.4.0
 Volume in drive C has no label.
 Volume Serial Number is A896-80F2

 Directory of C:\Users\Bryce\AppData\Roaming\ADBC\Drivers\duckdb_windows_amd64_v1.4.0

10/16/2025  04:20 PM    <DIR>          .
10/16/2025  01:52 PM    <DIR>          ..
10/16/2025  01:52 PM        34,269,152 duckdb.dll

The registry key does get removed so the driver DLL that gets left behind is basically inaccessible.

We could possibly move the DLL removal before the registry removal, at least on Windows, or we could just catch the above case and print a message indicating that the driver may have been removed but left behind extra files.