Recommended Posts

Hi,

According to the quote below, there is no other way than the "uxtheme hack" to install third-party (non-microsoft) visual styles. It clearly states, "By default, uxtheme.dll is locked, so third party (i.e. non-Microsoft) visual styles cannot be used. Fortunately, it is easy to unlock uxtheme.dll to allow the use of non-Microsoft visual styles."

The two questions that I require answers for are:

1. First, is there a possibility of a third party signed windows visual style to be directly accepted by windows without the hack in both Vista and XP?

2. How do we digitally crypto sign a custom built windows visual styles file (*.msstyles) and which tool (like SignTool.exe, SignCode.exe, sn.exe .. etc) do we use for this purpose?

Any help would be really appreciated.

Thanks & Regards,

Ram

Basic Questions

Q: What is uxtheme?

A: Uxtheme.dll is the file in Windows XP that controls the theming engine. By default, uxtheme.dll is locked, so third party (i.e. non-Microsoft) visual styles cannot be used. Fortunately, it is easy to unlock uxtheme.dll to allow the use of non-Microsoft visual styles.

Q: Where can I find uxtheme.dll files?

A: Uxtheme Repository: http://www.withinwindows.com/uxtheme-patches/

Q: How do I use uxtheme.dll?

A: Luckily, hacked uxtheme.dll files are readily available. One need only replace the default, locked uxtheme.dll with the hacked, unlocked version.

Q: How do I replace uxtheme.dll?

A: This is very easy to do.

1. Download the unlocked uxtheme.dll. Extract the file to the desktop. Here is a version for sp2 2180 English: https://www.neowin.net/forum/index.php?act=...t&id=122794

More are here: http://www.extended64.com/blogs/rafael/

2. Download Replacer. Extract Replacer to the desktop (create a folder called Replacer and extract the contents of the compressed file).

3. Run replacer.cmd. A black command prompt window should appear.

4. Browse to C:\Windows\system32 and find uxtheme.dll. Drag this file into the command prompt window. Press enter.

5. Drag in the unlocked uxtheme.dll from the desktop into the command prompt window. Press enter.

6. Confirm the replacement and wait for Replacer to finish. Press any key when prompted.

7. Reboot.

Q: How do I use visual styles (msstyles) now?

A: This, again, is very simple.

1. First, download a visual style. The Completed Visual Styles Section and Deviantart are two good places.

2. Extract the visual style to a folder with the same name in the following directory: C:\Windows\Resources\Themes. For example, if the msstyles file is xyz.msstyles, create a folder called ?xyz? in C:\Windows\Resources\Themes and extract xyz.msstyles to that folder.

3. To load the visual style, go to the Display Properties > Appearance > Windows and Buttons, and find the visual style. Do not look for the visual style in the Themes tab. You can also double-click the msstyles file.

Q: What is the difference between a theme and a visual style?

A: The terms ?theme? and ?visual style? are often thrown around carelessly and used interchangeably, which adds to the confusion, but the distinction is clear.

A visual style (*.msstyles) is the file that skins the windows, taskbar, start menu, and other elements of the Windows appearance. Visual styles are loaded in the Appearance tab of the display properties dialog.

A theme (*.theme) is a visual style with saved settings, wallpapers, icons, and so on. Themes are loaded in the Theme tab of the display properties dialog.

When people say themes, they usually mean visual styles.

Q: What is a shellstyle and how do I install it?

A: Shellstyle.dll is a file often bundled with the visual style that skins the common tasks pane (and other panes, e.g. the add/remove panel). No installation is necessary. Simply unzip the visual style to the appropriate directory as mentioned above and make sure the shell folder is in the visual style folder along with the msstyTroubleshootingshooting

Q: My uxtheme did not patch! What do I do?

A: Now hold on there. How do you know it failed? The easiest way to check to see if uxtheme.dll was patched is to simply double-click the msstyles file of a third party theme. If double-clicking loads the display properties dialog with the correct visual style, then the patching process was successful. If not, re-patching is necessary. You can try to re-patch in safe mode and make sure the themes service is set to automatic. To make sure it is set to automatic, go to Run > services.msc > and set Themes service to automatic.

Also, you should do a search for uxtheme.dll and delete all instances of the file NOT in C:\Windows\system32. Extra uxtheme.dll files can conflict and cause problems. Deleting them will solve almost every issue regarding patching.

Q: Uxtheme was patched successfully, but visual styles do not appear in the Appearance tab dropdown list. What do I do?

A: This is a common problem, but one that deserves more attention than it is currently given. The problem is caused by a misnamed visual style folder. For the style to appear in the list, the folder name in which it is residing must correspond to the name of the msstyles file. For instance, gloss.msstyles must be in its visual style folder named ?gloss? in the correct directory (C:\WINDOWS\Resources\Themes) and it will appear. The correct path for the file itself should then be:

C:\WINDOWS\Resources\Themes\gloss\gloss.msstyles

And equivalently, the shell folder should be in the same ?gloss? folder: C:\WINDOWS\Resources\Themes\gloss\shell.

Q: I patched, but my start menu and taskbar are not skinned or visual styles do not work. What is wrong?

A: First, check to make sure the correct version of the dll is being used. Also try patching in safe mode. Then check the directories to see if uxtheme.dll has been misplaced. It should only appear in the system32 folder, and not in the Windows folder. If all else fails, try replacing uxtheme.dll with Replacer in safe mode several times. Some have indicated that this fixes their problem.

Q: My system freezes during "Please wait..." when I try to apply a visual style. What's wrong?

A: This is most likely caused by extra uxtheme.dll files. Do a search for all uxtheme.dll files and delete the ones that are not in C:\WindoOther Questions>Other Questions

Q: How do I create visual styles using the .msstyles format?

A: The easiest way is to modify an existing visual style. You can use Stylebuilder to do this. Note: you do NOT need Stylexp installed to use Stylebuilder, so ignore the error message, but you must be patched (obviously, you'll need to be able to apply visual styles in order to use Stylebuilder. That's all the error means).

Resource Hacker and Resedit are similar programs that can be used to modify visual styles. These are simple and intuitive, and are my personal recommendation. These allow you to modify images (bitmaps, png files, etc.) and values (in the textfile section) to change the visual style. This is all that is needed to create a visual style.

Q: Why don?t people use Stylexp?

A: The uxtheme hack has several advantages over Stylexp.

-the uxtheme hack is simple. You simply replace the file with a hacked one and that?s it. No installations, no need to run and configure programs, no hassle.

-the uxtheme hack does not waste resources. Stylexp patches uxtheme.dll in memory, but the uxtheme hack replaces the file physically on the system. This means that you are unlocked forever (until Microsoft creates a new uxtheme.dll file).

-the uxtheme hack is completely free!

Enjoy!

According to the quote below, there is no other way than the "uxtheme hack" to install third-party (non-microsoft) visual styles. It clearly states, "By default, uxtheme.dll is locked, so third party (i.e. non-Microsoft) visual styles cannot be used. Fortunately, it is easy to unlock uxtheme.dll to allow the use of non-Microsoft visual styles."

I'm pretty sure that's a load of crap. That' so you just risk your system files with the UXTheme package. I personally have NO problems using TuneUp Styler 2, included in my copy of TuneUp Utilities 2009. It allows me to use ANY visual style (msstyle) without having to overwrite vital system files.

I'm pretty sure that's a load of crap. That' so you just risk your system files with the UXTheme package. I personally have NO problems using TuneUp Styler 2, included in my copy of TuneUp Utilities 2009. It allows me to use ANY visual style (msstyle) without having to overwrite vital system files.

Thanks for the quick response.

I tried the Tune Up styler on Vista Enterprise. It does have an interface which allows a Visual Style file (*.msstyles) to be selected from the disk to be applied as the windows appearance.

When I selected a Windows XP Visual Style file to be installed using the Tune Up styler (in Vista) it said that the Visual Style file was incompatible and asked me if an installer was available.

OK. Now, to the critical part of the problem.

I want to be able to create a visual style file (*.msstyles) or an installer for it which can be interchangeably used both in Vista and XP.

Regards,

Ram

From Vista Thread...

I believe that the two msstyle formats are quite different in structure, enough to be incompatible. You could however create an installer that includes two different msstyle files and installs the correct one based on the OS version you are installing on.

From Vista Thread...

Ok. Then the question that arises now is:

Using which command or syntax do we "install" an unsigned Visual Style File in Windows XP and Vista?

That is.. we need a code similar to the one used by Tune Up styler internally to install the Visual Style File.

Regards,

