To configure Windows Explorer to open only one instance at a time, you must modify the Windows Registry by adding a specific DWORD value. This setting prevents multiple window instances from launching when accessing files or folders, ensuring that all operations occur within a single Explorer process.
Why Multiple Instances Occur
By default, Windows is designed to allow multiple instances of File Explorer to run simultaneously. This behavior is useful for users who frequently need to drag and drop files between different directories without closing existing windows. However, this feature can lead to resource consumption issues, confusion in taskbar management, and complications during file transfer operations. Some users prefer a single-instance model to maintain a cleaner desktop environment and reduce memory overhead associated with running duplicate processes.
Prerequisites and Safety Warnings
Before proceeding with any registry modifications, it is crucial to back up your system. The Windows Registry contains critical configuration data, and incorrect changes can lead to system instability or failure to boot. Create a system restore point or export the relevant registry hive to a safe location. Additionally, ensure you have administrative privileges on your machine, as modifying these settings requires elevated permissions. If you encounter difficulties with the registry editor, consider reviewing related troubleshooting guides such as
Explorer Keeping Restart: Taskbar.View.dll Issue for broader context on Explorer stability.
Step-by-Step Registry Modification
The core solution involves editing the registry key responsible for shell folder behaviors. Follow these steps carefully:
- Open Registry Editor: Press
Win + R to open the Run dialog, type regedit, and press Enter. Confirm any User Account Control prompts.
- Navigate to the Key: In the address bar, paste or navigate to the following path:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced.
- Create New Value: Right-click on the
Advanced key in the left pane. Select New > DWORD (32-bit) Value. Name the new value LaunchFolderWindowInSeparateProcess.
- Set Value Data: Double-click the newly created
LaunchFolderWindowInSeparateProcess entry. Set the value data to 0. Ensure the base is set to Hexadecimal or Decimal; both work as long as the value is zero.
- Apply Changes: Close the Registry Editor. You must restart your computer or log off and log back on for the changes to take effect.
Setting this value to zero tells Windows to reuse an existing Explorer window rather than spawning a new one. When you attempt to open a new folder while another is already open, the system will switch focus to the existing window instead of creating a duplicate.
Alternative Method: Group Policy
For enterprise environments or users who prefer not to edit the registry directly, Group Policy can enforce this setting. Open the Local Group Policy Editor by typing
gpedit.msc in the Run dialog. Navigate to
User Configuration >
Administrative Templates >
Windows Components >
File Explorer. Look for the policy named
Show Folders in New Window. Setting this to
Disabled achieves a similar result by preventing new windows from opening for folder actions. Note that this policy may affect other shell behaviors depending on your Windows version.
Verifying the Configuration
After restarting, test the configuration by having one Explorer window open. Try to open another folder via the Start Menu, a shortcut, or by double-clicking a directory in another application. Instead of a new window appearing, the original window should update its contents to display the new folder. If a new window still opens, verify that the registry value is correctly set to
0 and that no third-party shell extensions are interfering with the behavior. For more information on resolving unexpected Explorer behaviors, refer to
Windows Explorer Stuck 'Items remaining: 0' during file copying.
Frequently Asked Questions
Does this setting affect Command Prompt or PowerShell?
No, this registry change specifically targets the Graphical User Interface of File Explorer. It does not influence how command-line tools or terminal emulators launch windows. Each console application retains its own independent window management behavior regardless of the Explorer setting.
Can I revert this change if I dislike the single-instance behavior?
Yes, you can easily reverse the modification. Simply return to the same registry key, delete the
LaunchFolderWindowInSeparateProcess DWORD value, or change its data back to
1. After deleting or changing the value, a restart or sign-out/sign-in cycle will restore the default multi-instance behavior.
Will this fix issues with Explorer crashing repeatedly?
While forcing a single instance can sometimes reduce resource contention, it is not a guaranteed fix for crashes. If Explorer is crashing due to corrupted shell extensions or system file errors, this setting alone will not resolve the underlying cause. You may need to investigate event logs or use
Where are my system files located in Windows? to check for integrity issues.
Is there a way to temporarily override this for a specific action?
Standard Windows shortcuts do not provide a direct modifier key to force a new window when this setting is active. However, you can hold Shift while right-clicking certain elements to see additional options, though this rarely bypasses the single-instance rule for standard folder navigation. Third-party utilities might offer workarounds, but they are generally unnecessary for most users.
Does this apply to Windows 11 as well as Windows 10?
Yes, the registry key LaunchFolderWindowInSeparateProcess is supported in both Windows 10 and Windows 11. The behavior remains consistent across these versions, allowing users to unify their file management experience regardless of the operating system interface style.