Right-click menus are the kitchen drawers of Windows: incredibly useful, slightly chaotic, and somehow always hiding the exact tool you need. If you open the same apps, scripts, folders, or system utilities every day, adding them to the desktop and Windows context menu can save clicks, reduce Start menu hunting, and make your PC feel like it was actually built for the way you work.
In this guide, we will walk through how to create cascade menus and add apps to the desktop and Windows context menu using Registry-based methods. We will focus on practical, real-world examples for Windows 10 and Windows 11, including how to add a single app shortcut, how to group several apps inside a cascading submenu, and how to keep your right-click menu clean instead of turning it into a digital junk drawer with icons.
Before we begin, one important reality check: Windows 11 has two context-menu experiences. The compact modern menu appears first, while the classic menu appears when you select Show more options or use the classic shortcut. Traditional Registry entries usually appear in the classic context menu. That does not make them useless; it simply means Windows 11 likes to make you take the scenic route.
What Is the Windows Context Menu?
The Windows context menu is the menu that appears when you right-click a file, folder, drive, desktop background, or blank area inside File Explorer. It is called a “context” menu because Windows changes the options depending on what you clicked. Right-click a photo and you may see image tools. Right-click a folder and you may see sharing, compression, terminal, copy, or security options.
For productivity, the context menu is valuable because it keeps common actions close to your cursor. Instead of opening Start, searching for an app, waiting for results, and launching it, you can right-click the desktop and choose your custom shortcut. For developers, writers, designers, IT administrators, and power users, this can be a surprisingly satisfying upgrade.
What Is a Cascading Menu?
A cascading menu is a submenu that opens from a main menu item. For example, you might add one top-level item called Favorite Apps. Hover over it, and a second menu opens with options such as Notepad, Terminal, Paint, Visual Studio Code, Calculator, and File Explorer. It is tidy, expandable, and much nicer than dumping eight separate shortcuts into the main right-click menu like confetti at a software parade.
Windows supports static cascading menus through Registry entries. The key ingredients are usually values such as MUIVerb, Icon, Position, SubCommands, and command subkeys. In plain English, those values tell Windows what label to show, which icon to use, where to place the item, and what command to run when the user clicks it.
Before You Edit the Registry: Safety First
The Windows Registry is powerful. It is also the place where one tiny typo can make you question every life decision that led you to editing system settings at midnight. So, before changing anything, create a backup.
Open Registry Editor by pressing Windows + R, typing regedit, and pressing Enter. Navigate to the key you plan to edit, then choose File > Export. Save the backup somewhere easy to find. If something goes wrong, you can import that file later to restore the previous settings.
For even better protection, create a system restore point before experimenting. Registry tweaks for context menus are usually simple and reversible, but a backup is still cheaper than panic.
Where Desktop Context Menu Shortcuts Live
The most common Registry location for shortcuts that appear when you right-click the desktop background is:
This location applies to the current user only, which is usually the best choice. It avoids administrator permission problems and keeps your changes from affecting other accounts on the same computer.
You may also see guides using:
That path works, but HKEY_CLASSES_ROOT is a merged view of system-wide and per-user class settings. For personal customization, HKEY_CURRENT_USER\Software\Classes is cleaner and safer.
How to Add a Single App to the Desktop Context Menu
Let’s begin with the easy win: adding one app shortcut to the desktop right-click menu. In this example, we will add Notepad.
Manual Steps
- Press Windows + R, type
regedit, and press Enter. - Go to
HKEY_CURRENT_USER\Software\Classes\Directory\Background\shell. - Right-click
shell, choose New > Key, and name itOpenNotepad. - Select the new key and set its default value to
Open Notepad. - Create a new string value named
Iconand set it tonotepad.exe. - Create another key under
OpenNotepadnamedcommand. - Select
commandand set its default value tonotepad.exe. - Restart File Explorer or right-click the desktop to test it.
Here is the same tweak as a .reg file:
Copy the code into Notepad, save it as Add-Notepad-Context-Menu.reg, then double-click it to merge. If Windows asks whether you trust yourself, say yes only if you actually copied the code correctly.
How to Add an App With a Full File Path
Some applications need a full path. For example, if you want to add Visual Studio Code, you might use a command like this:
Notice the escaped quotation marks. Paths with spaces must be wrapped in quotes. Without them, Windows may try to open C:\Users\YourName\AppData\Local\Programs\Microsoft and then stare blankly at the rest of the path like a confused intern.
For Microsoft Store apps or packaged apps, shortcuts may not always behave like traditional .exe files. In those cases, pinning, URI commands, or app-specific launch methods may be required.
How to Create a Cascade Menu for Favorite Apps
Now for the fun part: grouping multiple apps under one clean menu. The following example creates a cascading desktop menu called Favorite Apps with Notepad, Calculator, Paint, and Windows Terminal.
Save this as Add-Favorite-Apps-Cascade.reg, merge it, and then right-click the desktop. On Windows 10, you should see the menu directly. On Windows 11, you may need to select Show more options to see the classic context menu where traditional Registry entries appear.
Understanding the Registry Values
MUIVerb
MUIVerb controls the visible label. If you set MUIVerb to Favorite Apps, that is what the user sees in the menu.
Icon
Icon controls the menu icon. You can use an executable file, a DLL resource, or a full path to an icon file. Icons are optional, but they make the menu easier to scan.
Position
Position can be set to Top or Bottom. This influences where the item appears in the classic context menu. It does not magically force a traditional Registry item into the first-level modern Windows 11 menu.
SubCommands
SubCommands tells Windows the item should behave like a cascading menu. In many desktop-menu examples, setting it to an empty string allows child items under the nested shell key to appear as submenu entries.
How to Add Context Menu Items for All Files
Desktop shortcuts are useful, but sometimes you want an app to appear when you right-click a file. For example, you may want to open any file in Notepad. The common per-user path is:
Here is a simple example:
The %1 placeholder represents the file you clicked. This tells Windows to launch Notepad and pass the selected file to it. Use this carefully. Not every file type belongs in Notepad unless you enjoy reading binary data that looks like a robot sneezed into your monitor.
How to Add Context Menu Items for Folders
To add an option when right-clicking a folder, use:
For example, to open a selected folder in Windows Terminal:
This is especially useful for developers, sysadmins, and anyone who spends more time in command lines than in polite society.
How to Remove Your Custom Context Menu Items
Every good tweak should have an escape hatch. To remove the Notepad desktop shortcut created earlier, delete this key:
To remove the cascading Favorite Apps menu, delete:
You can also create a removal .reg file:
The minus sign before the key tells Registry Editor to delete that key and its subkeys.
Windows 11 Notes: Modern Menu vs Classic Menu
Windows 11 redesigned the right-click menu to be cleaner and more compact. The goal is reasonable: fewer confusing entries, common commands closer to the pointer, and a more modern visual style. The catch is that many traditional Registry menu items appear under the classic menu instead of the first menu you see.
To access those classic options in Windows 11, right-click and choose Show more options. On many systems, you can also use Shift + right-click to open the classic menu directly. If your custom menu appears there, it is working; Windows 11 is simply being Windows 11.
Developers who want first-level modern Windows 11 integration usually need newer shell extension methods rather than simple static Registry keys. For regular users, the classic menu remains the most practical place for custom app shortcuts, scripts, and cascade menus.
Best Practices for a Clean Context Menu
The context menu is most useful when it is selective. Add only the apps and commands you genuinely use. A menu with four smart shortcuts feels powerful. A menu with twenty-three shortcuts feels like a software garage sale.
Group related tools into cascade menus. For example, create Writing Tools for Notepad, Word, Obsidian, and your grammar checker. Create Developer Tools for Terminal, VS Code, Git Bash, and PowerShell. Create System Tools for Task Manager, Settings, Disk Management, and Control Panel shortcuts.
Use clear names. “Open in VS Code” is better than “CodeThingy.” Use icons when possible, but do not obsess over them. Function matters more than decoration, unless you are the kind of person who alphabetizes desktop wallpapers. No judgment. Well, maybe a tiny bit.
Common Problems and Fixes
The Menu Item Does Not Appear
Check that you used the correct Registry path. Desktop background items belong under Directory\Background\shell. Folder items belong under Directory\shell. File items belong under *\shell. Also restart File Explorer if the menu does not update immediately.
The App Does Not Open
Check the command path. If the path contains spaces, wrap it in quotes. If you are passing a selected file or folder, include "%1" in the command.
The Cascade Menu Is Empty
Confirm that the parent key has SubCommands set and that child items are placed under the nested shell key. Also verify that each child item has its own command subkey.
The Item Appears Only Under Show More Options
That is normal on Windows 11 for many traditional Registry-based customizations. The shortcut is not broken; it is simply living in the classic menu.
Experience Notes: What Actually Works Well in Daily Use
After using custom context menus for daily work, the biggest lesson is simple: fewer shortcuts are better. The first instinct is to add everything. Browser? Add it. Calculator? Add it. Screenshot tool? Add it. Email client? Add it. A shortcut to a folder containing shortcuts? Add that too. Suddenly, right-clicking the desktop becomes a dramatic event, like opening a restaurant menu with twelve pages and no pictures.
The best setup is usually built around workflows. For writing, a cascade menu with Notepad, Word, a markdown editor, and a research folder is genuinely useful. For development, Terminal, PowerShell, VS Code, Git Bash, and a local project folder can save time all day. For IT maintenance, shortcuts to Event Viewer, Device Manager, Services, Disk Management, and System Information make sense. The trick is to build menus around tasks, not around every app installed on the machine.
Another practical lesson: desktop background shortcuts are safer than aggressive all-file shortcuts. Adding “Open with Notepad” to every file type can be helpful, but it can also clutter the menu every time you right-click anything. A desktop cascade menu is less intrusive because it appears only when you right-click empty desktop space. It is like keeping tools in a toolbox instead of taping a screwdriver to every object in your house.
Icons are worth adding when they improve recognition. For example, Notepad, Terminal, Paint, and Calculator icons make a cascade menu feel polished. But if an icon path is hard to maintain, skip it. A broken icon does not usually break the command, but it makes the menu look unfinished. For portable apps, full paths can become a problem if you move the folder later. If you use portable tools, store them in a stable location such as C:\Tools and keep paths consistent.
Restarting File Explorer is often enough after a change. You do not always need to reboot. Open Task Manager, find Windows Explorer, and restart it. This refreshes the shell and usually shows your new menu entries. If a change still does not appear, sign out and back in before assuming the Registry goblins won.
Finally, keep removal files. Every AddSomething.reg should have a matching RemoveSomething.reg. That one habit makes experimentation much less stressful. Custom context menus are fun, useful, and surprisingly personal, but they should remain reversible. Your future self will thank you, probably while right-clicking triumphantly.
Conclusion
Creating cascade menus and adding apps to the desktop and Windows context menu is one of the most practical Windows customization tricks. It gives you fast access to the tools you use most, keeps your workflow close to your cursor, and helps turn the right-click menu into something genuinely useful instead of a random collection of app leftovers.
The safest approach is to use per-user Registry paths, back up before editing, start with one simple shortcut, and then organize related tools into cascading menus. On Windows 11, remember that many traditional Registry entries appear in the classic menu under Show more options. That is expected behavior, not failure.
Note: Always export the Registry keys you plan to edit before merging new .reg files. A tidy context menu is wonderful; a broken Registry is not the productivity upgrade anyone ordered.
