Windows 11 Now Lets You Set a Custom Profile Folder Name During Clean Installation

Microsoft has quietly introduced a long‑requested feature that ends the decades‑old habit of auto‑generated, truncated user profile folders. Starting with the optional update KB5089573, released on May 26, 2026, Windows 11 version 24H2 and the upcoming 25H2 allow you to specify the name of the C:\Users folder during a fresh installation. The change appears in the out‑of‑box experience (OOBE) and finally gives users direct control over a path that has stubbornly resisted customization since the NT era.

For years, setting up a new Windows PC meant accepting a folder name you didn’t choose. If you signed in with a Microsoft account, the system grabbed the first five characters of your email address. Jonathan became Jonat, Elizabeth became Eliza, and anyone with a name shorter than five letters got the whole thing, but that was a gamble. Local accounts fared slightly better—using the full display name—but special characters and spaces often led to awkward folder paths. The result was a landscape of cryptic C:\Users folders that annoyed power users, confused newcomers, and occasionally broke applications that couldn’t handle non‑standard characters.

What’s Changing

The new option appears during the account creation step of Windows Setup. After selecting your keyboard layout and sign‑in method, you choose a username. Whether you go with a Microsoft account or a local account, a new field or an edit button lets you type a custom name for the profile folder. The interface warns against using reserved device names (like CON, PRN, AUX) and ensures the name doesn’t conflict with existing folders. Once you confirm, Windows creates C:\Users\YourChosenName and all your subsequent files, settings, and app data will live there.

The official KB article accompanying KB5089573 describes the feature as “a quality‑of‑life improvement for users who prefer a clean, predictable file system structure.” It’s available on Windows 11 Home and Pro editions, though some enterprise SKUs may disable the prompt via group policy. The update is cumulative and optional, meaning you’ll need to manually check for it in Windows Update or download it from the Microsoft Update Catalog. Media created with the latest Windows Installation Media Tool automatically slipstreams the update if generated after May 26, 2026.

A Brief History of the C:\Users Folder

To appreciate this change, it helps to understand why the folder name became such a pain point. In Windows XP, user profiles lived under C:\Documents and Settings, and the folder name was the full account name. Users could rename accounts freely, but the folder name often stayed the same—leading to a disjointed experience. Windows Vista moved profiles to C:\Users and introduced the concept of a “profile image path” in the registry. Still, renaming was unsupported and risky.

With Windows 8, Microsoft pushed Microsoft accounts for sign‑in, and the 5‑character truncation became standard. The official explanation was to ensure compatibility with legacy software that couldn’t handle paths longer than 260 characters. The real reason, many suspected, was simplicity in backend systems that tied user identity to a short string. Whatever the motive, users felt railroaded. Forums filled with complaints: “Why is my name cut off?” “How do I change the folder name?” Workarounds emerged—creating a local account first, then converting to a Microsoft account after setup; using Sysprep with an answer file; or even hacking the SAM registry hive. Each method carried risks and often failed with modern UWP apps that expect a specific SID-to-path mapping.

How the New Feature Works

When you boot from a USB drive or ISO that includes KB5089573, the OOBE flow is mostly unchanged until you hit the “Create your account” screen. Here’s what you’ll see:

1. Sign‑in method: Choose Microsoft account or local account.
2. Username: Type the display name you want shown on the lock screen and Start menu.
3. Folder name (new): If you picked a Microsoft account, the system auto‑suggests a short form of your email. Below or next to that field, a “Change folder name” hyperlink appears. Click it, and you get a text box. For local accounts, the folder name field is shown directly, pre‑filled with the username, but editable.

The text box enforces typical file system rules: maximum 20 characters (to maintain short path lengths), no trailing spaces, no characters from this list: \/:*?"<>|. The following reserved names are also blocked:

• CON, PRN, AUX, NUL
• COM1 through COM9
• LPT1 through LPT9

Once you submit, setup continues as usual, and the chosen folder is created. Apps that later install per‑user data will follow that path.

Why It Matters

