How to Remove Shortcut Arrows From Desktop Icons in Windows 11

56

Windows 11 puts a small arrow over many desktop shortcuts so users can distinguish a shortcut from the original file, folder, application or webpage. The overlay is easy to ignore, but on a carefully arranged desktop it can make icons look busier than necessary. If you want a cleaner desktop, the arrow can be customized without deleting the shortcuts themselves.

This guide covers the complete workflow rather than only giving a single registry command. It explains what the overlay is, how the Registry method works, how to do the same operation with PowerShell or Command Prompt, how to use a transparent ICO file, how to refresh Explorer without rebooting the PC, how to rebuild the icon cache when Windows keeps showing an old overlay, and how to restore the normal Windows behavior.

If you have already changed shortcut overlays on a Windows PC and later saw a black square, white box, blank overlay or another unexpected image, do not treat that symptom as a normal part of removing the arrow. It usually means the replacement overlay resource is not being loaded as intended. The safest troubleshooting path is to inspect the value named 29, remove an invalid custom reference, refresh Explorer and only then rebuild the icon cache if necessary.

What the Windows 11 Shortcut Arrow Actually Is

The shortcut arrow is an overlay drawn on top of the icon associated with a Windows shortcut. It is not normally part of the application’s executable icon and it is not stored as part of the target program’s artwork. This is why changing the overlay can make dozens of desktop shortcuts look different at once without changing the applications themselves.

A shortcut is still a shortcut after the arrow is hidden. Double-clicking it launches the same target, the shortcut’s path remains the same, and removing the visual overlay does not uninstall or modify the application. The main change is how Explorer renders the shortcut.

This distinction also explains why changing an individual shortcut icon is a different operation. The Change Icon button in a shortcut’s Properties dialog changes the icon used by that shortcut. The Shell Icons registry setting discussed in this article changes the overlay used by Windows Explorer.

Before You Change the Registry

Registry customization is reversible, but it should not be treated like an ordinary Settings switch. The HKLM registry location affects the Windows shell configuration and requires administrator permission. Before making the change, create a restore point or export the relevant Registry key.

If this is a work PC, a managed device, or a computer where Registry changes are restricted by policy, check the local administration rules before proceeding. A command that works on a personal Windows installation can be blocked by organizational security controls.

Also decide which result you actually want. If you only want a cleaner desktop, hiding all desktop icons may be enough. If you want shortcuts to remain visible but without the arrow overlay, use the shortcut-overlay procedure in this article. If you want different artwork for one application, change that shortcut’s icon instead.

Quick Comparison of the Available Methods

Method	What it changes	Administrator required	Explorer refresh
Registry Editor	Shell shortcut overlay value	Yes for HKLM	Usually
PowerShell	Same registry value by command	Yes for HKLM	Usually
Command Prompt / reg.exe	Same registry value by command	Yes for HKLM	Usually
Transparent ICO	Uses a custom overlay resource	Yes for HKLM	Usually
Remove value 29	Returns overlay handling to Windows	Yes for HKLM	Usually

Method 1: Remove Shortcut Arrows With Registry Editor

Registry Editor is the easiest method to audit because every part of the change is visible. The key used for this customization is under the Explorer configuration branch. Do not confuse the Shell Icons key with ShellIconOverlayIdentifiers. They are different registry locations and serve different Explorer overlay mechanisms.

Steps

1. Press Win + R, type regedit, and press Enter. Approve the User Account Control prompt if requested.
2. Go to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons. If Shell Icons does not exist, create it under Explorer.
3. Before editing the value, export the Shell Icons key or record its existing 29 value so you can roll back the change.
4. Create a String Value named 29 if it does not already exist.
5. Set 29 to the overlay resource or transparent ICO path you have chosen. Use the exact syntax required by that resource.
6. Close Registry Editor and restart Windows Explorer from Task Manager or PowerShell. A full Windows restart is normally unnecessary for the Explorer refresh.
7. Check several desktop shortcuts. If a black square or another unexpected overlay appears, restore the previous 29 value instead of adding another Registry override.

