nilesoft.org

The File Explorer context menu is the list of actions that appears when you right-click a file, folder, the desktop, or the taskbar. You can customize it in three ways: add your own commands, modify existing entries, or remove items you don't use. The right approach depends on whether you want faster access to tools you use often, a cleaner menu, or both. Third-party utilities such as Nilesoft Shell handle all three by loading menu rules from a plain-text configuration file, which also makes it easy to back up and restore your setup.

What the context menu is and where its items come from

Every entry in the menu is a registered command. Windows itself contributes core items (Open, Copy, Rename, Properties, Send to, and so on). Installed software adds its own entries through shell extensions, which is why a fresh PC has a short menu and a heavily used one can grow to two or three columns.

Because those entries come from different sources, the menu has two separate problems to solve:

• Clutter — items from software you rarely use, or duplicates from overlapping tools.
• Gaps — actions you perform constantly but that require opening an app first.

Customization is really about managing both at once, and it helps to treat them as separate tasks with separate risks.

The three kinds of customization and when each fits

A practical order is to remove first (it gives immediate relief), then add the commands you actually miss, and only then modify existing entries. Modifying is the step most likely to produce a menu that looks right but behaves unexpectedly, so do it last and test after each change.

How customization tools work

Most context-menu managers follow the same model:

1. A portable or installed program registers itself with Explorer.
2. A configuration file describes which items appear, in what order, with what label and icon.
3. Explorer reads that configuration when you right-click, and renders the menu accordingly.

Nilesoft Shell follows this pattern closely. Its site describes it as a free, open-source context menu customizer for Windows File Explorer that lets you handpick items, create custom commands, and modify or remove items added by the system or third-party software. It is portable — nothing needs to be installed — and all settings load from a configuration file named shell.nss. The site lists support for files, folders, the desktop, and the taskbar, plus sub-menus, separators, expressions with built-in functions and variables, colors, glyphs, SVG and embedded icons, search and filter, nested menus, and multiple columns. Compatibility is stated as Windows 7/8/10/11 on x86, x64, and arm64.

The plain-text configuration is the important detail: it means your entire menu setup is one file you can copy, version, or restore if something goes wrong.

A safe way to clean up and rebuild the menu

The following applies to any configuration-file-based tool; the specific file name below is Shell's.

Before you start: create a restore point or copy your current configuration file somewhere safe. If you are using Shell for the first time, note that its settings live in shell.nss, so keeping a copy of the original gives you a known-good fallback.

1. Inventory the menu. Right-click a file and a folder separately and note which entries you never use. Some items only appear for certain file types, so check more than one.
2. Back up the configuration. Copy shell.nss to a backup folder, or export your settings if the tool provides that.
3. Remove the obvious clutter first. Suppress third-party entries you recognize as leftovers. Leave system entries (Open, Properties, Copy, Rename) alone unless you have a specific reason.
4. Add your own commands. Create the items you actually reach for — a script, a favorite folder, a web page — and group related ones into a sub-menu so the top level stays short.
5. Verify after each change. Right-click a file, a folder, the desktop, and the taskbar. A change that works on files may not apply to folders, and the taskbar is a separate surface.
6. Keep the backup until you are satisfied. If the menu misbehaves, restore the file and start again from a smaller change.

Common sticking points:

• A removed item comes back. Some software re-registers its menu entry on update or launch. Suppressing it in the configuration is more durable than deleting it once.
• The menu looks different in different places. File, folder, desktop, and taskbar menus are not identical; test each surface you care about.
• An entry disappears that you wanted. Restore from your backup and re-apply changes one at a time so you can identify the culprit.
• Changes don't show up. Confirm the configuration file is the one actually being loaded, and that the tool is running with the settings you edited.

Choosing between built-in settings and a dedicated tool

Windows itself offers limited control — you can manage some startup and default-app behavior, but not the full context menu. For real control you need a shell extension manager or a customizer.

Use a dedicated tool when you want to add commands, restyle the menu, or manage many entries across files, folders, desktop, and taskbar. Stay with minimal changes when you only need to hide one or two items and are uncomfortable editing configuration text. In that case, removing the offending software or using its own settings is often the lower-risk path.

If you do adopt a tool, prefer one that stores settings in a readable file you can back up, states its Windows compatibility clearly, and lets you undo changes without reinstalling. Shell meets those conditions on its own documentation — free, open source, portable, configuration-driven, and listed as compatible with Windows 7 through 11 — but the deciding factor should be whether its feature set matches the commands you actually want, not the length of its feature list.

