Skip to main content

Want to switch from the Mole Mac site to the Windows site?

Go to the Windows site
Mole
MacWindows
Features Tested apps Testimonials Pricing FAQ Blog
EnglishEN 简体中文中 繁體中文繁 日本語日 한국어한 FrançaisFR DeutschDE ItalianoIT EspañolES PortuguêsPT NederlandsNL
Buy Download

    Help, documentation, releases, and articles.

    Blog

    Microsoft AutoUpdate on Mac: Settings and Shared Components

    Apps & MaintenancePublished July 8, 2026Updated October 31, 20266 min read

    Microsoft AutoUpdate can remain on a Mac after you stop using an Office app. Before removing it, check whether another installed Microsoft app still uses it, and separate automatic updating from permission to run in the background. Changing one does not establish that the other is disabled.

    Identify What AutoUpdate Is Updating

    Microsoft Learn describes Microsoft AutoUpdate, or MAU, and lists supported applications beyond Word and Excel. Review AutoUpdate's actual app list before deciding it is an Office leftover.

    Microsoft's Office update instructions distinguish apps installed from Microsoft's website from apps installed through the Mac App Store. The latter use App Store updates. That distinction applies to those apps, not automatically to every Microsoft product on the Mac.

    What you find What it establishes Next step
    An installed app appears in AutoUpdate There is a reason to preserve its update route Keep MAU and review its settings
    Office came from the Mac App Store Those Office apps use the App Store update route Check other MAU consumers separately
    No familiar Office app remains Only that those apps were removed Check the complete MAU app list and managed software

    Record the apps you intend to keep. Do not remove shared update components merely because you deleted Word or no longer have a Microsoft 365 subscription.

    Why It Appears in Background Items

    Microsoft's background-permission guidance explains that MAU detects, downloads and applies updates in the background. On macOS Ventura and later, macOS exposes background permissions in its settings.

    The presence of a background entry alone does not identify a fault. Microsoft says blocking AutoUpdate can cause an Office app to display an update error, asking you to allow it again. A background-permission switch is therefore a poor substitute for choosing how updates should be handled.

    If you disabled it and now see that error, use the linked Microsoft instructions to restore its background permission, then check for updates again. Leave managed-device policy to your administrator.

    Change Update Behavior in AutoUpdate

    Open an Office app you still use, such as Word, and open its update check from the help menu. Microsoft's update instructions above document this route. Record the current automatic-update selection before changing it.

    If your version shows an option for keeping Microsoft apps up to date automatically, change that option there rather than deleting launch files. Turning it off means taking responsibility for checking and applying app updates yourself; it is not a promise that MAU will never appear or update itself.

    Microsoft's current preference reference distinguishes the following behavior:

    Preference value Documented behavior
    AutomaticDownload Checks regularly and applies updates automatically
    AutomaticCheck Checks regularly and opens the interface when updates are found
    Manual Checks for MAU's own updates, without automatically offering other app updates

    These are preference identifiers, not a promise of three choices in your window. The reference says Manual has been removed from the GUI. If the controls differ or are managed, do not force an old screenshot's layout onto the current version.

    Locate the App and Its Launch Agent

    Microsoft Learn's msupdate instructions locate the updater inside this system-wide directory:

    /Library/Application Support/Microsoft/MAU2.0/Microsoft AutoUpdate.app
    

    A Microsoft staff answer on Microsoft Q&A also identifies these associated items. This is a component inventory, not a deletion sequence:

    Location Component
    /Library/LaunchAgents/com.microsoft.update.agent.plist Launch agent
    /Library/LaunchDaemons/com.microsoft.autoupdate.helper.plist Helper launch daemon
    /Library/PrivilegedHelperTools/com.microsoft.autoupdate.helper Helper executable

    Keep /Library distinct from ~/Library. Do not erase a whole Microsoft support directory, remove a licensing helper, or change executable permissions just to stop an updater window.

    Remove It Only When No App Still Needs It

    Treat removal as a separate decision after removing all apps that actually rely on MAU. The supported-app list is wider than Office, and a Mac App Store copy of Word does not prove another installed app is independent of MAU.

    This is a conservative keep-or-remove rule, not a claim that Microsoft publishes a universal MAU removal checklist. The official pages above establish update responsibilities and component locations; they do not justify deleting every Microsoft-named file. On a managed Mac, ask the administrator to confirm the consumers and removal method.

    For Office removal and Outlook data, follow the Office removal article and the tested Office guide. Keep that data decision separate from the updater decision.

    Verify the Change and Restore Updating

    After a settings change, reopen AutoUpdate and confirm the selection, run an update check, then reopen an app you kept. Check the reported update result rather than treating a closed window as success. Restore the previous automatic-update choice if you no longer want to maintain updates manually.

    If MAU is missing or damaged, Microsoft's repair guidance points to its latest installer. Reinstall through that official source and retry the update check. Do not delete more helpers in response to a missing-helper error.

    For broader decisions, see Mac app update sources and startup items.

    Where Mole Fits

    Mole Mac filters shared Microsoft AutoUpdate paths out of Homebrew-derived uninstall leftovers and refuses its system-wide Microsoft support tree as an uninstall remnant. Its orphan-service scanner also excludes com.microsoft.autoupdate.helper unconditionally. Removing an Office app with Mole is not a request to remove this shared updater; use AutoUpdate itself to manage its update behavior.

    FAQ

    Can I Remove AutoUpdate After Deleting Word?

    Deleting Word alone does not establish that MAU is unused. Check other registered apps and managed software first, and preserve the updater while an installed app relies on it.

    Does Turning Off Automatic Updates Stop Every MAU Process?

    No. Update behavior and background permission are separate, and Microsoft's Manual preference still permits MAU to check for its own updates.

    What If Office Says AutoUpdate Cannot Run?

    Check Microsoft's background-permission instructions first. If the updater is missing or damaged, use its official installer and verify that an update check works afterward.

    Mac running low on space or slowing down? Mole can clean out the junk, remove apps completely and keep macOS in shape.

    Try Mole

    Keep reading

    • Apps & MaintenanceDo You Need a Mac Cleaner5 min read
    • Apps & MaintenanceGoogleUpdater and the Google LLC Background Item on Mac5 min read
    • Apps & MaintenanceA Mac Maintenance Checklist That Prevents Problems5 min read

    Mole · 鼴

    Cleanup, software, and status for your Mac.

    v1.19.0 (353) · 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

    For Windows 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.