How to Rename a User Profile Folder in Windows 11 Without Breaking Sign-In

Change the Name of a User Profile Folder in Windows 11 (C:\Users)

A practical, step-by-step guide with validation and rollback

Renaming the folder under C:\Users is one of those Windows tasks that looks simple but can break sign-in, OneDrive, or app shortcuts if it is done the wrong way. The safe approach is to rename the folder and update Windows’ mapping to that folder using the user’s SID in the registry. For added compatibility, you can also create a symbolic link from the old path to the new one.

This guide walks you through a clean, repeatable process, plus verification steps and a rollback plan.

---

What you are changing (and what you are not)

• You are changing the profile folder path (example: C:\Users\OldName → C:\Users\NewName)
• You are not necessarily changing:
  • The account display name
  • The sign-in name (local user name, Microsoft account name, Entra ID UPN)
  • The home directory permissions (unless you manually modify them)

Windows ties the profile folder to a SID (Security Identifier). That is why the registry change is based on SID, not on the username.

---

When you should not do an in-place rename

Use the “new profile and migrate” method instead if:

• This is a production work device with a lot of line-of-business apps that may hardcode paths
• The profile is heavily integrated with OneDrive Known Folder Move (KFM), Outlook data files, or legacy apps
• You want the lowest risk, most supportable outcome

I include that method later in the post.

---

Prerequisites and safety checklist

Before touching anything:

1. Back up the user’s data
   • At minimum: Desktop, Documents, Downloads, Pictures
2. Create a restore point
3. Ensure you have a second admin account
   • You must not be signed into the profile you are renaming while you rename it
4. Confirm BitLocker recovery key access
   • Not required for the rename itself, but essential if something goes wrong later

---

Method 1: Rename the existing profile folder (Registry + Folder rename + optional symlink)

Step 1: Sign out of the target account

Sign out of the user whose folder you want to rename.

Step 2: Sign in with a different administrator account

Use another local admin account or a separate admin identity.

Step 3: Find the user’s SID

Open Windows Terminal (PowerShell) and run:

Get-LocalUser | Select-Object Name,SID

If this device is Entra ID or Microsoft account based, you can still use the SID that appears under the ProfileList registry key (next step). For local users, the command above is usually enough.

Step 4: Update the ProfileImagePath in the registry

1. Open Registry Editor (regedit.exe)
2. Browse to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

3. Under ProfileList, you will see SID keys like S-1-5-21-...
4. Click each SID and locate the value:

ProfileImagePath

5. Edit ProfileImagePath to your new folder name

Example:

• Old: C:\Users\OldName
• New: C:\Users\NewName

Tip: The correct SID usually has values like ProfileImagePath, Flags, State, and often a ProfileLoadTimeHigh/Low type of metadata depending on build.

Step 5: Rename the folder under C:\Users

In File Explorer (or elevated command prompt), rename:

• C:\Users\OldName → C:\Users\NewName

If Windows refuses the rename, something is still holding the profile open. Confirm you are not signed into that user and reboot if needed.

Step 6 (Recommended): Create a symbolic link for backward compatibility

Some apps and scripts might still reference the old path. A symlink preserves compatibility.

Open Command Prompt as Administrator and run:

mklink /d "C:\Users\OldName" "C:\Users\NewName"

This creates a directory link so C:\Users\OldName transparently redirects to the new location.

Step 7: Reboot

Do a full reboot before testing sign-in. This clears cached handles and refreshes profile loading behavior.

---

Post-change validation checklist

Sign in to the renamed account and verify the following:

Confirm the profile path

Open Command Prompt and run:

echo %USERPROFILE%

Expected output:

• C:\Users\NewName

Confirm the environment resolves correctly

Open PowerShell and run:

[Environment]::GetFolderPath("UserProfile")
[Environment]::GetFolderPath("Desktop")
[Environment]::GetFolderPath("MyDocuments")

Paths should point to C:\Users\NewName\...

Confirm core shell behavior

• Start menu opens
• Taskbar pins launch
• File Explorer opens to the correct location
• Settings app opens

OneDrive (if used)

If OneDrive is configured:

• Confirm OneDrive signs in successfully
• Confirm syncing works
• Confirm Desktop/Documents/Pictures sync status if KFM is enabled

If OneDrive fails or prompts for setup again, you may need to re-link OneDrive to the new location in OneDrive settings.

Windows Search indexing

If you rely on search heavily:

• Search may show stale results briefly
• Rebuild the index if needed:
  • Settings → Privacy & security → Searching Windows → Advanced indexing options (varies by build)

---

Common issues and quick fixes

“User profile service failed the sign-in”

Usually caused by:

• Folder rename happened but registry path did not match
• ProfileImagePath points to a folder that does not exist

Fix:

• Sign in with the other admin
• Re-check ProfileImagePath
• Ensure C:\Users\NewName exists and contains the profile data

Apps still writing to the old path

Fix:

• Create the symlink (Step 6)
• Check for hardcoded paths in:
  • Scheduled tasks
  • Scripts
  • App configs

OneDrive reconfigures or breaks KFM

Fix:

• Unlink OneDrive (OneDrive settings)
• Re-link and reselect folders
• Avoid manually moving OneDrive content while it is still connected

---

Rollback plan (fast and clean)

If sign-in fails or apps are unstable:

1. Sign in with the other admin account
2. If you created a symlink, remove it (delete the linked folder entry)
3. Rename the folder back:
   • C:\Users\NewName → C:\Users\OldName
4. Revert the registry value:
   • ProfileImagePath back to C:\Users\OldName
5. Reboot and test sign-in again

This rollback works because you are returning Windows to the original SID-to-path mapping.

---

Method 2 (lowest risk): Create a new profile and migrate data

If you want the most supportable result:

1. Create a new local user (or new account profile) with the name you want
2. Sign in once to generate the new profile folder under C:\Users
3. Copy user data from old profile to new profile:
   • Desktop, Documents, Downloads, Pictures
4. Reconfigure:
   • OneDrive
   • Outlook
   • Any apps that store data in AppData
5. When satisfied, remove the old profile

This approach avoids edge cases where applications hardcode the old profile path.

---

Enterprise notes (Intune and managed endpoints)

In managed environments, the biggest risk is not Windows. It is tooling that assumes a fixed path:

• Win32 app install scripts with hardcoded C:\Users\OldName
• Detection rules that check for files under a specific user folder
• Scheduled tasks running in user context
• Legacy apps that store absolute paths

If you manage devices via Intune, treat this as a controlled change:

• Validate install and detection scripts
• Prefer environment variables like %USERPROFILE% over hardcoded paths
• Use proactive remediations to detect stale path references if needed

---