**Record the Python version and architecture.** Run python with a print of the version and whether it is 64 bit or 32 bit, and note the environment path so you test the interpreter that actually runs the app. Expected: one clear version and bitness, for example Python 3.12 64 bit in a named virtual environment.

**Reinstall cffi from a wheel in that environment.** Uninstall cffi, then install it again allowing only the binary wheel for your platform rather than a source build. Success check: the install reports a wheel file whose name matches your Python version and bitness.

**Install the Microsoft Visual C++ runtime.** Add the current Visual C++ redistributable for your architecture and restart the shell afterwards. Expected: the runtime shows in installed programs and a fresh terminal opens cleanly.

**Verify the backend import directly.** Import the backend module on its own before importing packages that depend on it, such as cryptography. Success check: the backend import prints no error and reports its version.

**Check for a shadow copy.** Search the project folder and the app folder for a stray _cffi_backend file from another Python version that could be loaded first. Expected: the only backend file found lives in the active environment site-packages.