Custom UI Runtime Error in Visual Studio Tools for Office Design-Time Adaptor for Excel
This error drove me crazy because I could only find pieces of the answer, but never the whole answer. Here’s the whole answer that resolved the problem for me.
The Error: The Call to GetCustomUI() for RibbonID “Microsoft.Excel.Workbook” failed.
It typically comes up after an installation of Microsoft Office and Visual Studio. Somehow the combination of these two causes the problem and Microsoft hasn’t figured out why, or how. There is a workaround.
Step 1: Open Excel in Administrator mode
There are two ways to do this.
A) Right click on the Excel shortcut and click on Properties in the context menu. In the properties dialogue click the Advanced button. In the Advanced Properties dialogue check off “Run as Administrator” and click OK on all the open dialogues.
B) Click the Start Button, or the Windows button. Type Excel in the search box. Press SHIFT + CTRL + Enter
Open a blank workbook
Step 2: Activate the Developer Tab in the Ribbon if isn’t available
In the workbook file menu select “Options” and in the Options menu select “Customize Ribbon”.
In the right hand list of the Ribbon Customizer you should see a list of tabs. Make sure the “Developer” tab is selected.
Click OK to close the Customizer
Step 3: Turn off the “Visual Studio Tools for Office Design-Time Adaptor for Excel”
In the Ribbon select the Developer tab.
In the Developer tab select the “COM Add-Ins”
In the COM Add-Ins dialogue look for the “Visual Studio Tools of Office Design-Time Adaptor for Excel” add in. You’ll likely see one for every version of Visual Studio that you’ve installed on this particular machine. Uncheck all of them and click OK out of the dialogue
That should immediately resolve the problem.
Once you open Excel in non-Administrator mode you might encounter the problem again. If that’s the case follow the above steps without opening Excel as an Administrator.
I have the same problem in Excel 2013 and this resolved it. THNX.
This works like a charm!
You rock! Thanks.
It worked. Thanks!
This annoyed me greatly! Thank you for saving me lots of annoyances!! 🙂
thx, cristal clear info
Worked like charm… Thanks.
You’re welcome!
Yes, it worked. Thanks!
Thanks. It worked.
Perfect! Thank you!
I my case it was a document creator for a Samsung scanner that was causing the problem.
Thanks. it’s working
Finally a resolution that actually works. Thanks so much for posting this!
Yeah, but I need that on as I’m doing VSTO development. This doesn’t really solve the problem.
solucionado gracias
Great help. Thanks a lot.
It works for me. Thank you.
thank you very much – worked for me
I am not sure why I want to disable something in stead of fixing it. Do you know the root cause and how to do fix that? (is Microsoft working on this?)
I’m not aware of any fix to this problem from Microsoft. This bug showed up in older versions of Excel, so maybe Office 365 has corrected this problem?
Worked fine for me today. Thanks a lot for saving me much time of annoying search.
Thanks So MUCH!!! I’ve been fighting this for several weeks and finally located your site. Thanks for sharing with the community and being thorough about how to fix it!
You’re welcome! I’m glad it helped.