

:: Path to the uninstaller (see path definition above) set UNINSTALLER = %ProgramFiles%\GNU\GnuPG\gpg 4win-uninstall.exe set PROGRAM_FILES = %ProgramFiles% if not "%ProgramFiles(x86)%" = "" set PROGRAM_FILES = %ProgramFiles(x 86)% Depending on the result (either :: remove completes or timeout occurs) it exits with different ecit code: :: code 0: all fine, program uninstalled :: code 1: failed, uninstaller still exissts after timeout :: This is required to evaluate the target of %ProgramFiles% on 64-bit systems :: Please note that this is required only if you uninstall a 32-bit application. :: It is able to run an uninstaller application and then to monitor if the :: uninstaller is erased from the system. Please add the author of the script if you know echo off :: This script is an extended uninstaller script for programs which have tricky :: uninstallers (e.g. I didn't write it myself but I can't find the webpage again, where I took it from. I was able to solve this problem by using an uninstaller-script that takes care of the issue. The uninstall-process is completed with error code zero but the uninstall still fails according to wpkg. Įxecuting the uninstall-command via wpkg results sometimes in an error. You may want to fall back to a GNU Privacy Guard 1.4.11 binary for Windows from. See a question about this on the GPG4Win forum at

The 2.1.0 installer reboots straight after installation, whether it's the GUI installer doing so without prompting, or the silent installer.Installation of 2.1.0 and 2.3.x gives "Error: StartService: ec=1-56" and never fully completes, stop the DirMngr -Service to prevent this."/language=Deutsch", otherwise there's a popup with a listbox. starting from 2.2.4, the gpg4win-uninstall.exe needs a language parameter, e.g.
