A family of Microsoft word processing software products for creating web, email, and print documents.
For both issues, the underlying cause is usually leftover, obsolete Office/Mac components that AutoUpdate and Word still see, even though the main apps (EndNote, Silverlight) were removed.
- EndNote CWYW add‑in still listed in Word
The context does not provide a specific EndNote removal procedure, but it does show that Office for Mac components can persist in system folders (for example, fonts and receipts under /Library). When an Office component is fully removed, the remaining references (icons, bundles, receipts) must also be deleted so Office stops loading them.
For Word/EndNote CWYW, the equivalent cleanup is:
- Remove any remaining EndNote add‑in files from the Office add‑ins location (for example, any EndNote CWYW bundle in the Word startup/add-ins folders).
- Remove any remaining Office-related icons or references from the Dock after uninstalling, as shown for Office for Mac 2011 icons:
- Hold down CONTROL and click the Word (or other Office) icon in the Dock.
- Select Options > Remove from Dock.
If the add‑in is still listed but cannot be removed with the minus sign, that typically means Word is still seeing a file or registration entry. The documented pattern for Mac cleanup is to manually delete residual Office components from Library locations and then restart the Mac so Office rebuilds its configuration. This is the same approach used when completely uninstalling Office for Mac 2011 before reinstalling.
- Microsoft AutoUpdate keeps trying to update Silverlight / old components
The context describes two closely related scenarios on macOS:
- Old Office components (such as Microsoft Error Reporting 2.2) remain in
/Library/Application Support/Microsoft/MERP2.0, and Microsoft AutoUpdate keeps trying to update them until the folder is deleted. - Another user found that right‑clicking the icon next to an entry in the AutoUpdate error list and choosing Show in Finder reveals the stale file; deleting that file stops AutoUpdate from trying to update it.
Applied to Silverlight:
- Open Microsoft AutoUpdate.
- In the list where Silverlight (or another obsolete component) shows an error, right‑click the icon next to that entry and select Show in Finder.
- This opens the folder containing the stale component. Delete that file or folder.
- Alternatively, navigate manually to the system Library path used for old Office components and remove the obsolete folder, following the same pattern as for MERP2.0:
- Open Finder and go to the system-level /Library/Application Support/Microsoft/ folder (not the user
~/Library). - Locate the folder corresponding to the obsolete component (for example, MERP2.0 in the documented case) and delete it.
- Open Finder and go to the system-level /Library/Application Support/Microsoft/ folder (not the user
After deleting the stale component, rerun Microsoft AutoUpdate. It should no longer attempt to update Silverlight or the removed component.
This approach is consistent with the documented guidance for removing obsolete Office/Mac components and stopping AutoUpdate from repeatedly failing on them.
References: