Which TortoiseGit Icon Overlay Settings Remain Effective When Windows 11 Slots Are Exhausted?

Short answer

No. Drive-type and path-list restrictions in TortoiseGit cannot preserve overlay visibility when Windows has already exhausted its shell icon overlay slots. Those settings control where TortoiseGit scans for repositories; they do not influence which overlay handlers Windows loads or in what order.

Why the settings do not help in this case

Windows Explorer enforces a system-wide cap on active shell icon overlay handlers. When competing applications register handlers that sort ahead of TortoiseGit's registry entries, the shell ignores the remaining handlers. TortoiseGit's Icon Overlays settings reduce the workload for handlers that do load by excluding network drives, removable media, or specific paths. They do not create additional slots, change priority, or force Windows to prefer TortoiseGit over another application.

What actually determines visibility

Overlay priority is governed by the alphabetical ordering of subkeys under ShellIconOverlayIdentifiers. If TortoiseGit's entries fall outside the active limit, no combination of local, network, or removable drive settings inside TortoiseGit will make the icons appear. The handler is effectively invisible to the shell, so its scope settings are irrelevant.

Windows 11 considerations

Windows 11's shell rendering can differ from earlier versions, and the exact number of slots honored may vary by build or view mode. The underlying constraint remains the same: if the handler is not among the slots the shell chooses to load, overlays will not render. Consequently, Windows 11 does not require a different TortoiseGit configuration strategy—it requires ensuring TortoiseGit's handlers are actually within the active set.

What to check before changing anything

Because manual registry edits to ShellIconOverlayIdentifiers are unsupported by TortoiseGit and may be overwritten by updates, treat them as a last resort. First verify the actual state:

• Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers.
• Count the subkeys and note their alphabetical order. Identify which applications own entries that sort ahead of TortoiseGit.
• Confirm whether TortoiseGit entries (often prefixed with Tortoise) appear within the active range.

Practical next step

If TortoiseGit entries exist but sit outside the active limit, the only reliable fix is to reduce competition—disable or uninstall overlay handlers from other applications that sort earlier, or accept that overlays may be unavailable in that environment. If TortoiseGit entries are absent entirely, the issue is a registration or installation problem, not slot exhaustion.

Missing diagnostic detail

Are TortoiseGit's overlay identifiers present in the ShellIconOverlayIdentifiers key, and do they appear within the first several entries? If they are absent, the recommendation changes from slot management to repairing the TortoiseGit installation.