A custom profile folder name isn’t just about aesthetics. Consider a developer named Patricia who always sets up her machine with the folder name “pat.” She uses command‑line tools that reference %USERPROFILE% frequently, and a short, predictable path reduces typos. A gamer named Alexander might want “Alex” instead of “Alexa” to maintain consistent Steam cloud syncs across devices. In enterprise environments, IT admins can standardize folder names to match employee IDs (e.g., “emp12345”) for easier scripting and log management.

Moreover, the ability to avoid spaces and special characters nips a long‑standing source of bugs in the bud. Some legacy installers and scripts stumble over paths like “C:\Users\John Smith” because the space isn’t escaped properly. Now, users can choose a clean folder name from the start.

Limitations and Caveats

The feature is strictly limited to clean installations. If you upgrade from an older Windows 10 or Windows 11 build, or if you reset your PC with the “Keep my files” option, the existing C:\Users folder structure remains untouched. Microsoft has no plans to backport the option to upgrades or add a post‑setup rename utility. The official stance remains: rename a profile folder at your own risk, and only by creating a new account and copying data.

Additionally, the feature is tied to KB5089573. Without that update, even the latest 24H2 build will fall back to the old behavior. Users installing from an ISO downloaded before May 26, 2026, will see the old auto‑generated names. To check, look for the update in Windows Update or verify that your installation media version is 10.0.26100.xxxx or later with the appropriate servicing stack update.

Community Response

Although Microsoft hasn’t made a big splash about this change, early reports on tech forums have been overwhelmingly positive. Veteran Windows enthusiasts who have been using the “local account workaround” for years are happy to retire it. “I’ve been waiting for this since Windows 8,” wrote one redditor in a now‑popular thread. Others caution that the option is easy to miss—buried behind a tiny hyperlink—and hope Microsoft makes it more prominent in future builds.

One practical concern: if a user creates a Microsoft account with a custom folder name, then later resets the PC and chooses “Keep my files,” Windows might recreate the old auto‑generated folder, leading to confusion. Microsoft’s documentation advises against renaming folders post‑setup, so this edge case remains a user‑education challenge.

For Enterprise and Deployment

System administrators who provision dozens of machines will find the new option a boon. Previously, scripting a clean install with a specific profile name required an unattend.xml answer file that specified the parameter. That approach still works, but KB5089573 now also exposes the option through the GUI, allowing for manual overrides during ad‑hoc deployments. Group policy can disable the editable field if organizations prefer to enforce a naming convention via the answer file.

Table 1 summarizes the scenarios where the new option appears.

How to Get It Now

If you want to test the feature before it reaches the general monthly patch cycle, join the Windows Insider Program. Dev and Beta channel builds already include KB5089573, though they come with the usual preview‑build caveats. For a safe test environment, use a virtual machine. Download the latest Windows 11 Insider ISO from Microsoft’s website, boot from it, and proceed as described. Once you have a machine running the updated version, you can also create custom installation media by using the Media Creation Tool and then applying the KB5089573 MSU file offline.

Production users should wait for the optional update to appear in Windows Update. After installing it on an existing system, you won’t see the option unless you perform a clean install. To prepare, you can use the built‑in media creation tool to make a USB stick that already includes the update, or you can slipstream the update manually with tools like DISM.

The Bigger Picture

This update is one of several under‑the‑hood improvements in 24H2 that polish the Windows experience. Combined with recent tweaks—like a redesigned Bluetooth pairing flow and the optional removal of Bing search highlights—Microsoft seems to be paying attention to long‑standing user feedback. The profile folder naming option may not make headlines like Copilot+ PC features, but for the millions who interact with the file system daily, it’s a tangible win.

Looking ahead, there’s no indication that Microsoft will expose this option for existing accounts or during feature updates. The safe bet is to plan your next clean install around this update if a custom folder name matters to you. As Windows 10 nears its end of support, the timing couldn’t be better for those migrating to Windows 11 on new hardware.

In the end, the ability to name your own C:\Users folder is a small concession that rights a design decision many considered arrogant. It acknowledges that users—not operating systems—should decide how their personal corner of the disk is labeled. For that, Windows 11 just became a little more humane.