Open the Run dialog with Win + R, enter regedit, and press Enter. Approve the User Account Control prompt if Windows asks for elevation.

Navigate to the following key:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons

If Shell Icons is missing, right-click Explorer, select New > Key and name it Shell Icons. Then select the new key.

Inside Shell Icons, right-click an empty area in the right pane, select New > String Value and name the value 29. The value name must be exactly 29.

Double-click 29 and enter the overlay resource you want to use. A transparent shell32 resource is commonly documented as %windir%System32shell32.dll,50 in Microsoft Q&A material. Other historical Windows builds and documented examples use negative resource indexes such as -50, so do not blindly mix values from different tutorials. If a particular resource produces a black or blank square on your Windows build, remove the custom value rather than continuing to stack additional registry modifications.

Method 2: Do the Same Change With PowerShell

PowerShell is useful when you want a repeatable procedure or when you are configuring several machines. The following commands create the Shell Icons key if necessary, create or replace the 29 string value, and then restart Explorer.

Steps

1. Open Windows Terminal or PowerShell with Run as administrator.
2. Set a variable containing the HKLM Shell Icons path.
3. Create the Shell Icons key if it is missing.
4. Write the 29 string value with the chosen overlay resource.
5. Restart Explorer with Stop-Process -Name explorer -Force followed by Start-Process explorer.exe.
6. Verify the value with Get-ItemProperty and check several shortcuts.
7. If the result is wrong, remove or restore the 29 value and restart Explorer again.

Open Windows Terminal or PowerShell using Run as administrator. Use the elevated shell because the HKLM registry path is protected.

$path = 'HKLM:SOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons'

New-Item -Path $path -Force | Out-Null

New-ItemProperty `
 -Path $path `
 -Name '29' `
 -PropertyType String `
 -Value "$env:SystemRootSystem32shell32.dll,50" `
 -Force | Out-Null

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

The -Force switch makes the operation idempotent for this purpose. If the key already exists, New-Item does not require you to create it manually. New-ItemProperty with -Force replaces an existing value named 29.

If PowerShell returns Access is denied, the terminal is probably not elevated. Close it, start Windows Terminal or PowerShell with Run as administrator, and run the commands again. If the command succeeds but the icon does not change, inspect the value with the verification command later in this article rather than repeatedly writing new values.

Method 3: Use Command Prompt and reg.exe

Command Prompt can make the same Registry change through reg.exe. This is useful on systems where you prefer CMD or when the procedure needs to be included in a batch script.

Steps

1. Open Command Prompt as administrator.
2. Use reg add to create or update the Shell Icons key and its 29 value.
3. Restart Explorer with taskkill /F /IM explorer.exe and then start explorer.exe.
4. Inspect multiple shortcuts after Explorer returns.
5. If the result is incorrect, use reg delete to remove the custom 29 value or restore your backup.

reg add "HKLMSOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons" /v 29 /t REG_SZ /d "%windir%System32shell32.dll,50" /f

After the command completes, restart Explorer:

taskkill /F /IM explorer.exe
start explorer.exe

The /f option to reg add overwrites an existing value. Verify the command before executing it because the Registry path and value name are the important parts of this operation.

Method 4: Use a Transparent ICO File

A custom transparent ICO file is another approach. Instead of asking Windows to load a particular shell resource index, the 29 value can point to a file you control. This is useful when you have a known-good transparent icon and want the overlay asset to remain independent of a particular shell resource index.

Steps

1. Create or obtain a genuine transparent ICO file. The image must contain transparency rather than a black background.
2. Store the ICO in a permanent location that will remain available to Windows Explorer.
3. Create or update the 29 Registry value so it points to the ICO file.
4. Restart Explorer and test shortcuts at more than one icon size.
5. If Explorer shows a black square or a missing overlay, verify the ICO file path and transparency first, then restore the previous 29 value if necessary.

For example, if you have a transparent ICO file at C:WindowsNoShortcutArrow.ico, the Registry value can point to that file.

reg add "HKLMSOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons" /v 29 /t REG_SZ /d "C:WindowsNoShortcutArrow.ico" /f

Do not put a temporary file in Downloads and then delete it. Explorer needs to be able to access the referenced file whenever it loads the overlay. A missing file can result in an incorrect overlay or a generic icon.

A transparent ICO should contain actual transparent pixels rather than a black background. Test the file at multiple icon sizes if you are creating it yourself. An image that looks transparent in an editor is not necessarily encoded as a Windows ICO with the transparency and sizes Explorer expects.

Why Some Shortcut-Arrow Tutorials Cause Black Squares

Black squares are not the intended result of removing the shortcut arrow. A common failure mode is a bad or missing replacement overlay resource. Older tutorials also mix different shell32.dll resource indexes, custom blank ICO files and cache-clearing instructions without explaining that the resource behavior can differ between Windows versions.

If you see a black square where the arrow should be, first inspect the value named 29. If it points to a file that no longer exists, restore the normal configuration by removing the value. If it points to a shell32 resource that behaves incorrectly on your system, remove the value and let Windows return to its normal overlay handling.

Do not keep changing between -50, 50, -30, 29 or other resource numbers at random. Those numbers are resource identifiers, not universal Windows settings. A number copied from an older tutorial can have a different visual result on another build.

Refresh Windows Explorer Without Restarting the PC

After changing the Registry, Explorer may still have the previous overlay loaded. In many cases you do not need to restart Windows. Restarting Explorer is enough to reload the desktop shell.

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

You can also do this from Task Manager. Press Ctrl + Shift + Esc, locate Windows Explorer in the process list, right-click it and choose Restart. The desktop and taskbar will disappear briefly while Explorer restarts and then return.

A full Windows reboot can still be useful if Explorer refuses to reload the change, but it should not be the first troubleshooting step.

Rebuild the Windows Icon Cache When the Old Overlay Remains

If Explorer has been restarted but Windows still shows the old arrow, blank square or stale icon, the icon cache may be holding the previous appearance. Rebuilding the cache is a troubleshooting step, not a replacement for correcting an invalid Registry value.

Open Command Prompt as Administrator and run:

taskkill /F /IM explorer.exe
del /A /Q "%localappdata%IconCache.db"
del /A /F /Q "%localappdata%MicrosoftWindowsExplorericoncache*"
start explorer.exe

The commands stop Explorer before deleting its cached icon files and then start Explorer again. Some Windows versions maintain several icon-cache files, which is why the second delete command uses a wildcard.

If the problem returns immediately after the cache is rebuilt, stop rebuilding the cache and inspect the underlying Registry value or custom ICO file. A cache rebuild cannot permanently repair an invalid overlay resource.

Verify the Registry Value With PowerShell

After applying the change, verify what Windows actually stored. This is especially useful when troubleshooting a command that appears to run successfully but does not change the desktop.

Get-ItemProperty `
 "HKLM:SOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons" `
 -Name 29

You can also check whether an older per-user override exists:

Get-ItemProperty `
 "HKCU:SoftwareMicrosoftWindowsCurrentVersionExplorerShell Icons" `
 -Name 29 `
 -ErrorAction SilentlyContinue

If both HKLM and HKCU contain custom values, document them before deleting anything. The goal is to remove the unintended override, not to make multiple unrelated Registry changes.

How to Restore the Normal Shortcut Arrow

The cleanest rollback is to remove the custom 29 value you created and then restart Explorer. This returns the Shell Icons configuration to its default state instead of replacing one custom overlay with another.