Ram

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Google was using the old CATPCHAs data to train their LLMs. What is the say they won't use this camera data of users to train their LLM? these companies need some strict regulations!
    • Depends on what you need. Might be a bit clearer on what you plan to do with it. Sort of a waste if you get the newest and greatest, but don't know how to use it.
    • NTLite 2026.06.11200 by Razvan Serea NTLite is a Windows configuration tool that allows you to modify your existing Windows install or an image yet to be deployed, remove Windows components, configure and integrate, speed up the Windows deployment process. Reduce Windows footprint on your RAM and storage drive memory. Remove components of your choice, guarded by compatibility safety mechanisms, which speed up finding that sweet spot. Windows Unattended feature support, providing many commonly used options on a single page for easy setup. Easily integrate a single or multiple drivers, update or language packages. Package integration features smart sorting, enabling you to seamlessly add packages for integration and the tool will apply them in the appropriate order, keeping hotfix compatibility in check. One of the important new features of NTLite (compared to its predecessors) is the ability to modify an already installed the operating system, by removing unnecessary components. Supports Windows 11, 10, 8.1 and 7, x86 and x64, live and image. Server editions of the same versions, excluding support for component removals and feature configuration. ARM64 image support in the alpha stage. Does not support Checked/Debug, Embedded, IoT editions, nor Vista or XP. NTLite 2026.06.11200 changelog: New Secure Boot Migration support: Verification, certificate staging, and boot-manager/sector update across the Image, Updates, Apply, and Create-ISO pages (2023 CA migration, optional 2011 revocation, Anti-rollback, Boot sector choice etc) Secure Boot Host Readiness: Live host Secure Boot migration monitor and Servicing-task control Option under Image page - C:\Windows row, or load the host as the target - Updates - Secure Boot Image: 'Sort mounted images first' option for the image list in Menu-Settings UI: Hover description card for Components and Unattended pages, selectable text and quick access to Compatibility options Command line: Relay commands into the already-running instance Enables controlling already running NTLite via ntlite.exe Use /NewInstance to launch an additional instance using CLI operations (premium) UI: 'New instance' option via main menu instead of a secondary ntlite.exe prompt Apply: Hide individual Apply-page notes with a per-note dismiss (X), critical excluded Settings: 'Unsigned RDP file launch warnings' tweak (RDP client), bypassing the April 2026 security-update prompt on RDP connections Upgrade Image: Live OS and deployed image editing now unlocked on free/test licenses, same licensing as images Image: 'Recompress' option in manual dialog Remove Editions to shrink the WIM in one session Image: SWM part size set inline on the Apply page and image dialogs, split-size popup retired Image: Relative 'Last change' dates; editions grouped by build time to reduce noise Image: 'Forget - Missing' on the Edit-cache menu to mass drop entries whose folder is gone Components: Root groups reorganized - user-facing groups first, system/critical last Components: Show filter options to view components by Template or App-type, since Apps are now merged into groups Presets: Delete confirmation now lists the multi-selected preset names UI: Design update propagated to the rest of the tool UI: Filter and search match words in any order and partially, better results filtering Components Unattended: Input-locale language derives from the user locale, with an independent keyboard picker, enables combinations previously unavailable Unattended: Input-locale now allows for a user value override Unattended: Localization OOBE WinPE now can be copied with the new WinPE Copy OOBE localization toggle, enter locale settings once for both stages Updates: Downloader greys and locks updates the image already carries (hotfix and MSIX) Updates: Resume interrupted update downloads Command line: Many upgrades, see /?, now prints help to the console or redirected output UI-Translation: Finnish language added, also thanks for Chinese Traditional (Matt), French (tistou77), Italian (clarensio), Russian (RDS), Swedish (1FF), Vietnamese (Vu Anh Vu) Fix Components: Containers removal breaking Apps deployment Components: Microsoft Account had leftovers when Easy Migrate is kept Image: Export to an existing WIM improvements, Append renamed to Merge Image: Improved 26H1 live removal support Image: No more 'X:\ not accessible' popup for certain drives during image scan Presets: Manual image refresh picks up presets added/removed outside the app Tweaks: Disabled visual-effect animations no longer return after first logon on a new profile Tweaks: Live Visual Effects toggles (animations, drag full windows, font smoothing) now apply correctly Download: NTLite 2026.06.11200 | 20.5 MB (Free, paid upgrade available) Link: NTLite Home Page | NTLite Features | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Ah. La Fontana De Incontinentia ! Bella ! Bella !
    • Hi everyone, I'm planning a small network upgrade and was wondering how others prepare their networks for future needs. Do you usually invest in higher-speed switches and better cabling from the start, or do you upgrade only when necessary? I'd be interested in hearing what has worked well for you and any lessons you've learned over time. Thanks!
  • Recent Achievements

    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
    • First Post
      carols23 earned a badge
      First Post
    • One Month Later
      Tom Willson earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      504
    2. 2
      +Edouard
      257
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      93
    5. 5
      macoman
      67
  • Tell a friend

    Love Neowin? Tell a friend!