Nilesoft Shell is a free, open-source, portable utility that customizes the Windows File Explorer right-click context menu. It lets you add new items (menu items, submenus, separators), modify or remove entries added by Windows or third-party software, and control appearance through a plain-text config file named shell.nss. It runs on Windows 7/8/10/11 (x86/x64/arm64) and requires no installation.

How Shell Works

Shell sits between File Explorer and the context menu. Instead of editing the registry or installing a traditional shell extension, you describe the desired menu in shell.nss. Shell reads that file and builds the menu accordingly.

Because it is portable, there is nothing to install: you place the utility on your PC and keep your settings in the config file. All settings load from shell.nss, so backing up or moving your configuration means copying one text file.

The configuration approach is plain text, which makes changes quick to write and easy to review. Shell also supports an expressions syntax with built-in functions and predefined variables, so menu items can adapt to context rather than being fixed entries.

What You Can Change in the Context Menu

Shell covers the main customization tasks in one tool:

Shell supports all file system objects: files, folders, the desktop, and the taskbar. You can also create custom commands that open favorite web pages, files, and folders, or launch any application directly from the menu.

A Concrete Example

Suppose you want a right-click entry that opens a frequently used folder, grouped under a submenu with a separator and a custom icon. In Shell, that means:

1. Input: a shell.nss file containing a menu item definition for the folder, a submenu to hold it, a separator, and an icon reference (for example an .ico or .png file, or an SVG glyph).
2. Action: Shell reads the config and integrates the item into the File Explorer context menu.
3. Expected result: right-clicking a supported object shows your submenu with the folder command, visually separated and carrying your icon.

The same pattern applies in reverse: to remove a cluttering third-party entry, you identify it and remove or modify it in the config instead of hunting through registry keys.

Practical Considerations

• Start from the config file. Since every setting lives in shell.nss, keep a copy before making large changes so you can revert.
• Use search and filter for busy menus. If the menu already has many entries, filtering helps you locate what to modify or remove.
• Keep resource use in mind. Shell is described as lightweight with minimal resource usage and high responsiveness, which matters because the context menu opens constantly.
• Check compatibility first. Confirm your Windows version and architecture (x86, x64, or arm64) are among the supported platforms.
• Expect a learning curve for expressions. Basic items and separators are straightforward; expressions with built-in functions and variables take more practice.

Shell is aimed at users who want direct control over the right-click menu without installing a heavyweight extension, and who are comfortable editing a text configuration file.

A shell extension is a small COM component that Windows Explorer loads to add functionality to the shell — most visibly extra right-click context menu entries, but also property page tabs, icon overlays, thumbnail handlers, and "Send To" additions. You manage them by identifying the handler behind the behavior, then disabling or removing it with a shell-extension manager or Explorer's own settings, while leaving system-critical handlers alone. This guide covers the types, how to trace a menu item back to its extension, and safe removal steps.

What a shell extension actually is

Windows Explorer is a shell host. Third-party software doesn't modify Explorer's code; instead it registers a COM object (a DLL, sometimes an EXE) under specific registry keys, and Explorer loads that object on demand. When you right-click a file, Explorer enumerates the registered context-menu handlers and asks each one whether it wants to contribute an item. That's why a single right-click can show entries from a dozen unrelated programs.

Two consequences follow from this design:

• Registration, not installation, is what makes an extension appear. Removing a program's folder without unregistering its COM object can leave a dead menu entry that does nothing or throws an error.
• Bitness matters. A 64-bit Explorer won't load a 32-bit handler, and vice versa. A menu item that appears in one app but not another is often a 32/64-bit mismatch rather than a bug.

Common types and where they show up

Nilesoft Shell is itself a context menu customizer in this space. Per its documentation, it lets you handpick which items appear in the File Explorer context menu, create custom commands, and modify or remove items added by the system or third-party software. It's described as a portable utility configured through a plain-text shell.nss file, supporting Windows 7/8/10/11 on x86, x64, and arm64. That makes it one option for managing menu clutter — but note it manages the menu layer, not arbitrary COM handlers like overlay or thumbnail extensions.

How to identify which extension owns a menu item

Work from the visible symptom back to the registration:

