File Explorer’s Folder Options is one of those small but crucial control panels that quietly governs how Windows shows files, handles hidden items, and performs searches — and when that panel disappears behind policy or malware it can block simple fixes and customization. This feature guide explains, step by step, how to
restore access to File Explorer Options (Folder Options) when it’s been disabled, how to
disable it intentionally for managed environments, and what each method actually changes under the hood so administrators and power users can make safe, auditable decisions.
Background / Overview
File Explorer Options (often still called “Folder Options”) exposes settings that control folder views, icon and thumbnail behavior, Quick access / Home layout, search options, and numerous view-level preferences. Windows exposes a supported Group Policy that removes user access to that panel and a matching registry value that system integrators and malware have historically used to hide it. The Group Policy entry is named
Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon; it maps to the registry value
NoFolderOptions under the Policies\Explorer key. Microsoft documents this ADMX/ADML policy mapping and the associated registry name (NoFolderOptions). Why this matters:
- Restoring Folder Options lets users change view settings, show hidden files, control thumbnail behavior, and toggle privacy-related Quick access recommendations.
- Disabling Folder Options is a lightweight control for admins who want to prevent users from changing explorer layout or privacy settings.
- Because both Group Policy and registry methods exist, the fix or the lock can be applied in both managed (Pro/Enterprise) and unmanaged (Home) environments.
The remainder of this feature explains both sides: how to re-enable access, how to lock it down, and how to verify and troubleshoot the changes.
How Folder Options gets hidden: policy vs registry
Policy (preferred for managed environments)
Windows exposes a Group Policy under:
- User Configuration → Administrative Templates → Windows Components → File Explorer → Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon.
When set to
Enabled, attempts to open Folder Options from File Explorer will be blocked and an error or “restricted” message will appear. This policy is backed by an ADMX file (WindowsExplorer.admx) and maps to a registry value as documented by Microsoft. For enterprise or domain-joined machines, using Group Policy (GPO) is the clean, auditable, and reversible path.
Registry (workaround for Home editions and single‑PC fixes)
The same behavior can be enforced by creating or editing the following registry value:
- Key(s):
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
- (Optionally for machine-wide enforcement) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer
- Value:
- Name: NoFolderOptions
- Type: DWORD (32-bit)
- Data: 1 (to disable), 0 or delete the value to enable
Using the registry is necessary on Windows Home where gpedit.msc is not available. Several reputable guides and community resources show this exact key/value approach. Always back up the registry before making changes.
How to enable access to File Explorer Options (step-by-step)
Use the Group Policy Editor first if it is available on your edition of Windows. If not, use the Registry Editor instructions below.
A — Enable via Group Policy (Windows Pro / Enterprise / Education)
- Press Windows + R, type gpedit.msc and press Enter to open the Local Group Policy Editor.
- Navigate to: User Configuration → Administrative Templates → Windows Components → File Explorer.
- In the right pane, find Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon and double-click it.
- Set the policy to Disabled or Not Configured. Click Apply, then OK.
- Sign out and sign back in, or reboot the PC to make sure the policy is reapplied cleanly.
Notes:
- Use the Computer Configuration branch if you require machine-wide enforcement (applies before user sign-in).
- Group Policy changes may take a short time to propagate on domain controllers; on a standalone machine a restart ensures the change is applied.
B — Enable via Registry Editor (Windows Home and all editions)
- Press Windows + R, type regedit and press Enter to open Registry Editor. Grant UAC permission if requested.
- Browse to:
- HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
If the Explorer key does not exist, create it (right-click Policies → New → Key → name it Explorer).
- In the right pane, look for a DWORD called NoFolderOptions.
- If it exists and is set to 1, double-click and change the value to 0.
- If it exists and you want to restore full defaults, you can delete the NoFolderOptions entry.
- Close Registry Editor and restart Windows (or sign out and back in).
- Confirm access: open File Explorer, click the three-dot menu → Options (or View → Options) and the Folder Options dialog should open. If it still shows a restriction message, double-check for the same value under HKLM (machine key) as that overrides HKCU in some scenarios.
How to disable access to File Explorer Options (intentionally)
You may want to restrict Folder Options in shared, kiosk, classroom, or locked-down business scenarios.
A — Disable via Group Policy (recommended)
- Open gpedit.msc.
- Go to: User Configuration → Administrative Templates → Windows Components → File Explorer.
- Edit Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon and set it to Enabled.
- Apply, OK, and then reboot or force a policy refresh (gpupdate /force) for immediate effect.
This blocks users from opening Folder Options from the ribbon and from the more typical UI entry points. Group Policy ensures an auditable change and can be enforced via domain GPOs in Active Directory or via MDM templates for Intune-managed machines.
B — Disable via the Registry (for single machines or automation)
- Run regedit as Administrator.
- Navigate to:
- HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer
- For machine-wide enforcement, also create the same DWORD under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer.
- Create a DWORD (32-bit) value named NoFolderOptions and set it to 1.
- Restart the PC. The Folder Options menu will be blocked and opening it will display a restriction message.
Verifying the change and troubleshooting
- Verify the policy mapping: Microsoft documents the ADMX-backed policy and the registry key mapping (NoFolderOptions) in its ADMX/Policy CSP documentation. If the Group Policy is set but the user still sees Folder Options, check for conflicting policies from domain GPOs or MDM.
- If Folder Options is still blocked after removing the registry key:
- Check both HKCU and HKLM locations; a machine-level key can supersede a user-level key.
- Run gpupdate /force to refresh policy and reboot.
- Scan for malware — certain infections set these policies as persistence or to frustrate users. Community troubleshooting guides warn that malware sometimes toggles NoFolderOptions and recommend full AV + offline scans if the setting recurs.
- If changes don’t appear immediately:
- Restart Explorer (Task Manager → restart Windows Explorer) and check again.
- Fully reboot to ensure any policy caching is cleared.
Auditability and enterprise controls
- Use Group Policy for enterprise-wide settings: GPO offers central control, event-logging, and reversibility via AD's Group Policy Management. For Intune/MDM-managed fleets, the ADMX-backed policy can be delivered as a policy profile via Policy CSP or ADMX ingestion; the ADMX mapping references the same registry key. For formal deployments, prefer GPO/MDM rather than ad-hoc registry scripts.
- Logging and monitoring: track changes to the Policies\Explorer keys with endpoint logging or SIEM rules. Because both HKCU and HKLM are valid locations, include both paths in monitoring. If your estate uses endpoint protection that can detect registry persistence patterns, consider adding NoFolderOptions to the watchlist.
Safety and best practices
- Backup before edits: always export the registry key or create a system restore point before editing the registry. This reduces recovery time if an incorrect edit causes system instability.
- Use least-privilege scripts: when automating via PowerShell or deployment tools, run with the minimal required privileges and record changes. Prefer Group Policy Objects in Windows Server/AD or Intune for organization-wide application.
- Reversibility: both Group Policy and registry edits are reversible. If a machine repeatedly re-applies NoFolderOptions after deletion, investigate scheduled tasks, provisioning scripts, or malware.
- Malware caution: if Folder Options is missing on a personal machine and you did not configure a policy, treat it as suspicious. Several community guides emphasize running a full anti-malware sweep and restoring the key as part of remediation.
Quick reference: commands and actions
- To open Group Policy Editor:
- Windows + R → gpedit.msc → Enter.
- To refresh policies from command line:
- Open an elevated Command Prompt or PowerShell.
- Run: gpupdate /force
- Reboot if necessary.
- Registry paths:
- HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoFolderOptions (DWORD 1 = disabled, 0 or delete = enabled)
- HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoFolderOptions (machine-level override)
- To safely remove the value using PowerShell (current user):
- Run PowerShell as the affected user (or use -Scope CurrentUser):
1. Remove-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer" -Name NoFolderOptions -ErrorAction SilentlyContinue
- Restart Explorer or reboot.
Common questions (concise answers)
- Will this work on Windows 10 and Windows 11?
- Yes. The policy and the registry value exist across modern Windows releases and are documented in ADMX mappings. Both Windows 10 and Windows 11 share the same policy path and registry name.
- Do I need to restart after making the change?
- Yes. A restart or at least an Explorer restart and a policy refresh (gpupdate /force) are recommended for the setting to take full effect. Some registry-only changes may appear after signing out and back in, but a reboot is the cleanest approach.
- Can I apply this restriction to all users on a machine?
- Yes. Set the Group Policy under the Computer Configuration branch or create the NoFolderOptions value in HKLM to affect all users. For domain fleets use a Computer Configuration GPO for machine-level enforcement.
- Could malware hide Folder Options?
- Yes. Several community troubleshooting resources show malware setting NoFolderOptions or other Policies values to frustrate detection and editing; if the setting reappears, run a thorough malware scan.
Practical examples
Example: restore Folder Options on a Home PC
- Run regedit, navigate to HKCU...\Policies\Explorer.
- If NoFolderOptions exists and equals 1, delete it or set it to 0.
- Reboot and confirm Options → Folder Options opens again.
Example: lock Folder Options in a school lab via scripted deployment
- Create an ADMX-backed GPO or use a login script that writes NoFolderOptions = 1 to HKLM...\Policies\Explorer.
- Use Group Policy Management to target the lab OU and enforce the setting.
- Test on a small set of machines, then widen the deployment after confirming behavior.
Critical analysis: strengths, risks, and operational notes
Strengths
- The policy and registry approach are simple, predictable, and documented; they make it straightforward for administrators to apply a single, reversible control across an environment. The ADMX mapping backed by Microsoft ensures the policy will be supported and manageable by enterprise tooling.
- Registry fallback ensures home users and small shops without Group Policy can still remediate or enforce this behavior.
Risks and limitations
- A registry-only approach is more error-prone and less auditable than Group Policy. Admins should prefer GPOs or MDM where possible and log registry changes if using scripts. Community sources repeatedly warn that malicious actors also use the same keys for persistence, so a recurring NoFolderOptions value should be treated as suspicious and investigated.
- Machine-level overrides (HKLM) can silently block user-level fixes (HKCU). Troubleshooting requires checking both HKCU and HKLM, which can confuse novice users.
- While disabling Folder Options blocks casual configuration changes, it is a coarse control. Advanced users with local admin rights may still change behavior via other registry edits, scripts, or third-party tools. In managed environments, combine this policy with standard least-privilege, AppLocker/SmartScreen, and endpoint controls to get stronger enforcement.
Conclusion
Controlling access to File Explorer’s Folder Options is a straightforward, supported administrative action with clearly mapped Group Policy and registry keys. Use Group Policy or MDM for enterprise-grade control and auditing; use the registry for single-machine interventions or remediation on Windows Home. Always back up the registry before editing, verify both HKCU and HKLM keys when troubleshooting, and treat a returning NoFolderOptions value as a signal to scan for malicious persistence. Microsoft documents the ADMX mapping and registry name (NoFolderOptions), and multiple community guides corroborate the behavior and practical steps for both enabling and disabling access. Restoring or locking Folder Options is one of those small administrative wins that makes Windows behave the way users and organizations expect — predictable, secure, and configurable.
Source: Windows Report
How to Enable or Disable Access to File Explorer Options