navywolf96
New Member
- Messages
- 1
- Reaction score
- 0
How would I change the default theme file in ntlite? and where would I place this custom theme file on the iso?
Changing the default Windows theme file for every user creation
- Thread starter navywolf96
- Start date
Hellbovine
Well-Known Member
- Messages
- 1,216
- Reaction score
- 776
This question comes up often, so I put it on my to-do list to write a thorough guide at a later date when I have more time. Until then, this reply serves as a rough draft that explains the mechanics behind the primary methods for handling themes and related cosmetics.
The first thing to understand though, is that themes are not woven into the operating system, but are installed at user-creation right before the desktop appears. That is a problem, because when a theme is installed it will overwrite any conflicting settings a user has made to their image.
REGISTRY METHOD
COMPONENT METHOD
THEME METHOD
POST-INSTALL METHOD
RESOURCE LOCATIONS
The first thing to understand though, is that themes are not woven into the operating system, but are installed at user-creation right before the desktop appears. That is a problem, because when a theme is installed it will overwrite any conflicting settings a user has made to their image.
REGISTRY METHOD
The most robust method is to not use themes. Instead, disable the installation of the Aero theme, which then puts Windows into "Custom" theme mode, allowing a user to modify settings however they want and without them being overwritten anymore. I have explained these details in many posts, which can be found by searching the forum (link1, link2). A user is then free to modify cosmetic settings in NTLite or through the integration of registry files into an image, without interference from the Aero theme.
There are many settings that can be customized, and it is not practical to list them all, instead it is more efficient to download a registry compare tool, such as RegistryChangesView by NirSoft, and then toggle options through the Windows Settings page and Control Panel, while taking snapshots to obtain the registry keys needed, for integrating into an image. I already have hundreds of customizations available in a downloadable registry file from this guide (link3), which can be used as-is, modified, or just serve as a learning example.
The registry method is superior to all others, since it addresses the root of the problem and produces no quirks or bugs, making it so that theme customizations apply to all users out of the box, while still maintaining the integrity of the operating system.
There are many settings that can be customized, and it is not practical to list them all, instead it is more efficient to download a registry compare tool, such as RegistryChangesView by NirSoft, and then toggle options through the Windows Settings page and Control Panel, while taking snapshots to obtain the registry keys needed, for integrating into an image. I already have hundreds of customizations available in a downloadable registry file from this guide (link3), which can be used as-is, modified, or just serve as a learning example.
The registry method is superior to all others, since it addresses the root of the problem and produces no quirks or bugs, making it so that theme customizations apply to all users out of the box, while still maintaining the integrity of the operating system.
COMPONENT METHOD
Users can uninstall themes and wallpapers from an image with NTLite through the components menu, which achieves the same concept as the registry method, but is a hacky approach that targets symptoms and affects the integrity of the image. It's a common method though, because many users want to reclaim the disk space taken up by these files, so they choose this method for the deletion aspect.
If a user only wants to change the wallpaper, they can skip the uninstalls, and instead mount an image in NTLite then replace the file at C:\Windows\Web\Wallpaper\Windows\img0.jpg before processing, but be sure to use the img0.jpg filename and extension or it will not work.
Note: System file checker will attempt to undo this method if it is ran, unless WinSxS is purged or those files are modified too. On that same note, because the theme and wallpaper files are "protected" they require TrustedInstaller permissions (TI) to modify, and one option to gain those permissions is to download the PowerRun tool by Sordum and run the NTLite program through it, then mount and replace files.
If a user only wants to change the wallpaper, they can skip the uninstalls, and instead mount an image in NTLite then replace the file at C:\Windows\Web\Wallpaper\Windows\img0.jpg before processing, but be sure to use the img0.jpg filename and extension or it will not work.
Note: System file checker will attempt to undo this method if it is ran, unless WinSxS is purged or those files are modified too. On that same note, because the theme and wallpaper files are "protected" they require TrustedInstaller permissions (TI) to modify, and one option to gain those permissions is to download the PowerRun tool by Sordum and run the NTLite program through it, then mount and replace files.
THEME METHOD
Another approach is to modify the existing Aero theme, which is not documented by Microsoft, so users have to figure it out on their own. Once the theme is finalized, use NTLite to mount an image and replace the aero.theme file at C:\Windows\Resources\Themes before processing.
Note: System file checker will attempt to undo this method if it is ran, unless WinSxS is purged or those files are modified too. On that same note, because the theme and wallpaper files are "protected" they require TrustedInstaller permissions (TI) to modify, and one option to gain those permissions is to download the PowerRun tool by Sordum and run the NTLite program through it, then mount and replace files.
Note: System file checker will attempt to undo this method if it is ran, unless WinSxS is purged or those files are modified too. On that same note, because the theme and wallpaper files are "protected" they require TrustedInstaller permissions (TI) to modify, and one option to gain those permissions is to download the PowerRun tool by Sordum and run the NTLite program through it, then mount and replace files.
POST-INSTALL METHOD
The final approach is for a user to reapply their customizations after the default Aero theme is finished installing, which can be accomplished using the post-setup (user) feature of NTLite with a PowerShell script, registry file, command, or other similar concept.
RESOURCE LOCATIONS
Below are some relevant filepaths for themes and wallpapers.
C:\Windows\Resources\Themes
C:\Windows\Web
C:\Windows\Web\4K\Wallpaper\Windows
C:\Windows\Web\Screen
C:\Windows\Web\Wallpaper\Theme1
C:\Windows\Web\Wallpaper\Theme2
C:\Windows\Web\Wallpaper\Windows
Note: The Theme1 filepath appears as a yellow folder that is labeled as Windows 10, but that is not the actual path the wallpaper files use. The Theme2 filepath has the same quirk and appears as a yellow folder that is labeled as Flowers.
C:\Windows\Resources\Themes
C:\Windows\Web
C:\Windows\Web\4K\Wallpaper\Windows
C:\Windows\Web\Screen
C:\Windows\Web\Wallpaper\Theme1
C:\Windows\Web\Wallpaper\Theme2
C:\Windows\Web\Wallpaper\Windows
Note: The Theme1 filepath appears as a yellow folder that is labeled as Windows 10, but that is not the actual path the wallpaper files use. The Theme2 filepath has the same quirk and appears as a yellow folder that is labeled as Flowers.
Last edited: