Microsoft Office Genuine Advantage KB949810 Breaks Office 2007 – Resolved!
Since I am developing applications for Office, I have enabled "Show add-in user interface errors" in the Advanced options of my Office applications. Yesterday, I installed KB949810, which was handed down from our WSUS server, which got the update from Microsoft.
Now, whenever I open any Office application, I receive a series of error messages all saying they couldn’t find an Office control.
Error Title: Custom UI Runtime Error in Office Genuine Advantage Add-in
Error found in Custom UI XML of "Office Genuine Advantage Add-in":
UPDATE/RESOLVED (4/19/2008 9:00AM)
Paul Berg of Microsoft has provided a patch for this issue with OGA. The patch appears to be working on my system. The add-in is still running, but I’m not receiving any error messages. His original post is in the Microsoft forums.
UPDATE (4/18/2008 7:45AM)
The solution I originally posted ended up only being a temporary fix. Now I receive the same error messages from OGAAddin. If you’re not a developer and want to hide the error messages, do the following:
I was also able to stop the error messages by deleting OGAAddin.dll, but I wouldn’t recommend anyone do that. It could lead to more problems. Hopefully Microsoft will let us know soon how to uninstall this add-in that we never should have received.
To stop the error messages, I removed the Office Genuine Advantage Add-in:
- Go into the application’s Options (i.e. click the Office Button and select "Excel Options")
- Select "Add-Ins" from the navigation pane on the left.
- At the bottom of the Add-ins form, select "COM Add-ins" in the Manage: drop-down, then click "Go…"
- In the COM Add-Ins window, highlight "Office Genuine Advantage Add-in" and click the Remove button.
- Click the Okay button.
For me, this seemed to remove it for all applications, so I didn’t receive the error message.
The default is to not show user interface errors, so unless you turned it on for a reason, you will most likely not see these messages.
Filed under: Troubleshooting | 5 Comments