HomeTroubleshootingAll Products: Startup"@RISK cannot be started because of the following Excel security setting ... noextensibilitycustomizationfromdocument=1"

2.20. "@RISK cannot be started because of the following Excel security setting ... noextensibilitycustomizationfromdocument=1"

Applies to: All products, releases 7.0.0 and newer

(This article is written in terms of @RISK, but the same problem could happen with any of our add-ins.)

The software installed just fine, but when I launch it I get

product cannot be started because of the following Excel security setting in the registry:

software\policies\microsoft\office\X.0\common\toolbars\excel!noextensibilitycustomizationfromdocument=1

(X is 12 in Excel 2007, 14 in Excel 2010, 15 in Excel 2013, and so on.)

You, or more likely your IT department, have set a Group Policy or Office Customization Tool setting that does not let @RISK or our other software run. "Disable UI extending from documents and templates" prevents our software from adding its tab to the Excel ribbon. (This setting was always a problem, but beginning with release 7.0.0 our software diagnoses it for you.) Please ask your IT department to remove that policy setting.

As a temporary workaround, you can follow this procedure if you have privilege to edit the System Registry. (The problem key is usually under HKEY_CURRENT_USER, but this procedure will find it wherever it is.)

  1. Open REGEDIT.
  2. Collapse the left-hand panel and click on Computer.
  3. Press Ctrl+F, and in the search window enter "NoExtensibilityCustomizationFromDocument" (without quotes, and upper/lower case doesn't matter). Under Look at, select Values and Match whole string, and deselect Keys and Data.
  4. Click Find Next. Change the displayed value from 1 to 0.
  5. Press F3, and change the value from 1 to 0. Repeat until there are no more hits. (You may find some 0 values along the way. You can ignore those, but keep searching until you've looked at all occurrences.)

Even if you're able to do this edit, you will probably have to do it again after any reboot of Windows. The best procedure is to get your IT department to remove the problem policy setting.

See also: Group Policy and Office Customization Tool Settings: Technical Reference

Last edited: 2017-04-26

This page was: Helpful | Not Helpful