如何无需UAC弹窗卸载安装在APPDATA目录的自研应用？

Got it, let's break down why that UAC prompt is popping up even when your uninstaller is configured to run as a regular user. Here are the most likely causes and fixes:

1. Incorrect Uninstall Registry Location #

If your installer added the uninstall entry to HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall (per-machine), Windows Control Panel will attempt to modify this system-level registry key when uninstalling—this requires admin rights, hence the UAC prompt. Since your app is installed per-user (in APPDATA), you should register the uninstall entry in the user-specific registry root instead.

Fix: Update your NSIS script to write uninstall entries to HKCU instead of HKLM:

; Example per-user uninstall registry entries
WriteRegStr HKCU "Software\Microsoft\Windows\CurrentVersion\Uninstall\YourAppID" "DisplayName" "Your App Name"
WriteRegStr HKCU "Software\Microsoft\Windows\CurrentVersion\Uninstall\YourAppID" "UninstallString" "$INSTDIR\uninstall.exe"
WriteRegStr HKCU "Software\Microsoft\Windows\CurrentVersion\Uninstall\YourAppID" "DisplayIcon" "$INSTDIR\your-app.exe"
WriteRegDWORD HKCU "Software\Microsoft\Windows\CurrentVersion\Uninstall\YourAppID" "NoModify" 1
WriteRegDWORD HKCU "Software\Microsoft\Windows\CurrentVersion\Uninstall\YourAppID" "NoRepair" 1

2. Uninstaller Attempting System-Level Actions #

Even with asInvoker in the manifest, if your uninstaller tries to modify system-wide resources (like HKLM registry keys, Program Files, or system folders), Windows will trigger UAC to elevate. Double-check your uninstall script to ensure it only touches per-user locations:

• Your app's APPDATA folder ($INSTDIR)
• HKCU registry keys
• User-specific files (Documents, AppData\Roaming, etc.)

Fix: Audit your NSIS uninstall script for any actions targeting system locations. For example, if you’re deleting a registry key in HKLM, confirm it’s actually necessary—if not, move it to HKCU. Remove any commands that modify system directories or registry roots.

3. Manifest Issues (Not Embedded or Conflicting) #

Sometimes the manifest might not be properly embedded in the uninstaller, or an external manifest file in the same directory could override the embedded one.

Fix:

• Verify the embedded manifest using the Windows SDK’s mt.exe tool:

  mt.exe -inputresource:uninstall.exe;#1 -out:extracted-manifest.xml
  

  Open the extracted file to confirm it includes <requestedExecutionLevel level="asInvoker" uiAccess="false"/>.
• Ensure there’s no external uninstall.exe.manifest file in your app’s directory—this can override the embedded manifest.
• Recompile your uninstaller with the manifest properly embedded using NSIS’s Modern UI macros:

  !define MUI_MANIFEST_FILE "your-uninstall-manifest.xml"
  !include "MUI2.nsh"
  

4. Windows Installer Detection Heuristics #

Windows uses heuristics to flag installers/uninstallers, and sometimes executables with names containing "uninstall", "setup", or similar terms get incorrectly flagged for elevation—even with a valid asInvoker manifest.

Fix:

• While not ideal, you can test renaming your uninstaller to something less likely to trigger heuristics (e.g., cleanup.exe).
• Ensure your embedded manifest explicitly sets asInvoker—this should override most heuristic checks if properly applied.

After implementing these changes, test the uninstall flow via Control Panel again to confirm the UAC prompt no longer appears.

内容的提问来源于stack exchange，提问作者Uwe Keim