Skip to main content
Mole
Features Tested apps Testimonials Pricing FAQ Blog
EnglishEN 简体中文中 繁體中文繁 日本語日 한국어한 FrançaisFR DeutschDE ItalianoIT EspañolES PortuguêsPT
Buy nowBuy Download

    Help, documentation, releases, and articles.

    Home/Apps tested with Mole

    How to uninstall Gureum on Mac

    Save Gureum input settings before removal and switch to a working macOS input source first. The official README explicitly requires that switch before uninstalling.

    Stop the input method and preserve data

    Finish typing, switch input sources, then use Activity Monitor to find the owned Gureum process and stop it. Before removing local settings, copy wanted existing ~/Library/Containers/org.youknowone.inputmethod.Gureum outside sync/removal roots and verify the copy. That sandbox was observed in the recorded test; it is not a shared vendor folder.

    The vendor's manual flow removes /Library/Input Methods/Gureum.app through Finder. The recorded extracted payload was instead ~/Library/Input Methods/Gureum.app; inspect your actual copy and remove only it, keeping other input methods. Review enabled input sources separately. If macOS denies access to the sandbox, keep it and resolve that access separately rather than bypassing it with a broad delete.

    If you installed it with Homebrew

    The cask installs a pkg and ordinary uninstall processes org.youknowone.inputmethod.Gureum:

    brew uninstall --cask gureumkim
    

    It has no zap stanza. Receipt-based removal is different from deleting only a copied per-user payload, and the command does not establish that the recorded sandbox was removed. Keep wanted settings backed up first.

    Check the result

    pgrep -ifl gureum
    ls -ld "/Library/Input Methods/Gureum.app" "$HOME/Library/Input Methods/Gureum.app" "$HOME/Library/Containers/org.youknowone.inputmethod.Gureum"
    

    No process match means no arguments matched this pattern. A printed app or container remains; retained settings or denied access are separate from app removal. Missing-path errors concern only those entries, other errors are inconclusive, and this check does not establish the enabled input-source list.

    What Mole lists

    The exact main container and Application Scripts rows are selected by default when selectable, so uncheck wanted local settings after backup. Input-method entries need individual review. The default-off Remove data and settings with apps option does not overcome macOS permissions or prove that a full pkg installation was removed.

    What this test covered

    On September 22, 2026, Gureum 1.13.2 was extracted from the official pkg and copied into the per-user Input Methods folder without running the full installer. The app, Application Scripts and temporary cache were removed, but the sandbox container remained after a macOS permission error. Full installed-input use, settings restoration and Homebrew were not tested.

    If Mac apps leave files behind after uninstalling, try Mole. I've personally tested and inspected 799 Mac apps.

    Try Mole

    Mole · 鼴

    Cleanup, software, and status for your Mac.

    v1.16.0 (301) · Release notes

    Product

    Mac Cleaner App Uninstaller Mac Optimizer Disk Analyzer System Monitor

    Support

    Help Documentation Releases Blog

    Legal

    Terms of Service Privacy Policy Refund Policy

    Resources

    CLI Tool Affiliate Program

    Connect

    Twitter hi@mole.fit

    Mole’s only official website mole.fit · Avoid installers from unknown sources

    The CLI stays free for terminal workflows.