After decades of user complaints, Microsoft finally gives Windows 11 installers a simple way to set the C:\Users folder name. The optional May 26, 2026 preview update KB5089573 for Windows 11 versions 24H2 and 25H2 introduces a setup page where you can specify the exact name for your user profile folder instead of relying on the automatic truncation of your Microsoft account email or the awkward default 'User' name fallback.

For anyone who has ever cringed at seeing their carefully chosen name mangled into a five‑character abbreviation on every command line, this update marks a small but significant quality‑of‑life improvement. The change applies exclusively to clean installations and out‑of‑box experiences (OOBE) on both Windows 11 24H2 (build 26100 and newer) and the upcoming 25H2 release. Existing installations are unaffected—once the profile folder is created, its name cannot be altered through official channels.

A twenty‑year‑old headache finally treated

The C:\Users folder name has been a thorn in the side of Windows users since the introduction of user‑centric profile directories in Windows Vista. Microsoft originally designed the naming logic to create a short, safe folder name derived from the user’s display name or the first five characters of a Microsoft account email. For a local account called “Jonathan Petersen,” the system would create “C:\Users\Jonat.” For Microsoft accounts, “[email protected]” became “C:\Users\alexa.” These truncated names often looked nothing like the intended username, causing confusion and even breaking path‑dependent applications that expected consistent folder names.

Power users developed elaborate workarounds: booting into Audit Mode, using unattended answer files (autounattend.xml), or temporarily setting up a local account and later converting it to a Microsoft account. None of these methods were straightforward for the average consumer. Microsoft acknowledged the pain point years ago but considered the automated logic a necessary compromise to avoid folder‑name conflicts and support legacy software that struggled with spaces or special characters.