1. Read the menu entry carefully. Many items name their vendor ("Scan with Contoso"). If not, hover or expand submenus — the parent usually reveals the source.
2. Check the program's own settings first. Most apps that add menu items have a toggle in their preferences ("Show in context menu," "Integrate with Explorer"). This is the cleanest fix and avoids registry work entirely.
3. Use a shell-extension manager to list registered handlers with their DLL paths and CLSIDs. Tools like Microsoft's Autoruns (Shell Extensions tab) or NirSoft's ShellExView show the file, publisher, and whether the entry is enabled. Match the DLL path to the vendor folder.
4. Cross-check the registry if you need certainty. Context menu handlers live under HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers (all files) and ...\Directory\shellex\ContextMenuHandlers (folders), with the CLSID pointing to the DLL under HKEY_CLASSES_ROOT\CLSID. Overlay handlers are under ...\ShellIconOverlayIdentifiers.

Expected result: you should end up with a specific DLL path and CLSID, not just a guess at the program name.

Disabling or removing unwanted extensions safely

Preferred order of operations:

1. Turn it off in the app's settings. Reversible, no registry risk.
2. Disable (not delete) via a manager. ShellExView and Autoruns let you disable an entry and re-enable it if something breaks. Disabling is the right first test.
3. Uninstall the parent program if you don't need it at all. A well-behaved uninstaller unregisters its handlers.
4. Delete the registry key only as a last resort, and only after exporting a backup of the key. Deleting a handler that another component depends on can break Explorer features.

Common pitfalls:

• Don't disable handlers you can't identify. Entries from Microsoft (publisher field) are usually system-critical — overlay handlers for OneDrive, for example, control sync badges.
• Restart Explorer to see the effect. Changes to shell extensions often require restarting explorer.exe or signing out; a menu item may persist until then.
• Watch for reappearance. Some apps re-register their handlers on every launch, so a disabled entry can come back after an update.
• Test one change at a time. If Explorer misbehaves after a batch of disables, you won't know which one caused it.

Choosing between built-in tools and a customizer

If your goal is simply to remove or hide clutter, a shell-extension manager plus each app's own settings is the lower-risk path. If your goal is to reshape the menu — reorder items, add custom commands, build nested submenus, or apply consistent styling — a context menu customizer like Nilesoft Shell is the more direct tool, configured through its text file rather than by editing registrations by hand. The two approaches are complementary: use a manager to audit what's registered, and a customizer to control what the menu actually presents.

The right-click context menu is the list of actions Windows File Explorer shows when you right-click a file, folder, the desktop, or the taskbar. You can customize it by adding your own commands, submenus, and separators, and by modifying or removing items that Windows or third-party software added. Nilesoft Shell is one free, open-source, portable tool for doing this: it reads all settings from a plain-text config file named shell.nss, so nothing needs to be installed on the PC.

What the context menu is and where its items come from

Every entry in the menu is a command registered with Windows. Items typically come from three sources:

• Windows itself — built-in actions such as open, copy, rename, or properties.
• Third-party software — programs that register shell extensions, which is why installing utilities often lengthens the menu.
• Your own custom entries — commands you define yourself, which is what a customizer like Shell is for.

The menu applies to file system objects, and Shell's documentation states it supports files, folders, the desktop, and the taskbar.

What you can change

Shell's feature list describes four kinds of customization:

It also supports an expressions syntax with built-in functions and predefined variables, plus search and filter, which matters once a menu grows past a handful of entries.

How customization works in practice

1. Get the tool. Download Shell from the Nilesoft site. It is described as a portable utility, so there is no installer step — the settings live in shell.nss.
2. Back up your current configuration. Before editing, keep a copy of the existing shell.nss so you can restore a working menu if an edit misbehaves.
3. Edit the config in plain text. Add, modify, or remove entries in shell.nss. Because the file is plain text, you can keep it under version control or copy it between machines.
4. Verify the result. Right-click a file, a folder, the desktop, and the taskbar to confirm the new items appear where intended and removed items are gone. Test nested submenus specifically, since a misplaced separator or bracket can hide an entire branch.
5. Keep a known-good copy. Once the menu behaves as you want, save that shell.nss as your baseline before the next round of changes.

Common sticking points: an edit that breaks the file's structure can make items disappear rather than error visibly, and third-party software may re-add its own entries after an update, so re-check the menu after installing or updating programs.

Who it suits, and compatibility

Shell is a reasonable fit if you want a lightweight, portable manager with no install footprint and you are comfortable editing a text config. Its stated compatibility is Microsoft Windows 7, 8, 10, and 11 on x86, x64, and arm64. The site describes it as free and open source with minimal resource usage; it does not publish pricing details beyond that, so treat availability and any future terms as something to confirm on the download page.

If you only need to hide one or two entries and never add your own, a simpler registry- or settings-based approach may be enough. If you want custom commands, nested menus, and appearance control in one place, Shell's feature set covers those directly.