Fix Microsoft AutoUpdate Helper Tool Code-Signing Errors on Mac
Question details
Resolve a Microsoft AutoUpdate error in which the privileged helper tool exists but is reported as unsigned.

- Product
- Microsoft AutoUpdate
- Device & OS
- macOS
- Scenario
- A user is updating Microsoft Office on a Mac and needs AutoUpdate to recognize its privileged helper tool.
- Observed behavior
- The helper tool is present, but AutoUpdate reports it as not code-signed.
Confirm that the helper file exists at /Library/PrivilegedHelperTools/com.microsoft.autoupdate.helper. You need an administrator account to run the permission commands; on a managed Mac, check with your IT administrator before changing system directory permissions.
Correct the AutoUpdate Helper Tool Permissions
Use this approach when restrictive permissions prevent AutoUpdate from reading an existing helper tool.
Changing permissions does not sign an unsigned file. If the helper has an invalid signature, reinstall Microsoft AutoUpdate from an official Microsoft source.
Open Applications > Utilities > Terminal and run `ls -ld /Library/PrivilegedHelperTools` followed by `ls -l /Library/PrivilegedHelperTools/com.microsoft.autoupdate.helper`.
In Terminal, run `sudo chmod o+r /Library/PrivilegedHelperTools/com.microsoft.autoupdate.helper` and enter your administrator password when prompted.
If the directory is set to 700 and the error persists, run `sudo chmod 755 /Library/PrivilegedHelperTools`. This changes access to a system-wide directory used by other apps, so review the change with IT on a managed Mac.
Open a Microsoft Office app and select Help > Check for Updates. In the relevant AutoUpdate log, look for `helperToolCodesigned: YES` to confirm that the helper is recognized as signed.

Use WPS Office as an Alternative on Your Mac
WPS Office is a free, lightweight alternative with a familiar interface for working with Office files. Its format compatibility helps you move existing documents, spreadsheets, and presentations without depending on Microsoft AutoUpdate.

Frequently Asked Questions
Why can AutoUpdate report that an existing helper is unsigned?
Restrictive file or directory permissions can prevent AutoUpdate from reading the helper. Check both paths with `ls -l` and `ls -ld` in Terminal.
Does changing permissions add a code signature to the helper?
No. The chmod commands only change access permissions. If the helper is genuinely unsigned or its signature is invalid, reinstall Microsoft AutoUpdate from Microsoft's official support site.
How do I check whether the fix worked?
In a Microsoft Office app, select Help > Check for Updates, then check the relevant AutoUpdate log for `helperToolCodesigned: YES`.
Should I change the PrivilegedHelperTools directory to 755 immediately?
First inspect it with `ls -ld /Library/PrivilegedHelperTools` and try making the helper readable. If the directory is set to 700 and the error remains, consider the 755 command; consult IT first on a managed Mac because the directory is shared by other apps.




