Wrong Name in C:\Users Folder in Windows 11 and 10 - Can't rename C:\users [Solution]

If C:\Users\ has the wrong name in it, the honest answer is no — do not rename that folder, and Windows refusing to let you is doing you a favor. The name came from the first five characters of the email address you signed in with, it was set once when the account was created, and hundreds of things on your PC now record that full path by name. Rename it and you get a half-working profile, not a renamed one. The route that works: create a new account with the name you want, sign in once, move your files across, delete the old account. An evening's work, and nothing is left pointing at a folder that no longer exists.

The Saturday Jake lost to a folder name

A customer brought a laptop into Jake's shop with a small, specific request. Her name is Priya. The folder said C:\Users\priya on her work machine and C:\Users\pkuma on this one, and it irritated her every time she went looking for a file. Could he change it?

Jake found a video, followed it, and it worked. Folder renamed, registry value changed, machine restarted, name correct on screen. He charged her for twenty minutes.

She was back on Thursday. The Store would not open. OneDrive was complaining about a location it could not find, over and over. Her tax software could not see last year's file, and her browser had forgotten every password.

Jake spent the whole of Saturday on it — shop shut, a full trading day gone — and ended up doing what he should have done on Tuesday: a fresh account, files moved across, programs reinstalled one at a time. He never charged her for the Saturday.

"It worked, though," he said afterwards. "That is what I do not get. It genuinely worked. I checked."

Ethan was less surprised. "You checked the one thing that was easy to check. Windows found her profile, so the desktop appeared. Everything else with her old folder path written down was still pointing at a folder that had stopped existing an hour earlier, and none of that shows up until you try to use it."

"So it broke on Tuesday and did not tell me until Thursday."

"And that," Ethan said, "is exactly why we do not recommend it. Not that it fails — that it fails late, in pieces, somewhere else."

Where that name came from, and the five-character rule

Nothing went wrong. The name is the output of a rule. When Windows creates a profile for an account signing in with a Microsoft account it needs a folder name, and it cannot use the email address itself — an at sign, dots and sixty-odd characters make a terrible folder name. So it takes the part before the at sign and keeps the first five characters.

Five characters explains almost every complaint on this subject. The truncation is why the name looks like a typo rather than a decision, and why two people at the same company can end up with the same folder — when that happens Windows adds a suffix to keep them apart, which is where names like pkuma000 come from.

Two things matter for everything below. It happens once, the first time that account signs in on that PC. And it is never revisited, because Windows has nothing to revisit it against.

Our guide to checking whether your account is local or Microsoft settles which kind you have in fifteen seconds. Local accounts get a folder named after the account, which is why this is almost entirely a Microsoft account problem.

Three names, and why changing two does not change the third

This is the part that costs people an afternoon. They change their name somewhere, restart, look at the Users folder, and find nothing has moved.

Microsoft's own support documentation is unusually direct here. It confirms that renaming a user account does not change the profile path, and under a heading marked Status calls the behavior by design. That word matters: it is not a bug awaiting a fix, so no update will correct it for you.

If what actually irritates you is the wrong name on the lock screen every morning, that part is fixable in two minutes — our post on changing the user account name walks through it. Just go in knowing the folder will not follow.

And if you are here because something rejected a name you typed rather than because a folder looks wrong, that is a different problem with an easier answer: our guide to finding your Windows username covers which of your names each box is asking for.

What actually breaks when you rename it

"Everything breaks" is useless as a warning — it sounds like the writer covering themselves. Here is the specific version.

Windows offers programs a proper way to ask where your profile is. Most do not use it. They ask once, at install time, get back C:\Users\pkuma\..., and write that string into a settings file or a registry value. From then on they are reading back a sentence they wrote down years ago.

We counted, on the machine this post was written on. In one registry hive — the one holding this account's own settings — there are 315 values containing the literal text of this profile's path. Not 315 references to "the current user". Three hundred and fifteen hard-coded copies of one folder name, plus 4,287 more in the machine-wide hive. A rename updates none of them.

The one Microsoft names itself

Microsoft publishes the folder-rename procedure, which is why so many guides exist. It then attaches a warning that is startlingly specific: do not apply this on machines running Windows 10 or later, because it can cause the winget command to stop working.

