How to Fix “New → Folder” Option Missing in Windows 10 & 11 (All Methods)

Joynul Abadin Rasel

October 08, 2025 October 08, 2025

Introduction

Have you ever right-clicked or tried using the “New Folder” button (or shortcut Ctrl+Shift+N) in Windows, only to find it missing? This problem often arises from corrupted registry settings, shell handlers being disabled, missing system files, or OS updates that messed things up. In this post, you’ll get every known method to restore the “New Folder” option in Windows 10 & 11—including registry fixes, re-registering core system files, running health checks, etc.

Description

When “New → Folder” disappears, you lose a very basic but important way to organize files. Sometimes the “New” submenu is there but “Folder” is missing; other times the whole “New” item or keyboard shortcut fails. Causes include:

Broken or wrong registry values
Missing or corrupted shell extension handlers
Corrupted system DLLs or shell files
OS updates or third-party software interfering
File associations messed up
Group Policy or security settings blocking the context menu

Below are all the methods I collected (from Microsoft articles, tech forums, etc.) to fix it step by step.

All Possible Methods to Restore New → Folder

Method 1: Keyboard Shortcut / Alternative Workarounds

Use Ctrl + Shift + N to create a folder when in a folder or Desktop. Even when context menu is broken, this may still work.
Use Command Prompt:
```
mkdir "New Folder Name"
```
Navigate to the path you want in CMD or PowerShell and run that.

Method 2: Run System File Checker (SFC) and DISM to Restore System Health

Open Command Prompt or Windows Terminal as Administrator.
Run:
```
sfc /scannow
```
This checks for corrupted system files and attempts to repair them.
If SFC reports issues it can’t fix: run DISM:
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Then run sfc /scannow again.

Method 3: Re-Register Shell / DLL Files (Shell32 etc.)

Some solutions mention re-registering key shell files which might restore missing menu items. For example:

Use regsvr32 on shell32.dll and possibly other shell-related DLLs. This re-registers them with Windows so OS knows how to handle context menu commands.
In some forums, people used:
```
regsvr32 /i shell32.dll
```
to fix missing New folder context menu.

(Note: be careful — using regsvr32 should be done with admin rights, and only for valid system DLLs.)

Method 4: Registry Fixes / Restore Default Registry Values

Here are multiple registry-based fixes:

4A: Ensure the “New” context menu handler is present and correct

Open Registry Editor (regedit) as administrator.

Navigate to:


HKEY_CLASSES_ROOT\Directory\Background\shellex\ContextMenuHandlers\New

On the right, the (Default) value should be:
```
{D969A300-E7FF-11d0-A93B-00A0C90F2719}
```
If the New key is missing, you create it under ContextMenuHandlers and then set the Default value to that GUID.

4B: Check or fix the “Folder” registry key

Go to:
```
HKEY_CLASSES_ROOT\Folder
```
On the right pane, double-click the (Default) entry.
Make sure its value data is exactly:
```
Folder
```
If it’s something else or blank, change it to “Folder”.

4C: Restore or fix the ShellNew values under Folder

Under HKEY_CLASSES_ROOT\Folder\ShellNew, there should not be incorrect values like Handler or NullFile pointing to a shortcut instead of a folder. In some broken systems, these values were added (or wrong values present), causing “New → Folder” to produce a shortcut instead of a real folder.
If they exist and are wrong, you delete them. Then ensure proper values like IsFolder, NoExtension, etc., exist if needed.

Direct Download This File and Apple Registry File!

Method 5: Use “assoc” Command to Fix File Type Associations

Open Command Prompt as admin.
Run:
```
assoc folder=Folder
```
This command ensures that the .Folder file type is correctly associated. Sometimes broken association can cause the folder creation functionality/registry links to break.

Method 6: Disable / Remove Third-Party Shell Extensions or Software Conflicts

Use tools like ShellExView or ShellMenuView to see all shell/context menu handlers. Disable any non-Microsoft ones, especially ones that could interfere with the “New” menu.
Sometimes software (e.g. apps that customize context menus) override or remove the “New” command, or hijack keyboard shortcuts like Ctrl+Shift+N.

Method 7: Restore Default File Explorer / Folder Options

Open File Explorer Options (View → Options) → Restore Defaults.
Reset folder search options. Sometimes custom folder templates or template settings interfere.

Method 8: Group Policy / Security Setting Checks

If you are on Windows Pro/Enterprise, open gpedit.msc.
Navigate to User Configuration → Administrative Templates → Windows Components → File Explorer.
Check if any policy is enabled like “Remove Windows Explorer’s default context menu” or “Prevent access to context menus”. If so, set to Not Configured or disabled.

Method 9: System Restore

If this issue began recently (after installing software or updates), use System Restore to roll back to a point where “New → Folder” was working.

Method 10: Safe Mode / New User Profile

Boot into Safe Mode → check if “New → Folder” works there. If yes, some third-party program or driver is interfering.
Create a new user account, log in, and see if issue persists. If new account works fine, then your old user profile is corrupted or has bad configuration.

Method 11: Repair / In-place Upgrade or Reset Windows

Doing a Windows repair install (in-place upgrade) keeps files/apps but restores Windows system files. This reinstates missing shell components.
As a last resort, a clean reinstall or reset PC (keep files option) may fix deeply broken registry or system component damage.

Watch Tutorial

Conclusion

If you’re missing “New → Folder”, one of the registry fixes usually solves it—especially restoring the ContextMenuHandlers\New key and the default value, checking the HKEY_CLASSES_ROOT\Folder default, or correcting the ShellNew sub-key. If that fails, running SFC/DISM to repair system files, re-registering shell DLLs, or even doing a repair install might be needed. Always back up your registry and create a restore point before making changes.