Customize the Default User Profile by Using CopyProfile
You can use the
CopyProfile setting to customize a user profile and then copy that profile to the default user profile. Windows uses the default user profile as a template to assign a profile to each new user. By customizing the default user profile, you can configure settings for all user accounts that are created on the computer. By using
CopyProfile, you can customize installed applications, drivers, desktop backgrounds, internet explorer settings, and other configurations. Note that some settings are not preserved by using
Using CopyProfile for Start menu customization isn't supported. Here are the ways to manage custom Start layouts in Windows 10:
- OEMs can use layoutmodification.xml. See Customize the Start layout for more information.
- IT pros can use the following resources learn about managing the Windows 10 Start Menu:
Create an answer file with the CopyProfile setting
In Windows SIM, create an answer file with
amd64_Microsoft-Windows-Shell-Setup_neutral\ added to Pass 4 - Specialize, and set
True. Save this answer file as
copyprofile.xml. You'll use this answer file when you run Sysprep.
Configure Default User Profile Settings
Configure user settings in audit mode and then generalize the Windows installation by using an answer file with
CopyProfile. If you install Windows with another answer file, make sure that answer file doesn't have
CopyProfile or any settings that create additional user accounts.
Install Windows on a reference computer and boot in audit mode. For more information, see Boot Windows to Audit Mode or OOBE.
Don't use a domain account, because the
CopyProfilesetting runs after the computer is removed from the domain when you run Sysprep. As a result, you'll lose any settings that you configured in a domain. If you change the default user profile and then join the computer to a domain, the customizations that you made to the default user profile will appear on new domain accounts.
Customize the built-in administrator account by installing applications, desktop shortcuts, and other settings.
There is a limit to the number of provisioned Windows Runtime-based apps that you can install. However you can create scripts to install additional non-provisioned apps. For more information, see Sideload Apps with DISM.
After your customizations are completed, insert the media that contains the CopyProfile answer file in the reference computer. For example, you can copy the answer file to a USB drive.
On the reference computer, open an elevated command prompt, and then type this command:
C:\Windows\System32\Sysprep\Sysprep /generalize /oobe /shutdown /unattend:F:\CopyProfile.xml
where F is the letter of the USB flash drive or other removable media. The Sysprep tool removes computer-specific information from the image, while preserving the user profile settings that you configured. For more information, see Sysprep (Generalize) a Windows installation.
After the image is generalized, the computer shuts down, capture the image by booting to Windows PE and then capture the Windows installation by using DISM. For more information, see WinPE: Create USB Bootable drive and Capture Images of Hard Disk Partitions Using DISM. After the image is captured, you can deploy it to a destination computer by using DISM. For more information, see Apply Images Using DISM.
Test the User Profile Customizations
After the customized image is deployed to a destination computer, you can test the user profile customizations. You can go through Out-Of-Box Experience (OOBE) to test the end user experience, or you can test the user customizations in audit mode.
Apps based on the Windows Runtime won't start in audit mode because audit mode uses the built-in administrator account. To run Windows Runtime-based apps you must modify a registry key before you can validate your Windows installation in audit mode.
To test the user profile customizations after OOBE
Install Windows to a test computer.
After Windows is installed, go through OOBE and specify the computer name, user account name, and other items. After OOBE is complete, the Windows start screen appears.
Log onto the computer with the user account specified during OOBE and verify that your apps and customizations appear.
To test the user profile customizations in audit mode
Boot to audit mode by using an answer file or by pressing Ctrl+Shift+F3 when OOBE starts. For more information, see Boot Windows to Audit Mode or OOBE.
Verify that your customizations work as intended. To test Windows Runtime-based apps, modify the following registry key:
From an elevated command prompt, run Regedit.exe.
Browse to the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken registry key.
Click FilterAdministrationToken, and then type 1 as the value data.
Log off from the computer.
Log back on to the computer, and start the Windows Runtime-based apps to verify that your customizations work as intended.
After you complete validation of your Windows Runtime-based apps, reset the FilterAdministrationToken registry key to 0.
If the user profile settings aren't successfully copied:
Make sure that you set the
CopyProfilesetting only once during the deployment process.
When you customize user settings, only use only the built-in administrator account on the computer to avoid accidentally copying settings from the wrong profile.
Confirm that you didn't use a domain account.
Verify that there are no additional user accounts other than the built-in administrator account that you configured:
Click Start, and then type Control Panel.
Click Control Panel, and then click Add or remove user accounts.
Select any additional user account other than the built-in administrator account that you configured, and then delete it.
Delete all other user accounts on the computer before you customize the built-in administrator account.
Make sure that non-provisioned Windows Runtime-based apps that are stored in the tile layout are installed within two hours of user logon to preserve the tile layout on the Start screen, when apps are registered after the new user first logs on.
Some settings can be configured only by using the
CopyProfileunattend setting, and other settings can be configured by using Group Policy.
Use Group Policy to configure settings that are reset by the new user logon process. You can also create scripts to define these user settings.
CopyProfileunattend setting instead. For more information, see Unattended Windows Setup Reference.