Remove-ItemProperty `
 -Path "HKLM:SOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons" `
 -Name "29" `
 -ErrorAction SilentlyContinue

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

If you also created an HKCU value, remove it separately:

Remove-ItemProperty `
 -Path "HKCU:SoftwareMicrosoftWindowsCurrentVersionExplorerShell Icons" `
 -Name "29" `
 -ErrorAction SilentlyContinue

Microsoft Q&A also documents explicit values for restoring a visible shortcut arrow on some Windows configurations. Removing an override is generally the simpler rollback when you want Windows to regain control of the default appearance.

Create Reversible .reg Files

A Registry file is convenient for repeatable setup, but it should contain only the change you intend to make. Save a copy of the original state before importing a customization.

The following example writes the shortcut overlay value:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons]
"29"="%SystemRoot%\System32\shell32.dll,50"

A rollback file can delete the value:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons]
"29"=-

Before importing a .reg file downloaded from the internet, open it in Notepad and inspect every key and value. A Registry file can contain changes unrelated to the visible problem, so do not merge an unknown file simply because its filename suggests it removes shortcut arrows.

PowerShell: Complete Backup, Change and Rollback Workflow

For administrators who want a more controlled PowerShell workflow, export the key before changing it. The export command uses reg.exe because it is available with Windows and creates a standard Registry backup.

reg export "HKLMSOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons" "$env:USERPROFILEDesktopShell-Icons-Backup.reg" /y

If the key does not exist yet, reg export can fail. That is not a reason to create unrelated keys. You can create the key, make the change, and keep a copy of the exact commands used for rollback.

A useful operational habit is to record the original 29 value, if any, before replacing it. That makes restoration more precise than assuming that deleting the value is always the desired rollback.

Troubleshooting: Access Is Denied

HKLM is protected. If New-Item, New-ItemProperty or reg add returns Access is denied, confirm that the terminal is elevated. The title bar of an elevated Windows Terminal normally indicates administrator privileges.

Do not work around a permission error by changing permissions on the Registry key. For this customization, an elevated administrator shell is the normal route. Changing Registry ownership or permissions creates a larger security and maintenance problem than the shortcut-arrow customization is worth.

Troubleshooting: Shell Icons Does Not Exist

The absence of Shell Icons is not itself an error. Create the key under Explorer when you need to add the custom value. Do not create ShellIconOverlayIdentifiers instead. That similarly named key is not a substitute for Shell Icons.

Troubleshooting: The Arrow Is Gone but a Black Square Appears

Stop and inspect the value named 29. If it references a custom ICO, verify the file exists and is actually transparent. If it references a shell32 resource, remove the custom value and restart Explorer. This is safer than trying multiple resource indexes until one appears to work.

If removing 29 restores normal icons, the replacement overlay was the problem. Rebuild the icon cache only after the Registry state is correct. This separates configuration problems from cached-display problems.

Troubleshooting: Nothing Changes After Explorer Restarts

First verify the Registry value. Next check whether another tool is managing shortcut overlays. Some desktop-tweaking utilities and old customization tools can leave behind Registry values after the utility itself is removed.

Also check whether the shortcut you are looking at is actually a shortcut. The overlay is associated with shortcut presentation. A normal executable, folder or document icon may not use the same indicator.

Related Guide: Customize Desktop Icons in Windows 11

Removing shortcut arrows is only one part of desktop customization. If you also want to resize icons, hide the desktop, add or remove standard Windows icons, create shortcuts or change an individual shortcut’s artwork, see our companion guide: How to Customize Desktop Icons in Windows 11.

The companion article covers the built-in Windows methods and keeps those broader personalization steps separate from the Registry-based shortcut-overlay procedure.

How to Check the Shortcut Before Changing Anything

Before modifying the Registry, right-click one of the affected desktop icons and choose Properties. If the item has a Shortcut tab, you are looking at a Windows shortcut. Note the target and the current icon before changing the overlay. This simple check prevents you from changing a shell setting when the actual problem is one damaged shortcut.

