{
	"id": "e1e538c3-ef6f-4d68-b3ef-b098e084955e",
	"created_at": "2026-04-06T02:12:07.423428Z",
	"updated_at": "2026-04-10T03:22:03.891537Z",
	"deleted_at": null,
	"sha1_hash": "c4b90e0bfb62ae95b3ca260114fadb4cdeee7128",
	"title": "How to turn off Visual Basic for Applications when you deploy Office - Office",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 49904,
	"plain_text": "How to turn off Visual Basic for Applications when you deploy\r\nOffice - Office\r\nBy simonxjx\r\nArchived: 2026-04-06 02:03:28 UTC\r\nThis article describes how to disable Microsoft Visual Basic for Applications during the deployment of the\r\nversions of Microsoft Office that are listed in the \"Applies To\" section.\r\nVisual Basic for Applications, although not a security risk in itself, can be used by other users to compromise\r\nsecurity. However, you can install Office without Visual Basic for Applications support.\r\nThe following methods can be used to remove Visual Basic for Applications support in Office.\r\nNote The Custom Maintenance Wizard and the Custom Installation Wizard can be used only with the Enterprise\r\nedition of Microsoft Office.\r\nNote\r\nThis method can be used only with the Enterprise edition of Microsoft Office.\r\nThe Custom Installation Wizard is included with the Microsoft Office Resource Kit (ORK). The wizard can be\r\nused to create a custom TRANSFORM file that is used with Setup.exe to customize the installation of Office\r\nfeatures during Setup. To create a TRANSFORM file that removes Visual Basic for Applications support during\r\ninstallation, follow these steps.\r\nNote\r\nTo create the TRANSFORM file , you must install the ORK. You can install the ORK from the ORK folder on the\r\nCD for an Enterprise edition of Office.\r\n1. Start the Custom Installation Wizard, and then click Next.\r\n2. In the Name and path of MSI file to open box, type the full path and file name of your .msi file, and then\r\nclick Next two times.\r\nNote An .msi file is included with the Office installation CD. For example, type D:\\PROPLUS.MSI.\r\n3. In the Name and path of MST file box, type the path and file name with which you want to save your\r\ncustom Setup file, and then click Next three times.\r\n4. In the Set Feature Installation States page of the Custom Installation Wizard, in the For each of the\r\nfollowing Microsoft Office features, click to select the default installation state list, expand Office\r\nShared Features.\r\nhttps://docs.microsoft.com/en-us/previous-versions/office/troubleshoot/office-developer/turn-off-visual-basic-for-application\r\nPage 1 of 5\n\n5. Click Visual Basic for Applications, and then click Not Available, Hidden, Locked.\r\nYou receive the following message:\r\nYou have chosen not to install Visual Basic for Applications. Microsoft Access requires this\r\ncomponent and will not be installed if you continue. Additional features in Microsoft Office,\r\nincluding some wizards and templates, will not work properly.\r\nDo you want to install Microsoft Office without Visual Basic for Applications?\r\n6. Click Yes, and then click Finish. After the transform file is created, click Exit to exit the Custom\r\nInstallation Wizard.\r\nFor more information about how to cutomize Office installations and about how to use the Custom Installation\r\nWizard, go to the following Microsoft websites:\r\nOffice 2016\r\n(Preview) Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool\r\nOffice 2013\r\nUse the OCT to customize Office 2013\r\nCustomize Setup before installing Office 2013\r\nOffice 2010\r\nCustomize Office 2010\r\nThe 2007 Office system\r\nCustomize the 2007 Office system\r\nNote\r\nThis method can be used only with the Enterprise edition of Microsoft Office.\r\nThe Custom Maintenance Wizard is included with the Microsoft Office Resource Kit (ORK). The wizard is used\r\nto create a Custom Maintenance Wizard customization file (CMW file) that can be used to update an existing\r\nOffice installation. To create a CMW file to remove Visual Basic for Applications support, follow these steps.\r\nNote\r\nTo create the CMW file , you must install the ORK. You can install the ORK from the ORK folder on the CD for\r\nan Enterprise edition of Office.\r\n1. Start the Custom Maintenance Wizard, and then click Next.\r\nhttps://docs.microsoft.com/en-us/previous-versions/office/troubleshoot/office-developer/turn-off-visual-basic-for-application\r\nPage 2 of 5\n\n2. In the Name and path of MSI file to open box, type the full path and file name of your .msi file, and then\r\nclick Next two times.\r\nNote An .msi file is included with the Office installation CD. For example, for Microsoft Office XP\r\nProfessional Plus, you would type D:\\PROPLUS.MSI.\r\n3. Click Next two times, and then on the Set Feature Installation States page, in the For each of the following\r\nMicrosoft Office features, click to select the desired installation state list, expand Office Shared\r\nFeatures.\r\n4. Click Visual Basic for Applications, and then click Not Available, Hidden, Locked.\r\nYou receive the following message:\r\nYou have chosen not to install Visual Basic for Applications. Microsoft Access requires this\r\ncomponent and will not be installed if you continue. Additional features in Microsoft Office,\r\nincluding some wizards and templates, will not work properly.\r\nDo you want to install Microsoft Office without Visual Basic for Applications?\r\n5. Click Yes, and then click Finish. After the Custom Maintenance Wizard configuration file (CMW file) is\r\ncreated, click Exit to exit the Custom Maintenance Wizard.\r\nSystem Policy Editor is included with the Microsoft Office Resource Kit (ORK). System Policy Editor can be\r\nused to turn off Visual Basic for Applications support for Office programs.\r\nTurning on the Disable VBA for Office applications policy sets the VBAOFF DWORD value to 1 in the\r\nfollowing registry subkey:\r\nOffice 2016\r\nHKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Office\\16.0\\Common\r\nOffice 2013\r\nHKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Office\\15.0\\Common\r\nOffice 2010\r\nHKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Office\\14.0\\Common\r\nThe 2007 Office system\r\nHKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Office\\12.0\\Common\r\nOffice 2003\r\nHKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Office\\11.0\\Common\r\nOffice XP\r\nhttps://docs.microsoft.com/en-us/previous-versions/office/troubleshoot/office-developer/turn-off-visual-basic-for-application\r\nPage 3 of 5\n\nHKEY_LOCAL_MACHINE\\Software\\Policies\\Microsoft\\Office\\10.0\\Common\r\nThis registry setting prevents Microsoft Excel, Microsoft FrontPage, Microsoft Outlook, Microsoft PowerPoint,\r\nMicrosoft Publisher, and Microsoft Word from using Visual Basic for Applications.\r\nDuring or after an Office installation, you can specify the features that you want installed. To do this, follow these\r\nsteps:\r\n1. In Office Setup, on the Choose installation options for all Office applications and tools page, in the\r\nFeatures to install list, expand Office Shared Features.\r\n2. Click Visual Basic for Applications, and then click Not Available.\r\n3. Continue the Office installation or update.\r\nMicrosoft Access requires Visual Basic for Applications. To enable the installation of Access and disable Visual\r\nBasic for Applications in all other Office programs, install a stand-alone version of Microsoft Access, and then\r\ninstall Office as a custom installation that has Visual Basic for Applications disabled.\r\nThe VBAOff registry subkey can be added manually to disable Visual Basic for Applications functionality for all\r\nusers on a computer after Office is installed. To add the VBAOff registry key, follow these steps:\r\n1. Exit your version of all Office programs.\r\n2. Click Start, click Run, type regedit, and then click OK.\r\n3. Locate and then click to select one of the following registry keys, depending on the version of the product\r\nthat you are using:\r\nFor Office 2016, locate and then click to select\r\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\16.0\\Common.\r\nFor Office 2013, locate and then click to select\r\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\15.0\\Common.\r\nFor Office 2010, locate and then click to select\r\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\14.0\\Common.\r\nFor the 2007 Office system, locate and then click to select\r\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\12.0\\Common.\r\nFor Office 2003, locate and then click to select\r\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\11.0\\Common.\r\nFor Office XP, locate and then click to select\r\nHKEY_LOCAL_MACHINE\\Software\\Microsoft\\Office\\10.0\\Common.\r\n4. After you select the key that is specified in step 3, point to New on the Edit menu, and then click DWORD\r\nValue.\r\nhttps://docs.microsoft.com/en-us/previous-versions/office/troubleshoot/office-developer/turn-off-visual-basic-for-application\r\nPage 4 of 5\n\n5. Type VBAOff, and then press ENTER.\r\n6. Right-click VBAOff, and then click Modify.\r\n7. In the Value data box, type 1, and then click OK.\r\n8. On the File menu, click Exit to quit Registry Editor.\r\nNote You can also disable Visual Basic for Applications functionality for the current user only. You can do this by\r\nselecting the HKEY_CURRENT_USER path for the appropriate product that is shown in step 3.\r\nFor more information, view the article in the Microsoft Knowledge Base:\r\n287567 Considerations for disabling VBA in Office XP\r\nSource: https://docs.microsoft.com/en-us/previous-versions/office/troubleshoot/office-developer/turn-off-visual-basic-for-application\r\nhttps://docs.microsoft.com/en-us/previous-versions/office/troubleshoot/office-developer/turn-off-visual-basic-for-application\r\nPage 5 of 5",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://docs.microsoft.com/en-us/previous-versions/office/troubleshoot/office-developer/turn-off-visual-basic-for-application"
	],
	"report_names": [
		"turn-off-visual-basic-for-application"
	],
	"threat_actors": [],
	"ts_created_at": 1775441527,
	"ts_updated_at": 1775791323,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/c4b90e0bfb62ae95b3ca260114fadb4cdeee7128.pdf",
		"text": "https://archive.orkl.eu/c4b90e0bfb62ae95b3ca260114fadb4cdeee7128.txt",
		"img": "https://archive.orkl.eu/c4b90e0bfb62ae95b3ca260114fadb4cdeee7128.jpg"
	}
}