Windows 11 is finally introducing an official way to choose the name of the default user profile folder during a clean installation. The feature first appeared in Insider testing in October 2025 and reached retail Windows 11 versions 24H2 and 25H2 through the May 26, 2026 optional preview update. However, availability can still vary because Microsoft is enabling the redesigned setup experience through a gradual rollout.
What Changed in Windows Setup
Windows traditionally creates a profile directory inside C:\Users when the first account is configured. When a Microsoft account is used, the generated folder name may be based on part of the account's email address rather than the display name selected by the user.
The new setup option allows a custom folder name to be entered before the first profile is created. In the current graphical implementation, the option appears on the Device Name page during the out-of-box setup experience.
The feature controls the physical profile folder name created during initial setup. It is not simply a change to the account display name shown in Settings or on the sign-in screen.
Is the Feature Generally Available?
The feature is no longer limited exclusively to the Windows Insider Dev Channel. Microsoft documented it for retail Windows 11 versions 24H2 and 25H2 in the optional cumulative preview update released on May 26, 2026.
That update, KB5089573, advanced Windows 11 to builds 26100.8524 and 26200.8524. Its Windows Setup notes state that users can choose a custom user-folder name on the Device Name page during setup.
The changes from that preview release were subsequently incorporated into the June 9, 2026 security update for supported Windows 11 24H2 and 25H2 installations. Installing the latest cumulative update therefore provides the necessary operating-system components, but it does not guarantee that every device will immediately receive the visible option.
| Release | Date | Status | Relevant Experience |
|---|---|---|---|
| Insider Dev Build 26220.6772 | October 6, 2025 | Insider testing | Command-line method during Microsoft account setup |
| Release Preview Builds 26100.7015 and 26200.7015 | October 21, 2025 | Release Preview testing | Command-line method expanded to a broader test channel |
| KB5089573 | May 26, 2026 | Optional retail preview | Graphical option on the Device Name page |
| KB5094126 | June 9, 2026 | Retail security update | Includes changes from the preceding preview update |
Microsoft's official descriptions can be reviewed in the original Insider announcement and the KB5089573 release notes.
How the Custom Folder Option Works
During a qualifying clean installation, Windows Setup can display a field for selecting the user-folder name. The value is applied when the first user profile is created after Microsoft account authentication.
If the option is skipped, unavailable, or supplied with an invalid value, setup continues using the automatically generated folder name. The selected name must comply with normal Windows file and directory naming restrictions.
- The option is intended for use during the initial Windows setup process.
- It affects the profile path beneath C:\Users.
- It does not change the email address connected to the Microsoft account.
- It does not provide a supported one-click method for renaming an existing profile folder.
- Reserved names and prohibited filename characters cannot be used.
The earlier Insider implementation required opening Command Prompt with Shift + F10 and running SetDefaultUserFolder.cmd. The retail implementation has been redesigned as part of the graphical setup interface, so the older command should not be treated as the primary method on current installations.
Why Some Updated PCs Do Not Show It
Microsoft commonly distributes Windows features through controlled feature rollout technology. Under this model, the necessary files may already be installed while the visible interface remains disabled until Microsoft activates it for a particular device group.
This explains why two computers running the same Windows build can show different setup screens. Hardware model, region, setup-image age, account configuration, update state, and rollout assignment may all affect what appears during installation.
Not seeing the field does not necessarily mean the update failed to install. It may mean that the feature has not yet been activated for that installation environment.
Checking for updates may bring the system to the required build, but reinstalling the same update repeatedly is unlikely to force a server-controlled feature assignment. Reports from individual PCs should therefore not be treated as proof that the feature is universally available or completely absent.
Is It Included in Windows 11 ISO Files?
Microsoft does not normally rebuild its public Windows installation media every time an optional cumulative update is released. Consumer ISO files and Media Creation Tool images may therefore contain an earlier base build even when a newer cumulative update is available through Windows Update.
A freshly downloaded ISO can receive current updates during setup through Dynamic Update, or after installation through Windows Update. This does not always mean that the initial offline setup environment will expose every newly released interface before those updates and feature configurations are applied.
| Installation Method | Expected Availability | Main Limitation |
|---|---|---|
| Older ISO used completely offline | Least likely to show the new option | Setup components may predate the feature |
| Older ISO with internet-connected Dynamic Update | More likely | Rollout activation can still vary |
| Updated installation media with matching setup packages | Potentially available | Requires more than servicing only the main Windows image |
| Future refreshed Microsoft ISO | Most consistent once broadly deployed | Microsoft does not publish a fixed refresh schedule for every feature |
The presence of build files in an ISO and the availability of a controlled Windows feature are related but separate questions. A newer ISO can improve the likelihood of receiving the option, but it cannot by itself guarantee that Microsoft has enabled the interface for every user.
Why Slipstreaming the Update May Not Be Enough
Adding a cumulative update only to install.wim may update the Windows image that is applied to the drive without fully updating the setup environment that runs before installation. Windows media can contain several images and supporting packages, including boot.wim, setup files, servicing-stack components, and Dynamic Update packages.
A setup-related feature may depend on updated components outside the primary edition image. The update package may also consist of multiple MSU files that must be applied in the correct order and to the correct image indexes.
- The installation image and setup image may require separate servicing.
- Architecture-specific packages must match the ISO.
- Servicing-stack prerequisites must be included where required.
- Setup Dynamic Update and Safe OS Dynamic Update packages may be necessary.
- A staged feature flag may remain disabled even after successful image servicing.
Microsoft provides separate guidance for applying current cumulative and Dynamic Update packages to Windows installation media. Third-party media tools can simplify parts of the process, but a completed integration message does not confirm that every OOBE component or rollout configuration has been updated.
Can It Rename an Existing User Folder?
The new feature is designed to choose a folder name before the profile is created. It does not add a supported Settings option for changing the path of an existing account from one folder name to another.
Renaming an established folder manually can break profile registry paths, application settings, scheduled tasks, cloud synchronization, permissions, development tools, and software containing absolute paths. Changing the account's visible name also does not rename the corresponding directory.
The more reliable approach on an existing installation is generally to create a new account with the desired profile path, move personal files carefully, verify application access, and remove the old account only after confirming that nothing important remains. Even this approach may require additional work for applications that store settings per user.
Manual profile-folder renaming should be approached as a system migration task rather than a cosmetic filename change.
Practical Options for a New Installation
Someone preparing to rebuild a PC can first create current Windows installation media and allow setup to download updates when prompted. During OOBE, the Device Name page should be checked carefully for the custom user-folder field before proceeding to account creation.
If the option does not appear, the safest choices are to postpone the clean installation, accept the automatically generated folder name, or use an established account-deployment method appropriate for the edition and environment. Unsupported scripts obtained from unofficial sources may stop working as Microsoft changes OOBE behavior.
- Use Windows 11 version 24H2 or 25H2 with current cumulative updates.
- Keep the installation connected to the internet if Dynamic Update is acceptable.
- Look for the folder-name field before the first user profile is created.
- Choose a simple name that avoids spaces, reserved words, and special characters.
- Do not assume an updated ISO automatically bypasses staged rollout controls.
Users managing multiple machines may prefer unattended deployment tools, provisioning packages, or supported enterprise imaging workflows. Those methods provide more predictable account creation than relying on a consumer-facing feature that is still being progressively enabled.
An Objective View
The custom user-folder feature has moved beyond its original Insider-only experiment and is now part of Microsoft's retail Windows 11 update path. The main source of confusion is that a retail release does not always mean immediate universal availability.
The May 26 preview update formally introduced the graphical setup option, and the June security update carried the preceding improvements into the normal cumulative servicing channel. Nevertheless, gradual rollout controls and older installation media can prevent the option from appearing on an otherwise fully updated PC.
For users planning a clean installation, the feature can now reasonably be expected on eligible systems, but it should not yet be treated as guaranteed on every setup attempt. Waiting for broader deployment or a refreshed official ISO may provide a more predictable experience than repeatedly rebuilding custom media.
Tags
Windows 11 user folder name, Windows 11 custom profile folder, Windows OOBE, KB5089573, KB5094126, Windows 11 ISO, Windows setup update, C Users folder, Windows gradual rollout
Post a Comment