If the shortcut launches correctly and only the small arrow is visually unwanted, the overlay is the right thing to change. If the shortcut does not launch, fix the target or recreate the shortcut first. Changing the overlay will not repair a broken target path.

If only one shortcut has an unexpected square while all other shortcuts look normal, do not immediately change the global Shell Icons value. A global overlay setting affects the shell’s presentation of shortcuts and should be reserved for a global presentation change.

What the 29 Registry Value Means

The value named 29 is a convention used by Windows shell customization guides to select the resource used for the shortcut overlay. It is not a general-purpose Windows setting exposed in the Settings application. That is why tutorials that remove the shortcut arrow normally create a Shell Icons key and a string value named 29.

The data stored in 29 is important. It can identify a shell resource or a custom icon file. A correct key with incorrect data can be worse than having no key at all because Explorer may successfully find the configuration but fail to load a useful overlay.

Treat the value as a pointer to an overlay resource, not as a magic switch. This is also why copying a value from a Windows 7 or Windows 10 tutorial without testing it on Windows 11 can produce unexpected results.

When You Should Not Remove the Shortcut Arrow

The arrow is useful when a desktop contains a mixture of shortcuts and original files. Without it, a user can accidentally treat a shortcut as the original file or folder. This is particularly relevant on shared PCs where different people use the same desktop.

If you regularly create temporary shortcuts, keeping the default indicator can make it easier to distinguish launch links from original documents. In that situation, changing icon size or organizing shortcuts into folders may provide the cleaner desktop you want without changing the shell overlay.

Accessibility is another consideration. The overlay provides a visual distinction. Removing it is a cosmetic choice, so make sure the result does not make the desktop harder for you or another user to understand.

A Safer Troubleshooting Order

When a shortcut-overlay customization fails, troubleshoot from the smallest change to the largest. First inspect the 29 value. Second restart Explorer. Third remove an invalid custom overlay. Fourth rebuild the icon cache if the configuration is already correct. Only then consider a full Windows restart.

This order matters because an icon-cache rebuild cannot correct a bad Registry value. Likewise, repeatedly restarting Explorer cannot make a missing ICO file appear. Each step should address a different layer of the problem.

If you are documenting the procedure for another person, ask them to capture the current 29 value before changing it. That gives you a concrete before-and-after comparison instead of relying on memory.

PowerShell One-Line Verification and Rollback

For a quick diagnostic, PowerShell can read the current 29 value without changing it. Use the following command in an elevated PowerShell session:

Get-ItemProperty "HKLM:SOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons" -Name 29 -ErrorAction SilentlyContinue

Frequently Asked Questions: Advanced Cases

Can I keep the arrow on some shortcuts but remove it from others?

The Shell Icons overlay is a shell-level presentation setting, so it is not designed as a simple per-shortcut toggle. If you need different visual treatment for individual shortcuts, changing their icons or organizing them into folders is a more targeted approach.

Will deleting the Shell Icons key itself restore Windows?

Usually the important part is the custom value named 29. Removing the value is more precise than deleting the entire key, especially if another customization has been stored under Shell Icons.

Should I change HKCU or HKLM?

The documented shortcut-arrow customization commonly uses the HKLM Explorer Shell Icons location. An HKCU value may exist from another customization or tool, so inspect both locations when troubleshooting. Do not create both simply because a tutorial shows two alternatives.

Can I automate the change on several PCs?

Yes. PowerShell, reg.exe and a reviewed .reg file can make the procedure repeatable. For managed environments, test the configuration on the target Windows build first and keep a rollback script.

Does rebuilding icon cache fix the Registry?

No. Cache rebuilding refreshes stored icon information. It does not change the Registry value, repair a missing ICO file or select a different shell resource.

Final Checklist Before You Change the Shortcut Overlay

