Introduction

MSysGit and older Git-for-Windows installers often add Explorer context-menu entries such as "Git Bash Here" and "Git GUI Here". Removing them usually means either changing the installation options or deleting the corresponding shell-extension registry entries. The right method depends on whether you want a supported installer-driven change or a manual Windows cleanup.

The Cleaner Option Is Usually Reconfigure or Reinstall

If the Git distribution still has an installer or maintenance mode available, the safest path is to re-run it and turn off Explorer integration.

That keeps the change aligned with how the software was installed and avoids manual registry edits when they are unnecessary.

Manual Removal Means Editing Registry Entries

The context-menu items typically come from shell keys under HKEY_CLASSES_ROOT or under the equivalent merged shell paths for directories and directory backgrounds.

Common places to check include:

HKEY_CLASSES_ROOT\Directory\shell
HKEY_CLASSES_ROOT\Directory\Background\shell

Look for entries related to Git Bash, Git GUI, or MSysGit-specific shell commands, then remove the ones you do not want.

Export Before Deleting Anything

Before editing the registry, export the relevant branch or create a restore point.

That is not just caution theater. Context-menu cleanup is simple when done carefully, but registry mistakes are annoying to reverse from memory.

Restart Explorer After the Change

Windows Explorer may keep showing old context-menu items until the shell reloads.

Stop-Process -Name explorer -Force
Start-Process explorer.exe

You can also sign out and sign back in, but restarting Explorer is often enough.

That avoids the false impression that the registry edit failed when the shell simply has not refreshed yet.

Know the Difference Between Local Git Tools and Shell Extensions

Some Git tools install only shell commands, while others install true shell extensions or helper programs. If the menu item comes back after an update, the installer may be re-adding it.

That is a clue that the permanent fix should be in installer settings or package choice, not only in one manual registry deletion.

Consider Whether You Want All or Only Some Entries Gone

Sometimes the real requirement is not removing all Git menu entries, but only hiding the ones you never use. Manual registry editing gives that granularity, while reinstall choices may be broader.

That is why it is worth deciding whether you want a clean menu, a minimal Git menu, or no Explorer integration at all.

Being precise here prevents unnecessary reinstall cycles and makes the cleanup more reversible.

It also makes documentation easier for the next person who has to maintain the same Windows setup.

Prefer Reversible Changes First

If you are working on a shared machine or a managed environment, prefer installer or maintenance-mode changes before deleting registry keys manually. Reversible changes are easier to explain, audit, and repeat after upgrades.

That is usually the safer administrative path.

Common Pitfalls

• Editing the registry without exporting or backing up the affected keys first.
• Deleting the wrong shell entry because the key names were not inspected carefully.
• Forgetting to restart Explorer and assuming the removal did not work.
• Making a manual change that later gets overwritten by reinstall or upgrade behavior.
• Treating all Git-related context-menu entries as if they come from the same exact component.

Summary

• The safest fix is often to reconfigure or reinstall Git without Explorer integration.
• Manual removal usually means deleting the relevant registry shell keys.
• Back up the affected registry branch before changing it.
• Restart Explorer so the shell reloads the updated context-menu state.
• If entries keep returning, look for installer settings or update behavior rather than repeating manual deletions.