windows-desktop-path-fallout-repair

name	windows-desktop-path-fallout-repair
description	Use when a Windows Desktop folder was renamed, moved, redirected, or display-renamed and the user wants broken paths, shortcuts, Explorer TypedPaths, desktop.ini, registry mappings, scripts, and project references repaired systemically rather than one file at a time.

Windows Desktop Path Fallout Repair

Core Workflow

1. Identify the intended Desktop path and the old path strings that keep reappearing.
2. Read authoritative Windows state first:
   • HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
   • HKCU:\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
   • Desktop GUID values when present
   • the live Desktop folder's desktop.ini
3. Back up Desktop contents before moves, renames, or consolidation.
4. Normalize the real Desktop folder and display name.
5. Repair active references in scripts, configs, shortcuts, and Explorer history.
6. Restart Explorer only after registry and file edits are complete.
7. Re-scan for the old path strings and report any true missing project folders as a separate issue.

Repair Targets

• User Shell Folders and Shell Folders Desktop values.
• Desktop GUID mappings.
• desktop.ini display name and localized resource settings.
• .lnk files, using WScript.Shell objects to update TargetPath, WorkingDirectory, and Arguments.
• Explorer TypedPaths.
• Batch files, PowerShell scripts, Python scripts, IDE configs, and recent project files that still contain the old path.

Decision Rules

• Use targeted registry keys before broad registry scans.
• Back up before moving or deleting Desktop content.
• Repair the real Desktop mapping before cleaning references, or scans will stay noisy.
• Do not fabricate a missing project directory just because an old shortcut points to it.
• If a script still fails after path repair, branch into ordinary project debugging or non-ASCII path handling.

Verification

• Windows registry values point to the intended Desktop path.
• The visible Desktop display name is correct after desktop.ini and Explorer refresh.
• The target Desktop folder exists and contains the expected files.
• Shortcuts resolve to real targets or unresolved targets are reported explicitly.
• TypedPaths no longer points at the old Desktop path.
• Active text/config scans no longer show the old path except in logs or backups that are intentionally left untouched.