Before changing the shortcut overlay, confirm that the desktop shortcuts actually work. Check one or two representative shortcuts and make sure the issue is visual rather than a broken target.

Next, check whether a previous customization already exists at HKLMSOFTWAREMicrosoftWindowsCurrentVersionExplorerShell Icons. If value 29 is already present, export the key or record its data before replacing it. This is especially important if another desktop customization tool was previously installed.

After the change, restart Explorer and inspect several shortcuts. If the result is correct, keep the rollback command with your notes. If the result is wrong, remove the custom value rather than layering another replacement over it.

This process gives you a controlled before-and-after state and makes it much easier to identify whether a problem comes from Registry configuration, the overlay asset or the icon cache.

Why This Article Keeps Icon-Cache Repair Separate

Icon-cache repair is often included in shortcut-arrow tutorials as if it were the actual arrow-removal mechanism. It is not. The Registry value controls which overlay Explorer attempts to display, while the icon cache stores information Explorer has already loaded.

If the Registry points to a valid transparent overlay but Explorer still shows the old arrow, cache refresh can help. If the Registry points to a missing ICO file, rebuilding the cache only makes Explorer reload the same broken configuration.

Keeping these two layers separate makes troubleshooting faster. Fix the configuration first, refresh Explorer second and rebuild the cache only when stale rendering remains.

Frequently Asked Questions

Will removing shortcut arrows delete my shortcuts?

No. The shortcut files remain on the desktop and continue pointing to the same targets. The procedure changes the overlay displayed by Explorer.

Will my applications be modified?

No. The application installation and executable are not changed. The Registry setting controls the visual overlay used for shortcut icons.

Do I have to restart Windows?

Usually no. Restarting Windows Explorer is normally enough to make the desktop reload the change. A full reboot is a fallback if Explorer continues showing stale state.

What is the difference between Shell Icons and ShellIconOverlayIdentifiers?

They are different Registry locations. This article uses Shell Icons for the shortcut-arrow customization. ShellIconOverlayIdentifiers is used for a different class of Explorer overlay handlers and should not be substituted for Shell Icons.

Can I remove the arrow without the Registry?

Windows 11 does not provide a normal Settings switch specifically for removing the shortcut arrow. You can avoid seeing desktop arrows by hiding all desktop icons, but that also hides the shortcuts. Third-party utilities can automate the Registry change, but they add another software dependency.

Why did an older tutorial use a different shell32.dll number?

The number is a resource identifier. Different tutorials and Windows generations have used different resource indexes. A resource reference that works on one build is not a universal guarantee for every Windows 11 build. Test the actual result and keep a rollback path.

What should I do if I get black squares?

Remove the custom 29 value, restart Explorer, and verify that the normal icons return. If they do, the replacement overlay was the cause. Only rebuild the icon cache if stale rendering remains after the Registry configuration is corrected.

Can I use a transparent ICO instead of shell32.dll?

Yes. A custom transparent ICO can be referenced by the 29 value. Keep the file in a permanent location and make sure it contains proper transparency and icon sizes.

Is the change reversible?

Yes. Export the relevant Registry key before changing it, or record the original 29 value. Removing the custom value is the normal rollback when you want Windows to handle the overlay again.

Bottom line: Removing the shortcut arrow is a small visual customization, but the underlying setting lives in the Windows Explorer Registry configuration rather than a normal personalization switch. The safest approach is to back up first, make one controlled change, restart Explorer, verify the result and keep a simple rollback command ready. If the desktop develops a black or blank overlay, fix the Registry resource first instead of repeatedly rebuilding the icon cache.

Sources: Microsoft Support documents Windows desktop icon customization, including Desktop icon settings, shortcut creation, resizing and showing or hiding desktop icons. Microsoft Q&A contains documented examples of the Explorer Shell Icons registry location and value 29 used for shortcut overlays. These registry instructions are a customization technique rather than a dedicated Windows Settings feature.