winget is Windows Package Manager, the built-in tool that installs software from the command line. It breaks because your account's Path setting — the list of folders Windows searches when you type a command — holds the absolute path to it, and nothing rewrites that when the folder moves.

Worth sitting with: the clearest documented objection to renaming the folder is on Microsoft's own page describing how to rename it.

The rest, in the order you will notice it

• OneDrive. Loudest and fastest. It stores the absolute path to your local folder and complains it cannot find it, repeatedly. Where folder backup was on, your Desktop and Documents lived inside that path — which is how a rename makes files look deleted.
• Store and packaged apps. Strict about where they live. Calculator, Photos, the Store itself — the ones that either open instantly or not at all.
• Your account's Path, TEMP and TMP. All absolute, all stale. Stale temporary folders make installers fail with errors that say nothing about profiles.
• Anything installed "for you" rather than for the whole PC. Python, Node, VS Code, Teams, most browsers, most developer tooling.
• Browser profiles. Saved passwords, sessions, extensions. The browser looks in the old path, finds nothing, starts fresh. Priya's forgotten passwords were this.
• Scheduled tasks, backup jobs and sync tools pointed at your Documents folder. These fail silently, which is the worst way for a backup to fail.

None of it is catastrophic alone. That is the problem: no single failure is bad enough to point back at the rename, so you spend a fortnight fixing six unrelated-looking things.

The three routes, ranked, with a straight recommendation

There are exactly three things you can do. We will say which one we would pick, because a page that lists three options evenly and lets you choose has not actually helped.

Route 1: a new account with the right name, and move in

The supported answer, and the one we would take on any machine that matters. You are not renaming anything: you let Windows create a fresh profile folder, using the naming rule in your favor this time, then move in.

The detail most guides skip: create it as a local account. A local account's folder is named after the account exactly, with no truncation and no email involved. Create it as a Microsoft account and you get five characters of an email all over again, which is how people end up doing this twice. Attach the Microsoft account afterwards — the folder already exists by then and keeps its name.

Route 2: leave it alone

Genuinely. For most people it is the right answer and nobody ever says so. Ask what the folder name actually costs you: it is not on the sign-in screen or in the Start menu, not what people see when you share a file, not your email address. It appears in file paths, occasionally in an error message, and in File Explorer when you go looking for it.

"That is a bit dismissive though," Jake said. "Priya looks at it every day. It is her computer and it has got the wrong name on it. That is not nothing."

"It is not nothing, no," Ethan said. "I would just want her to know what it costs before she buys it. If the answer is still yes, fine — do Route 1 and do it properly. What I object to is people paying an evening of risk for something they were told would take ninety seconds."

Two cases where leaving it stops being reasonable: the name contains something you do not want on your screen — an old surname, an ex-partner, a former employer — or you are hitting real build errors because development tooling dislikes the path. Irritation is not a reason. Those two are.

Route 3: the registry route, which we do not recommend

You will find this everywhere, so here it is accurately, including the parts the videos leave out. We are not recommending it — we are documenting it so that if you do it anyway, you know what to clean up. It needs a second account because you cannot rename a folder that is in use, and yours is in use for as long as you are signed in.

1. Back up first. Files and registry, per the warning above, plus a System Restore point.

2. Get a second administrator account. Create a local account and make it an administrator. Older guides — ours from 2017 included — tell you to enable the hidden built-in Administrator instead. That still works, but it is the worse choice now: the built-in account runs without Admin Approval Mode, so packaged apps refuse to open there, and you end up troubleshooting where half the tools will not start.

3. Note your SID. The security identifier is the long string starting S-1-5-21 that Windows really uses to identify your account. Run whoami /user before you sign out and write it down — guessing later is how people edit the wrong account.

4. Sign out completely. Not lock, not switch user — a locked session still has the folder open.

5. Rename the folder from the second account. On Windows 11 rename is an icon in the compact right-click menu rather than a word; if you cannot see it, press Shift + F10.

6. Edit the registry. Open Registry Editor and go to:

Every account has a key here named after its SID, holding a ProfileImagePath value with the path to that profile. Change yours to match the folder's new name, and nothing else.

