release_2.4.0

Cross-Integrity Mount (WinFsp)

Mounted drives are now visible to both standard and elevated (Administrator) processes, solving the classic Windows UAC isolation issue.

• New setting: "Cross-integrity mount" in Settings > Security Settings. When enabled, archives are mounted to a folder path with a permissive security descriptor (Everyone Full Access), making the drive accessible from any process regardless of integrity level.
• Automatic enforcement: When SimpleZipDrive_WinFsp runs as Administrator, cross-integrity mode is automatically enabled — no manual configuration needed.
• Configurable mount folder: Set a custom base folder for cross-integrity mounts, or leave empty to use the default (%LOCALAPPDATA%\SimpleZipDrive\Mounts).
• Browse button: Folder picker for the mount folder setting.

Note: Drive letter mounts cannot bypass UAC isolation due to Windows OS limitations. Cross-integrity mode uses folder-based mounting instead.

Fixes

• Auto-open for folder mounts: The "Auto-open in Explorer" feature now correctly opens folder-based mount points instead of falling back to the Documents folder. Uses explorer.exe /root for proper path handling.
• Unmount button styling: The Unmount button now changes color when enabled/disabled, matching the Mount button's visual behavior (both WinFsp and Dokan variants).
• Temp folder cleanup: Orphaned temp directories (e.g. from crashed sessions) are now cleaned from both %TEMP%\SimpleZipDrive and %LOCALAPPDATA%\SimpleZipDrive at startup.
• Folder name truncation: Cross-integrity mount folder names no longer truncate at 32 characters. Archive names like Assassin's Creed III (USA) (En,Fr,Es,Pt) now produce full folder names.
• Null-safety: Fixed potential NullReferenceException in Settings window when mount folder text is null.
• Test stability: Fixed parallel test interference issues in ServiceProvider and ErrorLogger test collections.

Full Changelog: release_2.3.0...release_2.4.0