Inno Setup打包MSYS2后非管理员运行异常问题求助
Hey there, let's work through this problem you're facing—since you're new to Inno Setup, this is a super common pitfall with system permissions, so we'll get it sorted quickly.
What's Going On Here?
The core issue is permissions and system-protected directories:
- When you install to default paths like
C:\Program Files, non-admin users don't have write access to these folders. MSYS2 needs to write config files, cache, or temporary data during runtime, and since it can't do that silently (no error pop-up), it just fails to run properly. - Admin mode works but breaks drag-and-drop because elevated processes have restricted interactions with non-elevated apps (like File Explorer)—that's a Windows UAC security feature, not an Inno Setup bug.
Step-by-Step Fixes
1. Install to a User-Writable Directory (Best Solution)
The simplest fix is to move the installation to a directory where all users (including non-admins) have full access. Replace your Inno Setup script's DefaultDirName with a user-specific path:
DefaultDirName={localappdata}\MSYS2
{localappdata} points to C:\Users\[YourUsername]\AppData\Local—a system-approved path that doesn't require admin rights for read/write operations. This eliminates permission conflicts entirely.
2. Add Permissions If You Must Use System Directories
If you need to keep MSYS2 in Program Files, explicitly grant regular users full permissions to the installation folder. Add this to your Inno Setup script's [Dirs] section:
[Dirs] Name: "{app}"; Permissions: users-full
This ensures non-admin users can modify files in the MSYS2 folder, which is critical for runtime operations.
3. Disable UAC Virtualization (Optional)
Sometimes Windows redirects write operations from protected folders to a virtualized user directory, causing MSYS2 to lose track of files. To fix this, add a registry entry to force MSYS2 to run with the invoker's permissions:
[Registry] Root: "HKLM"; Subkey: "SOFTWARE\Microsoft\Windows\CurrentVersion\AppCompatFlags\Layers"; ValueType: string; ValueName: "{app}\msys2.exe"; ValueData: "RUNASINVOKER"; Flags: uninsdeletevalue
This prevents UAC from interfering with the app's file access paths.
4. Verify MSYS2 Config Paths
Double-check that MSYS2's internal config files (like /etc/fstab or user-specific .bashrc) aren't hardcoding paths that require admin access. Use relative paths or user directory variables (like $HOME) instead.
Testing the Fix
After updating your script, rebuild the installer, then:
- Install it with a non-admin account (or run the installer as non-admin)
- Launch MSYS2 normally—no admin rights needed
- Test drag-and-drop functionality (it should work now since you're running at the same permission level as File Explorer)
If you still hit issues, check the Windows Event Viewer > Application Log for silent error messages—this will show exactly which file or operation is failing due to permissions.
内容的提问来源于stack exchange，提问作者modz2014