7. Sign out and back into your own account. If the desktop looks normal, the profile loaded. That is all you have proved.

8. Now the part nobody mentions. Your account's environment settings still hold the old path. Open HKEY_CURRENT_USER\Environment and correct Path, TEMP, TMP and any OneDrive value, then search the registry for the old folder name and work through the results.

Step 8 is the whole argument. It has no end condition: you are not finished when the list is empty, you are finished when you get bored, and everything you did not reach fails next month.

Moving into the new account without losing anything

Create it, and create it local

Go to Settings → Accounts → Other users → Add account. When it asks for an email, choose the option to continue without one, then to add a user without a Microsoft account. Type the name you want the folder to have: short, lower case, no spaces, no punctuation. That exact string becomes the folder. Then make it an administrator.

Sign into the new account once. Not optional — the profile folder does not exist until the account signs in for the first time. Let it finish setting up, then sign out.

Copy the right things, and only the right things

Sign back into your old account and copy across Documents, Desktop, Downloads, Pictures, Videos, Music, and anything else you keep at the top level of your profile.

Do not copy AppData. That hidden folder inside your profile is where programs keep their settings, and it is stuffed with absolute paths pointing at the old profile. Copying it wholesale turns a clean new profile into a copy of the old broken one. If one specific thing in there cannot be lost — a mail archive, a saved game, a license file — copy that one folder deliberately. Copying the lot is not the same decision.

Programs are reinstalled rather than moved. Anything installed for all users is already there; anything installed for your user only has to be installed again, and that is the point, because the installer writes the new correct path. Browsers are easy — use the browser's own sync. Software with an activation count is worth deactivating in the old account first.

Attach the Microsoft account, then remove the old one

In the new account: Settings → Accounts → Your info → Sign in with a Microsoft account instead. Use the same address as before. The folder keeps its name, and your settings, licenses and OneDrive follow the account across.

Live in the new account for a week before touching the old one — long enough to discover what you forgot, while the old profile is still sitting there intact. When you are sure, delete the old account, and take the option to keep its files if you are offered it.

If you already renamed it: find your symptom

Plenty of people arrive here after the fact. Start with the reassuring part: your files are still on the disk. Renaming a folder does not delete anything. What is broken is a pointer, and pointers are fixable.

Everything is gone: the temporary profile

Empty desktop, default wallpaper, none of your files, usually a notice that you have been signed in with a temporary profile. Windows could not load your profile from the path it has recorded, so it made you a disposable one for this session. Do not settle in — anything you save in a temporary profile is discarded at sign-out.

Sign in with another administrator account and open Registry Editor at the profile list:

Look for your SID appearing twice: once normally, once with .bak on the end. That pairing is Windows having set your real profile aside and created a stand-in. To undo it:

• Rename the key without the suffix out of the way — add .temp to it.
• Rename the .bak key to remove the suffix, so your real profile becomes the live one.
• In that key, check ProfileImagePath points at a folder that actually exists, and correct it if not.
• Set its State value to 0, and RefCount to 0 if that value is present.
• Restart and sign in.

If there is only one key and no .bak, it is simpler: ProfileImagePath points at a folder that is not there. Make the two agree — correct the path or rename the folder back — and restart.

Temporary profiles have causes other than renaming. If you did not rename anything, our post on the User Profile Service failing to sign you in covers those.

You cannot sign in at all, and there is no second account

The awkward one. You need an administrator account to fix the registry and cannot reach one. Try Safe Mode first — hold Shift while clicking Restart, then Troubleshoot, Advanced options, Startup Settings, Restart. On some machines the built-in Administrator becomes available there, which is enough to correct the path.

If that fails, the honest position: recovering without a working administrator account is a repair-shop job. Pulling the files off the drive is straightforward; getting the original installation working again is what costs. Which is the argument for a second admin account, made in the least pleasant way possible — every PC that matters should have one, created before it is needed.

It works but things keep failing: the slow version

Priya's case, and the most common of the three. You are signed in, the desktop is fine, and a different thing is broken every few days.

