Outlook ‘Group Policy Loading’ Delay on Profile Sign-In: Workaround

When you start Outlook, the status bar may display “Loading Group Policy” for 30 seconds or longer before the mailbox loads. This delay occurs because Outlook applies Group Policy settings from the Windows registry during each sign-in. The Group Policy processing can hang or take excessive time when a policy setting is misconfigured or when the client cannot reach a domain controller. This article explains why the delay happens and provides a workaround to bypass the Group Policy check during Outlook startup.

Why Outlook Displays “Loading Group Policy” During Sign-In

Outlook checks for Group Policy settings stored in the Windows registry each time a user profile loads. The registry keys are located under HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook and HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\16.0\Outlook. During startup, Outlook reads these keys to apply administrative policy restrictions such as blocking add-ins, disabling features, or enforcing security settings.

The delay occurs when the policy processing takes longer than expected. Common causes include:

• A policy setting references a network path that is unreachable, such as a file share or registry value on a remote domain controller.
• The client computer is offline or has a slow connection to the domain controller during Group Policy refresh.
• A corrupted or orphaned registry key under the Outlook policy path causes Outlook to hang while iterating through entries.
• Third-party security software intercepts registry reads and introduces latency.

The delay is not a sign of a broken Outlook installation. It is a symptom of the Group Policy client-side extension (CSE) for Microsoft Office 2016 and later versions. Outlook does not stop responding during this period; it simply waits for the policy read to complete before loading the mailbox.

Workaround: Disable Group Policy Loading in Outlook

The workaround disables Outlook’s ability to read Group Policy settings from the registry. This change does not remove any existing Group Policy settings from the Windows registry. It only tells Outlook to skip policy processing during startup. Administrative policies that were already applied before the change remain in effect until they are removed or modified through Group Policy.

Method 1: Modify the Windows Registry

1. Open Registry Editor
   Press Windows + R, type regedit, and press Enter. If prompted by User Account Control, click Yes.
2. Navigate to the Outlook Policy Key
   Go to HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook. If the path does not exist, right-click the Office key, select New > Key, and name it Outlook.
3. Create the DisableGroupPolicy DWORD
   Right-click the Outlook key, select New > DWORD (32-bit) Value, and name it DisableGroupPolicy. Double-click the new value, set the data to 1, and click OK.
4. Restart Outlook
   Close and reopen Outlook. The status bar no longer shows “Loading Group Policy” during sign-in.

To revert the change, delete the DisableGroupPolicy value or set its data to 0.

Method 2: Use Group Policy for Domain-Joined Computers

If you manage multiple computers in a domain, you can disable Outlook policy processing through the Group Policy Management Console. This method prevents the registry change from being overwritten by a future Group Policy refresh.

1. Open Group Policy Management Console
   On a domain controller or management workstation, run gpmc.msc from the Run dialog.
2. Create or Edit a Group Policy Object
   Right-click the organizational unit containing your Outlook users, select Create a GPO in this domain, and Link it here. Name the GPO Disable Outlook Policy Processing.
3. Navigate to the Outlook Policy Setting
   In the GPO editor, go to Computer Configuration > Policies > Administrative Templates > Microsoft Outlook 2016 > Miscellaneous. If the templates are not available, download the Microsoft 365 Apps administrative template files from the Microsoft Download Center and add them to the Central Store.
4. Enable the Disable Outlook Policy Processing Setting
   Double-click Disable Outlook Policy Processing, select Enabled, and click OK.
5. Force a Group Policy Refresh on Clients
   On each client computer, open Command Prompt as Administrator and run gpupdate /force. Restart Outlook.

This GPO setting writes the DisableGroupPolicy registry value to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\16.0\Outlook on the client computer. Outlook reads this key during startup and skips policy processing.

If Outlook Still Has a Delay After Disabling Group Policy

Outlook Displays “Loading Profile” Instead

After disabling Group Policy, the status bar may show “Loading Profile” for an extended period. This delay is unrelated to Group Policy. It indicates a slow connection to the Exchange server or a corrupted Outlook profile. To resolve this, create a new Outlook profile via Control Panel > Mail > Show Profiles > Add. Then set the new profile as the default.

Outlook Crashes After Applying the Registry Key

If Outlook crashes immediately after you set DisableGroupPolicy to 1, a third-party add-in or security software may be conflicting with the registry change. Start Outlook in safe mode by holding the Ctrl key while clicking the Outlook icon. If safe mode loads without crashing, disable all COM add-ins via File > Options > Add-Ins > Manage COM Add-ins > Go. Re-enable add-ins one at a time to identify the conflicting add-in.

Group Policy Is Not Actually Disabled

If the status bar still shows “Loading Group Policy” after you set DisableGroupPolicy to 1, verify that the registry key is in the correct path. The key must be under HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook. If the key exists under HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Office\16.0\Outlook, a domain-level GPO may be overwriting the per-user setting. In that case, use Method 2 to set the GPO at the computer level instead.

Registry Edit vs Group Policy: Key Differences

Item	Registry Edit (DisableGroupPolicy)	Group Policy (Disable Outlook Policy Processing)
Scope	Single user on a single computer	Multiple users on multiple computers in a domain
Persistence	May be overwritten by a Group Policy refresh at next sign-in	Persists until the GPO is removed or disabled
Administrative rights required	No (user can edit own registry)	Yes (domain administrator or delegated permissions)
Risk of breaking other policies	Low (only affects Outlook policy processing)	Low (only affects the specific GPO setting)
Revert method	Delete the DWORD or set to 0	Disable or delete the GPO link

You can now start Outlook without waiting for the Group Policy loading delay. If the delay persists after applying the registry key, verify the key location and check for conflicting domain-level policies. For advanced management, deploy the Group Policy setting across your organization using the Group Policy Management Console. Remember that disabling Group Policy processing means new policy changes for Outlook will not take effect until you re-enable the setting.