Load Controls in Forms3: registry value loadcontrolsinformsUserHKCU\software\policies\microsoft\vba\security

Policy ID: L_LoadControlsinForms3
Scope: User Configuration
Supported on: At least Windows Server 2008 R2 or Windows 7
Source: Microsoft 365 Apps / Office Administrative Templates (version 5568.1000)
Category: Microsoft Office 2016 › Security Settings

This policy setting allows you to control how ActiveX controls in UserForms should be initialized based upon whether they are Safe For Initialization (SFI) or Unsafefor Initialization (UFI).

ActiveX controls are Component Object Model (COM) objects and have unrestricted access to users' computers. ActiveX controls can access the local file system and change the registry settings of the operating system. If a malicious user repurposes an ActiveX control to take over a user's computer, the effect could be significant. To help improve security, ActiveX developers can mark controls as Safe For Initialization (SFI), which means that the developer states that the controls are safe to open and run and not capable of causing harm to any computers. If a control is not marked SFI, the control could adversely affect a computer--or it's possible the developers did not test the control in all situations and are not sure whether their control might be compromised at some future date.SFI controls run in safe mode, which limits their access to the computer. For example, a worksheet control can both read and write files when it is in unsafe mode, but perhaps only read from files when it is in safe mode. This functionality allows the control to be used in very powerful ways when safety wasn't important, but the control would still be safe for use in a Web page. If a control is not marked as SFI, it is marked Unsafe For Initialization (UFI), which means that it is capable of affecting a user's computer. If UFI ActiveX controls are loaded, they are always loaded in unsafe mode.

If you enable this policy setting, you can choose from four options for loading controls in UserForms:

1- For a UFI or SFI signed control that supports safe and unsafe mode, load the control in unsafe mode. For an SFI signed control that only supports a safe mode configuration, load the control in safe mode. This option enforces the default configuration.

2 - Users are prompted to determine how UserForm forms will load. The prompt only displays once per session within an application. When users respond to the prompt, loading continues based on whether the control is UFI or SFI:

- For a UFI signed control, if users respond Yes to the prompt, load the control in unsafe mode. If users respond No, load the control using the default properties.

- For an SFI signed control that supports both safe and unsafe modes, if users respond Yes to the prompt, load the control in unsafe mode. If users respond No, load the control using safe mode. If the SFI control can only support safe mode, load the control in safe mode. This option is the default configuration in the Microsoft Office 2016 release.

3 - Users are prompted to determine how UserForm forms will load. The prompt only displays once per session within an application. When users respond to the prompt, loading continues based on whether the control is UFI or SFI:

- For a UFI signed control, if users respond Yes to the prompt, load the control in unsafe mode. If users respond No, load the control with its default properties.

- For an SFI signed control, load in safe mode.

4 - For a UFI signed control, load with the default properties of the control. For an SFI signed control, load in safe mode (considered to be the safest mode).

If you disable or do not configure this policy setting, the behavior is as if you enable this policy setting and then select option 1.

See the full description on the Group Policy page ›

Registry

loadcontrolsinforms

REG_DWORDUser

HKCU\software\policies\microsoft\vba\security Current key

Enabled value: Depends on the option value
Element: Load Controls in Forms3:

Options
Item	Stored value
1	1
2	2
3	3
4	4

Apply with .reg · CMD · PowerShell

.reg

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\software\policies\microsoft\vba\security]

; Options (use only one)
; 1
"loadcontrolsinforms"=dword:00000001
; 2
"loadcontrolsinforms"=dword:00000002
; 3
"loadcontrolsinforms"=dword:00000003
; 4
"loadcontrolsinforms"=dword:00000004

CMD

:: Options (use only one)

:: 1
reg add "HKCU\software\policies\microsoft\vba\security" /v "loadcontrolsinforms" /t REG_DWORD /d 1 /f
:: 2
reg add "HKCU\software\policies\microsoft\vba\security" /v "loadcontrolsinforms" /t REG_DWORD /d 2 /f
:: 3
reg add "HKCU\software\policies\microsoft\vba\security" /v "loadcontrolsinforms" /t REG_DWORD /d 3 /f
:: 4
reg add "HKCU\software\policies\microsoft\vba\security" /v "loadcontrolsinforms" /t REG_DWORD /d 4 /f

PowerShell

# Common: create the key
New-Item -Path 'HKCU:\software\policies\microsoft\vba\security' -Force | Out-Null

# Options (use only one)
# 1
New-ItemProperty -Path 'HKCU:\software\policies\microsoft\vba\security' -Name 'loadcontrolsinforms' -PropertyType DWord -Value 1 -Force | Out-Null
# 2
New-ItemProperty -Path 'HKCU:\software\policies\microsoft\vba\security' -Name 'loadcontrolsinforms' -PropertyType DWord -Value 2 -Force | Out-Null
# 3
New-ItemProperty -Path 'HKCU:\software\policies\microsoft\vba\security' -Name 'loadcontrolsinforms' -PropertyType DWord -Value 3 -Force | Out-Null
# 4
New-ItemProperty -Path 'HKCU:\software\policies\microsoft\vba\security' -Name 'loadcontrolsinforms' -PropertyType DWord -Value 4 -Force | Out-Null