KB5089573 finally addresses the root cause by giving the user direct control during device setup. Instead of the old, silent truncation, the OOBE now presents a dedicated page after the account creation step, asking: “What should we name your user folder?” A text field allows you to type any Windows‑valid folder name, and the installer immediately validates it for disallowed characters (such as \ / : * ? " < > |) and length restrictions. If the name is valid, the system creates the profile folder precisely as specified.

How the new user folder naming works

The new feature integrates seamlessly into the existing OOBE flow. After you choose your preferred language, connect to a network, and sign in with a Microsoft account or create a local account, a new screen appears with the title “Personalize your experience.” Below the standard privacy settings and customization toggles, a section titled “User folder” offers a text box pre‑filled with the system’s traditional suggestion. You can keep the suggested name or replace it entirely. A live validation check prevents you from continuing if the name contains forbidden characters or if the chosen folder already exists at C:\Users.

For example, if you want your profile folder to be “C:\Users\Jon,” you simply type “Jon” and click Next. If you prefer the full name “Jonathan,” that works too. Spaces are allowed (the installer will automatically strip leading/trailing spaces but keep internal ones), though Microsoft still recommends avoiding spaces for maximum compatibility with command‑line tools. Users setting up a device for work or school can enter their organization’s preferred naming convention—such as firstname.lastname—directly, removing the need for IT departments to script post‑deployment renaming hacks.

The update also includes a subtle safety valve: if you install Windows on a machine that already has a user profile folder with the same name (say, from a previous installation), the installer will alert you and refuse to proceed until you pick a different name. This prevents accidental data overwrites in dual‑boot scenarios. There is no “merge” option; you must delete or rename the existing folder manually via offline methods if you genuinely want to reuse the same name.

Technical underpinnings and upgrade paths

KB5089573 is an optional, non‑security preview update released on May 26, 2026. It bumps the OS build for Windows 11 24H2 to 26100.4xxx (the exact build number varies by cumulative update version) and applies equally to the 25H2 development branch. Since it is a preview update, it does not install automatically via Windows Update for most users; you must manually check for updates and select “Download and install” under the optional updates section. The full patch will be included in the June 2026 Patch Tuesday mandatory update, at which point the feature becomes a permanent part of those Windows versions.

The user‑folder naming capability is delivered through modifications to the OOBE components (sppsvc.dll, userprofile.dll) and the setup engine. Crucially, Microsoft has not exposed this feature retroactively for upgrades. If you update an existing Windows 11 machine from an older build to KB5089573, your C:\Users folder name remains whatever it was before. This update only affects the initial device‑setup experience. IT administrators can also pre‑configure the user‑folder name via an updated unattend.xml schema, which now supports a element within the section.

Enterprise and education editions gain an additional Group Policy setting (under Computer Configuration \ Administrative Templates \ System \ User Profiles) to enforce a specific naming pattern or to disable the manual input, forcing the automatic truncation logic for consistency across fleet deployments.

Why this matters for everyday users and developers

Beyond mere aesthetics, the user‑folder name has practical implications. Many command‑line applications, scripts, and development tools resolve home‑directory paths using %USERPROFILE% or ~ in PowerShell, which maps directly to C:\Users\\. A short, cryptic folder name like “C:\Users\a12b3” makes reading command‑line output unnecessarily difficult. Developers who rely on consistent folder structures across machines—for example, when using package managers like npm or setting up Python virtual environments—often run into bugs because their scripts reference a hard‑coded username. With KB5089573, they can ensure the profile folder matches their expected naming convention right from the start.

Gamers and modders also benefit. Many game launchers and modding tools store configuration files under %APPDATA%, which resides inside the user profile hierarchy. While most modern applications query the system for the correct path dynamically, some legacy games and fan‑made tools still assume a folder tree starting with “C:\Users\\.” A mismatch can lead to save‑file corruption or mod‑loading failures. Choosing a predictable name eliminates one more variable from troubleshooting.

Potential pitfalls and limitations

Despite the warm reception, early testers have flagged a few caveats. The validation logic does not warn against using system‑reserved names like “Administrator,” “Guest,” or “Public.” While these names are technically allowed in the text box, creating a profile folder with such a name could clash with built‑in system‑wide folders and cause unpredictable behavior. Microsoft’s documentation recommends sticking to alphanumeric characters and underscores, but the UI itself does not enforce this soft guideline.

Another limitation is the 255‑character path limitation that still affects many Windows programs. Since the profile folder sits deep in the filesystem, choosing a very long name (e.g., “Jonathan Peterson‑Richardson III”) could push total paths for some deeply nested application data over the MAX_PATH limit. The installer does not check for potential path‑length issues; it only validates the immediate folder name. Users who habitually organize files with detailed folder structures should remain mindful of this constraint.

There is also no “pick a different drive” option during this step. The user folder is always created on the system drive (typically C:), even if you specify a different volume during setup. Users wanting to store their entire profile on a separate disk will still need to use symbolic links or folder‑redirection policies after installation.

Community reaction and early feedback

Windows enthusiasts have celebrated the change on forums and social media, calling it “long overdue” and “the best OOBE improvement in a decade.” Beta testers in the Windows Insider Program report that the feature works as advertised, with one Reddit user noting: “Finally, I can have ‘C:\Users\Tom’ instead of ‘C:\Users\tomas_000’ added from some ancient GameSpy account.” Others caution that the new step adds yet another screen to the already lengthy OOBE process, though the optional nature of the update and the ability to skip customization make this a minor complaint.

IT professionals have expressed cautious optimism. The ability to set consistent folder names via unattend files simplifies deployment images for large organizations, but some worry about support calls from users who accidentally type a name they later regret. Because renaming the user folder after setup can break applications and system settings, Microsoft’s official stance remains that users should not attempt to rename the folder manually. The company has no plans to add a post‑setup rename utility, which means the choice made during OOBE is effectively permanent for the life of that installation.

How to get KB5089573 and use the feature

To take advantage of the new naming option, you must download and install KB5089573 from Windows Update before initiating a clean installation. The update itself does not trigger a re‑install; you need to create a bootable USB drive with the updated Windows 11 image (using the Media Creation Tool or an ISO that already includes the May 2026 cumulative update) or run a reset from within Windows after applying the patch. Once you boot from the installation media, the new user‑folder screen will appear automatically for all editions except Windows 11 Home in S mode (which retains the old logic for security and simplicity).

Alternatively, you can apply the update to an existing Windows 11 24H2 machine, then use the “Reset this PC” feature with the “Remove everything” option to trigger a fresh OOBE experience that includes the new naming screen. This method is particularly useful for users who want to change their folder name without performing a manual clean install.

Microsoft’s official support article (KB5089573) will be updated with more detailed guidance once the update transitions from optional preview to mandatory release in June 2026.

Looking ahead: a more personal Windows

KB5089573 is part of a broader trend in Windows 11’s evolution toward greater user agency. Recent updates have similarly reintroduced classic customization options, such as the ability to move the taskbar to the top of the screen and to disable Start menu recommendations entirely. While the user‑folder naming may seem like a minor tweak, it underscores Microsoft’s renewed attention to the polish and personalization demands of its enthusiast base.

For millions of users who have lived with abbreviated, generic folder names for years, this update removes one of the last persistent annoyances of setting up a new PC. The days of “C:\Users\user” or “C:\Users\email5” are numbered—at least for those setting up a fresh installation. As Windows 11 continues to mature, such refinements confirm that even enormous operating systems can still learn to sweat the small stuff.