The decision is honest arithmetic. Fixing it properly means hunting every stale path, with no list and no way to know when you are done. Route 1 takes an evening and ends with certainty, and we would take the evening. If you would rather chase it, start with HKEY_CURRENT_USER\Environment — Path, TEMP, TMP and OneDrive live there and account for a good share of the symptoms. Then sign out of OneDrive and set it up from scratch rather than repointing it.

Stopping it happening on the next PC

This is the genuinely new part, and the reason this page needed rewriting rather than tidying. Microsoft spent years telling people not to rename the folder while providing no way to choose a better one. That changed in 2026: Windows 11 setup can now ask you what the folder should be called. It arrived in an optional update at the end of May 2026 and went out broadly with the June 2026 security update, for Windows 11 24H2 and 25H2. On the same page where you name the device there is a field for the user folder name — type what you want and that is the folder. No email, no truncation, no five characters.

Two caveats. It is a gradual rollout, so it does not appear on every machine even with the update installed. And it exists only during setup — on a PC already running it does nothing. This is prevention, not a cure.

Read it as an admission, though. The company that told everybody not to rename the folder has moved the decision to the only moment where it is free — about as close as you get to confirmation that after-the-fact renaming was never the intended route.

If the field does not appear

Use the Route 1 trick at setup time. Windows 11 requires a Microsoft account during setup on ordinary consumer editions — the old bypasses have been closed off one by one — so you cannot avoid the generated folder for the first account.

What you can do is finish setup, immediately create a local account with the name you want, make it an administrator, sign into it once, attach your Microsoft account, and delete the first account. Nothing to migrate on a new PC, so it is ten minutes. Jake now does this on every machine before it leaves the shop, and it has removed a whole category of callback.

Windows 10: same mechanism, one extra thing to check

Everything above applies to Windows 10 without modification: same five-character rule, same registry location, same reasons not to rename, same migration route. Where the menus differ it is cosmetic — the right-click menu is the full one, so you will not need Show more options. Two differences are not cosmetic.

There is no prevention route. The setup-time folder name field is a Windows 11 feature. On Windows 10 the only option is the new account.

Check your support status before you spend an evening on this. Windows 10 reached end of support on 14 October 2025. It still runs, but without Extended Security Updates it is not receiving security fixes. Consumer ESU is still open and now runs to October 2027: free if you sync your settings with Windows Backup, free for 1,000 Microsoft Rewards points, or about $30 as a one-off.

That collides with the advice on this page. ESU enrollment requires a Microsoft account — a local account cannot enroll. So if you migrate to a new local account on Windows 10, attach your Microsoft account before you call the job done, or you have quietly traded security updates for a tidier folder name.

Questions people actually ask about this

Can I rename the C drive Users folder in Windows 11?

You can make Windows accept a new name, but you should not. The full path to your profile folder is written down by name in thousands of places, and renaming it leaves every one of them pointing at somewhere that no longer exists. You get a profile that works for a week and then fails in ways nobody connects to the cause.

Why is my user folder only five letters?

Because Windows builds it from the first five characters of your Microsoft account email, taking the part before the at sign. Somebody signing in as jonathan at example dot com gets a folder called jonat. It happens once, when the account is first created on that PC, and is never revisited.

Does changing my account name change the folder name?

No, and Microsoft describes that as working by design rather than as a fault. The account name, the display name on the sign-in screen and the profile folder name are three separate things, and changing either of the first two leaves the third exactly as it was.

What breaks if I rename the profile folder?

Anything that recorded the old path by name instead of asking Windows where your profile is. Microsoft names one example in its own documentation: the winget package manager stops working. Your per-user command path, temporary folders, OneDrive, per-user program installs and browser profiles also keep pointing at the old folder, failing quietly.

What is the safe way to change the user folder name?

Create a new account with the name you want, sign into it once so Windows builds a fresh profile folder, copy your files across, reinstall your per-user programs, then remove the old account. Make it a local account, which names the folder after the account rather than an email.

Is editing ProfileImagePath in the registry safe?

It is safe in the narrow sense that Windows reads the new value and loads your profile from the new location. It is not safe in the sense people mean, because it corrects one reference out of thousands and leaves the rest stale. Microsoft publishes this workaround and then says not to apply it on Windows 10 or later, which is warning enough.

