NS_E_OPEN_CONTAINING_FOLDER_FAILED Fix (0XC00D1363)

Quick answer: Run sfc /scannow from an admin command prompt, then restart File Explorer. If that fails, delete HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\BrowseNewProcess and reboot.

What's actually happening here?

That error — NS_E_OPEN_CONTAINING_FOLDER_FAILED (0XC00D1363) — shows up in Windows 10 and 11 when you right-click a downloaded file in your browser (Chrome, Edge, Firefox) and pick “Show in folder” or “Open containing folder.” Instead of popping open a File Explorer window, you get that useless dialog: “The folder could not be opened.”

The reason this happens is almost never that the folder genuinely doesn’t exist. Windows is failing to find the folder’s shell interface. Under the hood, the shell extension that handles “open folder” is tied to a COM object — specifically the ExplorerBrowser or a third-party context menu handler that’s gone sideways. A corrupt registry key, a broken shell extension from an old app (like Dropbox or Google Drive), or a buggy Windows update can break the chain. The error code 0XC00D1363 maps to NS_E_OPEN_CONTAINING_FOLDER_FAILED, which means the component that’s supposed to resolve the folder path to a shell namespace failed silently.

I’ve seen this most often on Windows 11 22H2 systems after a feature update, and on Windows 10 machines with aggressive Registry Cleaner tools that delete too much.

Fix 1: Reset File Explorer via Task Manager

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Find Windows Explorer in the Processes tab.
3. Right-click it and select End task. Your taskbar and desktop will disappear — that’s normal.
4. In Task Manager, click File > Run new task, type explorer.exe, and hit Enter.
5. Test the “open containing folder” again.

This clears any temporary corruption in Explorer’s memory. It works maybe 30% of the time. If it doesn’t, move on.

Fix 2: Delete the BrowseNewProcess registry key

The real fix for most people is removing a specific registry value that forces Explorer to open folders in a separate process. Windows added this as an experimental feature in some builds, and it breaks the folder-open chain when a COM call fails.

1. Press Win + R, type regedit, and press Enter.
2. Navigate to:
   HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
3. Look for a key named BrowseNewProcess. It’s a DWORD.
4. If it exists, delete it (right-click > Delete). Do not just set it to 0 — delete it entirely.
5. Close Regedit and reboot.

The reason deleting it works: when the key is present (even if set to 0), Explorer uses a separate, isolated Explorer.exe instance for folder windows. That isolated instance sometimes fails to initialize the shell namespace correctly for the target folder. Removing the key forces Explorer to use the default behavior — opening folders in the same process — which resolves the COM call routing.

Fix 3: Run SFC and DISM

1. Open Command Prompt as Administrator (Win + X > Terminal (Admin)).
2. Run sfc /scannow. Let it finish — can take 15 minutes.
3. After it completes, run DISM /Online /Cleanup-Image /RestoreHealth.
4. Reboot.

This fixes system file corruption. It’s the nuclear option for this error, but it’s worth doing if the registry fix didn’t work.

If nothing else works: Check for shell extension conflicts

Download ShellExView (NirSoft, free). Disable all non-Microsoft shell extensions. Restart Explorer. If the error disappears, re-enable extensions one by one until you find the culprit. I’ve seen Dropbox and 7-Zip context menu handlers cause this exact error. Keep them disabled if the folder-open feature matters more to you than the convenience of those extensions.

Prevention tip

Don’t use Registry Cleaner software. They routinely delete BrowseNewProcess or related Explorer settings thinking they’re “orphaned” — they’re not. Also, when you install a major Windows update, take 30 seconds after the first reboot to restart Explorer manually. That flushes out any stale shell extension state before it causes problems.