Why Word Workgroup Templates Folder Path Resets to Default Per User

You set a custom workgroup templates folder path in Word, but the next time you or another user opens the application, the path has reverted to the default location. This problem occurs because Word stores the workgroup templates path in a per-user registry key that is overwritten under specific conditions, such as Group Policy refreshes or missing folder permissions. This article explains the root cause of the reset behavior, provides step-by-step methods to lock the path using Group Policy or registry settings, and covers related failure patterns when templates fail to load correctly.

Why the Workgroup Templates Folder Path Resets Per User

The workgroup templates folder path is stored in the Windows registry under each user profile. Word reads this value from HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options\PROGRAMDIR. The value is a REG_SZ string containing the full folder path.

When you change the path in Word using File > Options > Advanced > File Locations, Word writes the new path to that registry key. However, the path resets to the default for three main reasons.

Group Policy Overwrites the Registry Key

In enterprise environments, IT administrators often deploy Group Policy Objects that set the workgroup templates path. Group Policy refreshes every 90 to 120 minutes by default and at every user logon. If the policy contains a value for the Workgroup templates path under User Configuration\Administrative Templates\Microsoft Word 2016\Miscellaneous, the policy engine overwrites the per-user registry key. The user’s manual setting is lost.

Logon Scripts Reapply the Default Path

Some organizations use logon scripts that set registry values during user sign-in. A script that writes the default path to PROGRAMDIR will reset any custom path the user configured in the previous session. This happens silently because the script runs before Word starts.

Missing Permissions on the Target Folder

If the workgroup templates folder does not exist or the user lacks read permissions, Word may fall back to the default local templates folder. The registry key still shows the custom path, but Word ignores it. This creates the illusion that the path itself has reset, when in reality Word simply cannot access the specified folder.

Steps to Stop the Workgroup Templates Path From Resetting

Use one of the following methods depending on your environment. Method 1 works for individual users. Methods 2 and 3 require administrative access and are intended for IT administrators managing multiple machines.

Method 1: Set the Path in Word and Verify Folder Permissions

This method applies when no Group Policy or logon script is overwriting the path. It also ensures that the folder itself is accessible.

1. Open the File Locations dialog
   In Word, click File > Options > Advanced. Scroll to the General section and click File Locations.
2. Change the Workgroup templates path
   Select Workgroup templates from the list and click Modify. Browse to the shared network folder or local folder and click OK. Click OK again to close File Locations.
3. Confirm the registry value is updated
   Press Windows+R, type regedit, and press Enter. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word\Options. Look for the PROGRAMDIR value. Its data should match the path you set.
4. Verify folder permissions
   Open File Explorer and navigate to the workgroup templates folder. Right-click the folder, select Properties, and go to the Security tab. Ensure your user account has at least Read and List folder contents permissions. If the folder is on a network share, confirm the share permissions also grant read access.

Method 2: Set the Workgroup Templates Path via Group Policy

This method locks the path for all users in an Active Directory domain. It prevents any user from changing the path in Word, and the path will not reset because the policy reapplies it on every refresh.

1. Open the Group Policy Management Console
   On a domain controller or machine with RSAT installed, run gpmc.msc.
2. Create or edit a GPO
   Right-click the OU containing your users and select Create a GPO in this domain, and Link it here. Give the GPO a name such as Word Workgroup Templates.
3. Navigate to the Word templates policy setting
   In the GPO editor, go to User Configuration > Policies > Administrative Templates > Microsoft Word 2016 > Miscellaneous. Double-click Workgroup templates path.
4. Enable and set the path
   Select Enabled. In the Options pane, enter the full UNC path to the workgroup templates folder, for example \\server\templates. Click OK.
5. Force a policy refresh on client machines
   On a test client, open Command Prompt as administrator and run gpupdate /force. Restart Word and verify that File Locations shows the policy-set path and that the user cannot modify it.

Method 3: Lock the Registry Key With a Logon Script

If you cannot use Group Policy, you can deploy a logon script that writes the workgroup templates path and prevents the user from changing it by restricting registry write access.

1. Create a batch or PowerShell script
   Create a file named SetWorkgroupTemplates.ps1 with the following content: Set-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Word\Options" -Name "PROGRAMDIR" -Value "\\server\templates" -Type String
2. Deploy the script via Group Policy or startup script
   In Group Policy, add the script under User Configuration > Windows Settings > Scripts > Logon. Point to the script file on a network share.
3. Restrict write access to the registry key
   Open Regedit on a test machine. Right-click the Options key under HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word and select Permissions. Remove the Write permission for the Users group. This prevents Word from overwriting the value set by the script.

If the Workgroup Templates Path Still Resets

Word Ignores the Workgroup Templates Path and Uses Local Templates

When Word cannot find the workgroup templates folder, it silently falls back to the user’s local Templates folder. Check that the folder exists and that the user has read access. If the folder is on a network share, verify that the user is authenticated to the share. If the share requires different credentials, Word may not load the templates at all.

Workgroup Templates Do Not Appear in the New Document Dialog

This symptom occurs when the path is correct but the templates are not compatible with the installed version of Word. For example, a template saved in Word 2019 format may not appear in Word 2016. Open the template in the target version of Word and resave it. Also confirm that the template files have the .dotx or .dotm extension and are not set to hidden.

Group Policy Does Not Apply to a Specific User

If the policy is configured but one user still sees the default path, run gpresult /r in Command Prompt to verify that the policy is applied. If the policy is filtered by security group, ensure the user is a member of the correct group. If the user is a local administrator on the machine, User Policy may be blocked by loopback processing settings.

Group Policy vs Registry Script vs Manual Setting

Item	Group Policy	Logon Script With Registry Lock	Manual Setting in Word
Persistence across logons	Always reapplies	Reapplies at each logon	Resets if policy or script runs
User can change path	No	No if registry write permission is removed	Yes
Requires administrative tools	Yes, GPMC and domain	Yes, script deployment	No
Works in workgroup environment	No	Yes, with local script	Yes
Supports multiple folder paths	Single path only	Single path only	Single path only

Use Group Policy if you manage many users in a domain. Use a logon script with registry permission locking if you need a lightweight solution without Group Policy. Use the manual setting only for standalone machines where no policy or script overwrites the registry key.

You can now diagnose why the workgroup templates folder path resets and apply the appropriate fix for your environment. If you manage multiple users, deploy Group Policy to lock the path and prevent accidental resets. As an advanced step, audit the registry key PROGRAMDIR across machines using a PowerShell script to confirm that the correct path is in place after each logon.