I renamed the folder and now I get a temporary profile. What do I do?

Sign in with another administrator account and open the profile list in the registry. You will usually find two entries for your security identifier, one ending in dot bak. Move the one without the suffix aside, remove the suffix from the other, set its State value to zero, and restart.

I renamed the folder and cannot sign in at all. Can I recover?

Almost always, because your files are still on the disk under whatever name the folder now has. What is broken is the pointer, not the data. Sign in with a second administrator account, or start in Safe Mode, and either rename the folder back or correct the profile path to match.

Can I choose the folder name when setting up a new PC?

On a current Windows 11 installation, often yes. Since an update released in May 2026, setup can ask for a user folder name on the same page where you name the device. It is a gradual rollout, so it does not appear on every machine, and it exists only during setup, not afterwards.

Does anyone else ever see my profile folder name?

Almost never. It is not on the sign-in screen, not in the Start menu, not shown to people you share files with, and not part of your email address. It turns up in file paths and the occasional error message. For most people the only person it ever bothers is them.

Will a clean install fix the wrong folder name?

It will, and on a current Windows 11 build setup now asks what to call the folder. But reinstalling Windows to correct a folder name is a very large hammer for a small nail. If you were already planning a clean install, take the opportunity. Otherwise the new account route gets you there in an evening.

Does switching from a Microsoft account to a local account rename the folder?

No. Switching between the two changes how you sign in, not where your profile lives. The folder keeps the name it was given when the profile was created. It works in your favor in one direction only: create a local account first and attach a Microsoft account afterwards, and the folder is named after the local account.

How do I move my files to the new account without losing anything?

Sign into the new account once so its profile exists, then copy the old profile across as an administrator: Documents, Desktop, Downloads, Pictures, Videos and Music. Leave the hidden application data folder behind, because copying it turns a clean new profile into a copy of the old problem.

Is this different on Windows 10?

The mechanism is identical and every step here works the same way. Windows 10 setup never offered to name the folder, so there is no prevention route, only the new account one. And Windows 10 has been out of free support since October 2025, so check your extended security update enrollment before you spend an evening on this.

Does OneDrive get confused if I rename the folder?

Yes, and it is one of the loudest complaints after a rename. OneDrive stores the absolute path to its local folder, so afterwards it looks for a location that does not exist and says so repeatedly. Where folder backup was on, your Desktop and Documents were redirected into that path, which is how files appear to vanish.

What Priya's laptop says now

C:\Users\priya. What she wanted on the Tuesday, and what she got on the Saturday by a much longer road.

"What gets me," Jake said, "is that the slow way was always going to be the fast way. I just could not see it from Tuesday."

"Nobody can," Ethan said. "Twenty minutes against an evening is not a close call when you are looking at it. It only becomes one when you know the twenty minutes has a Saturday attached some of the time, and no way to know which you got until later."

"And now Microsoft just asks you at setup."

"Now they ask. Ten years of it, and the fix was a text box."

Take one thing away: the folder name is decided once, at account creation, and the only clean way to change it is to create the account again. Everything else is people trying to talk Windows out of a decision it wrote down thousands of times.

Revision note. Originally published 30 January 2017 and rewritten on 9 August 2026. The 2017 version gave the standard advice of its moment: enable the hidden built-in Administrator account, sign in there, and rename the folder. That was what everybody said then, and on a 2017 machine it was a far smaller thing to do than it is now. What changed underneath it is how much of a PC records that path by name — per-user installs, per-user command paths, packaged apps and cloud folder redirection have all become normal since, and the breakage Microsoft now warns about involves a tool that did not exist until 2020. So this rewrite leads with the recommendation not to rename at all, ranks the routes that work, and documents the registry route accurately for readers who will do it anyway. Newly added: Windows 11 setup began asking for the folder name in mid-2026, which makes this preventable at last, and the Windows 10 note about extended security updates needing a Microsoft account. If you are stuck part-way through a rename, or the field appeared during your setup and you can tell us what it accepted, write in through the contact page — the recovery cases get better every time a reader tells us exactly what their screen said, and we always read them.