Menu ▾ ▴

New Plugin: KeeAnywhere - Software startup issue during plugin loading.

2026-11-05
6 days ago
  • Antonio Saracco

    Antonio Saracco - 2026-11-05

    Hello everyone,

    This morning, when opening my KeePass client, I received a notification that a new version was available and that the plugins currently in use were compatible. I downloaded and installed version 2.62, but upon the first launch I received an error message related to the KeeAnywhere plugin: "Attempted to perform an unauthorized operation". The error occurs during the loading of an AWS library.

    I checked and there does not appear to be an updated version of the plugin available.

    I am sharing this information for awareness. I resolved the issue by downgrading to the previous KeePass version, and I would like to ask whether anyone else has experienced the same problem.

    Thanks!

     
  • Jayson Sosweet

    Jayson Sosweet - 2026-11-05

    I can confirm that ! Just had to downgrade to 2.61 and it works again properly.

     
  • Billolo-J

    Billolo-J - 2026-11-05

    Hi there,

    I report the same error during my fresh Keepass 2.62 installation startup. I'm using the KeeAnywhere plugin only. Attached to this message is a screenshot of the error I got.
    Rolled back to Keepass v1.61.1 to keep it running.
    Thank you for your attention and fixing of this 🙏🏼
    Best regards,

    B-J

     
  • Dominik Reichl

    Dominik Reichl - 2026-11-05

    See here:
    https://sourceforge.net/p/keepass/bugs/2450/

    Best regards,
    Dominik

     
  • Ivan Petrov

    Ivan Petrov - 2026-11-06

    Hi everyone,

    If you're encountering compilation or PlgxException issues with KeeAnywhere (often caused by Windows %TEMP% path restrictions or missing compilation tools during .plgx execution), installing the unpacked binary release directly into a subfolder in Plugins is the standard workaround.

    I've put together a small Batch script that automates this entire process:

    Elevates to Administrator if required.

    Gracefully stops KeePass.exe.

    Cleans up old KeeAnywhere*.plgx files and temp cache.

    Queries the official GitHub API for the latest release .zip.

    Downloads, extracts it directly into Plugins\KeeAnywhere, and launches KeePass.

    Here is the script (save it as Fix-KeeAnywhere.bat and run it):

    DOS

    @echo off
    setlocal EnableExtensions
    chcp 65001 >nul
    title KeeAnywhere Plugin Fix v2.0
    
    :: ==========================================
    :: KeeAnywhere Plugin Fix v2.0
    :: Automatic latest release download
    :: ==========================================
    
    :: Check for Administrator privileges
    net session >nul 2>&1
    if %errorlevel% neq 0 (
        echo Administrator privileges required...
        powershell -NoProfile -Command "Start-Process -FilePath '%~f0' -Verb RunAs"
        exit /b
    )
    
    set "KP=C:\Program Files\KeePass Password Safe 2\KeePass.exe"
    set "PLUGIN=C:\Program Files\KeePass Password Safe 2\Plugins"
    set "DEST=%PLUGIN%\KeeAnywhere"
    set "ZIP=%TEMP%\KeeAnywhere.zip"
    set "REPO=https://api.github.com/repos/Kyrodan/KeeAnywhere/releases/latest"
    
    echo.
    echo ==========================================
    echo       KeeAnywhere Plugin Fix v2.0
    echo ==========================================
    echo.
    
    :: Check KeePass location
    if not exist "%KP%" (
        echo [ERROR] KeePass.exe not found!
        goto :ERROR
    )
    
    :: Terminate KeePass
    echo [1/5] Terminating KeePass process...
    taskkill /IM KeePass.exe /F >nul 2>&1
    
    :: Clean up old files
    echo [2/5] Cleaning up old plugin files...
    
    del /F /Q "%PLUGIN%\KeeAnywhere*.plgx" >nul 2>&1
    
    if exist "%DEST%" rmdir /S /Q "%DEST%"
    
    if exist "%LOCALAPPDATA%\Temp\KeePass" (
        rmdir /S /Q "%LOCALAPPDATA%\Temp\KeePass"
    )
    
    :: Create target directory
    mkdir "%DEST%" 2>nul
    
    :: Fetch latest release info
    echo [3/5] Checking for latest release on GitHub...
    
    set "URL="
    
    for /f "usebackq delims=" %%U in (`powershell -NoProfile -Command "$ProgressPreference='SilentlyContinue'; (Invoke-RestMethod -Uri '%REPO%').assets | Where-Object { $_.name -like 'KeeAnywhere-*.zip' } | Select-Object -First 1 -ExpandProperty browser_download_url"`) do (
        set "URL=%%U"
    )
    
    if not defined URL (
        echo [ERROR] No ZIP asset found in latest GitHub Release!
        goto :ERROR
    )
    
    :: Download
    echo [4/5] Downloading latest release...
    
    powershell -NoProfile -ExecutionPolicy Bypass -Command "$ProgressPreference='SilentlyContinue'; Invoke-WebRequest -Uri '%URL%' -OutFile '%ZIP%'"
    
    if errorlevel 1 (
        echo [ERROR] Download failed!
        goto :ERROR
    )
    
    if not exist "%ZIP%" (
        echo [ERROR] Downloaded ZIP archive is missing!
        goto :ERROR
    )
    
    :: Extract
    echo Extracting plugin...
    
    powershell -NoProfile -ExecutionPolicy Bypass -Command "Expand-Archive -LiteralPath '%ZIP%' -DestinationPath '%DEST%' -Force"
    
    if errorlevel 1 (
        echo [ERROR] Extraction failed!
        goto :ERROR
    )
    
    :: Cleanup download cache
    del /F /Q "%ZIP%" >nul 2>&1
    
    :: Start KeePass
    echo [5/5] Launching KeePass...
    
    start "" "%KP%"
    
    echo.
    echo ==========================================
    echo  KeeAnywhere installed successfully!
    echo  Latest GitHub Release applied.
    echo ==========================================
    echo.
    pause
    exit /b 0
    
    :ERROR
    echo.
    echo ==========================================
    echo  AN ERROR OCCURRED!
    echo  Installation aborted.
    echo ==========================================
    
    if exist "%ZIP%" del /F /Q "%ZIP%" >nul 2>&1
    
    pause
    exit /b 1
    

    Hope this helps anyone dealing with PLGX compilation failures!

     

    Last edit: Paul 2026-11-06
  • Husker Du

    Husker Du - 6 days ago

    There has already been a pull request submitted to fix this issue two days ago. It would be nice if the plugin author could review and merge the fix.

     

Log in to post a comment.