Blender 4.x Import Settings detection of portable installations on Windows

Configuration migration gap for portable deployments

Blender isolates each major version's configuration in a versioned directory (e.g., %APPDATA%\Blender Foundation\Blender\4.0\ on Windows). On first launch of a new major release, the splash screen presents an Import Settings option that copies preferences, keymaps, themes, and enabled add-on metadata from the most recent previous version. However, the import logic relies on detecting the prior version's configuration path through the standard installed location.

Portable installations — where Blender runs from a self-contained folder with a portable subdirectory — do not follow the standard %APPDATA% layout. The splash-screen import routine may not locate these portable configuration directories, leaving users without a guided migration path. Additionally, the import process copies add-on metadata (enabled/disabled state) but not the add-on modules themselves, and it excludes custom scripts stored in scripts/startup or scripts/addons.

What is the documented detection logic for locating the previous version's configuration when the prior installation was portable? Does the import dialog fall back to a manual directory selection, or does it silently skip migration? Are there environment variables or command-line flags that can direct the import routine to a non-standard configuration path?