Risks of Modifying MountPoints2 Key in Regedit

Modifying or deleting the MountPoints2 registry key in Windows is often done to clear USB connection history, resolve drive letter conflicts, or reset mapped network shares. However, altering this key directly through the Registry Editor (Regedit) carries several distinct operational and system risks. Because MountPoints2 manages how the operating system tracks, mounts, and configures user-specific removable and network storage, unauthorized or improper changes can lead to broken drive mappings, lost preferences, and shell instability.

Understanding the MountPoints2 Key

Located at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2, this registry branch stores cached information regarding every volume, CD/DVD, USB drive, and mapped network share connected to a specific user account. It maintains device unique identifiers (UUIDs), AutoRun actions, drive icons, and folder configurations.

Key Risks of Modifying MountPoints2

1. Loss of Persistent Network Drive Mappings

The MountPoints2 subkeys hold vital connection parameters for shared network folders. Deleting or altering these subkeys can immediately sever remembered credentials, disconnect mapped drives, and prevent the system from automatically reconnecting to network resources upon boot.

2. Disruption of Removable Media Behavior

Windows relies on cached data in this key to determine AutoPlay and AutoRun behavior for specific devices. Modifying these entries can cause: * Failure of customized AutoPlay prompts. * Inability to remember assigned drive icons or volume labels. * Delays when connecting previously recognized USB drives as Windows attempts to rebuild the volume metadata.

3. Broken Shortcuts and Recent File Paths

Many Windows applications, including File Explorer, cache direct volume paths referenced within MountPoints2. Clearing or corrupting this key can break shortcuts pinned to the Quick Access menu, clear recent document histories linked to external storage, and disrupt software that depends on static device identifiers.

4. Windows Explorer and Shell Instability

Incorrectly editing binary values or permissions within MountPoints2 can cause Windows Explorer (explorer.exe) to crash, hang, or fail to refresh connected storage devices in the “This PC” view. If Explorer cannot read a corrupted entry, it may enter a crash loop upon volume detection.

5. Accidental Override of Group Policy and Security Configurations

In managed enterprise environments, administrators use MountPoints2 policies to restrict execution of scripts or binaries from removable drives. Deleting or modifying subkeys can inadvertently strip these security configurations until the next Group Policy update, potentially exposing the workstation to unauthorized AutoRun scripts.

Safe Modification Best Practices

If modification of the MountPoints2 key is necessary for troubleshooting: * Export a Backup: Always right-click the MountPoints2 key and select Export to create a .reg backup before deleting or changing values. * Target Specific Subkeys: Avoid deleting the root MountPoints2 folder; remove only the specific device or network GUID causing the conflict. * Restart Explorer: Restart the Windows Explorer process or log out of the user account after making edits to ensure the registry caches reload cleanly.