Recommended Posts

Okay, I was looking around and seeing if I could change the theme of my Windows because I was getting bored of the same thing. I came across a site called Customize.org. I browsed around and found one that I liked, downloaded it and automatically tried to use it. Obviously I got some typical error. I went back and saw that I needed some software so I just clicked what was in my face which happened to be: Ux Theme Multi-Patcher.

I downloaded, patched, rebooted and tried again. No luck. I then found out that this wouldn't work on SP2 or SP3. So, I went back and found: SP3 UxTheme Patcher 1.3. I downloaded, patched, and rebooted that and tried yet again. No luck. I opened the SP3 Patcher back up to restore and that worked fine. But when I opened the first Patcher, the option was not available after opening it (there's only Patch or Cancel).

Now, I'm stuck on Windows Classic Theme and can't get back to Windows XP Theme or any other without getting an error: "The visual styles could not load because the file failed to load. Details: "

I read that having more than one uxtheme.dll could cause errors. I read that you should ONLY have one in your system32 folder. So I searched and found one in a $NtServicePackUninstall$ (blue text) and one in ServicePackFiles/i386. These two are the same 214kb size while the one in my system32 folder is 199kb (if that makes any difference; probably, but I wouldn't know).

I've already tried system restore and that did nothing. I searched for any type of virus/malware/spyware/etc and found nothing. I fixed my registry with a software and when I rebooted I still had the problem. I also had downloaded this "XP_Theme_Fix" and put that in my registry prior to all the scanning and repairing and that did nothing.

I still have Luna and Classic Theme and everything in my Resources>Theme folder. I just don't know what else I need to edit, install, or restore to to fix this... All of this nonsense over wanting a new look... really?

If you need more information, I can provide it. Just help me at least get back to XP Theme... THANKS! :)

Link to comment
https://www.neowin.net/forum/topic/868294-uxtheme-problems-sp3/
Share on other sites

Copy over the 214kb one to your system32 folder. If windows complains that the file is in use rename it to uxtheme.old then try copying it over again. Reboot and delete uxtheme.old. You can also take the file from your Windows CD.

Rename the 214kb one I'm copying over to uxtheme.old or the 199kb one already in there? Oh, and remember that there's two 214s, so I do that with both which would inevitably delete one of them?

Edited by Darkiboo

Fixed! Thanks Lepton! :D

Took the uxtheme.dll from ServicePackFiles, tried to move it to system32, said if I wanted to override, said no, renamed system32 file to '.old, tried again, said if I wanted to override again (this time it listed they were the same size but after ordering by name and finding the second one, turns out it was 199-200kb), named that new file '.old2, transferred over ServicePackFiles uxtheme.dll (was allowed with no problems), rebooted and when it came to I saw that ugly, annoying, typical, olive green bar at the bottom of my screen again.

I listed the steps in case this happens to anyone else. >.<

Alright... ROUND 2!

Even though you've said you've fixed it already. When you come to wanting to patch another system try using UxStyle rather than UxTheme because it doesn't require patching, just a tiny process in the background.

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

    • No registered users viewing this page.
  • Posts

    • Although AI is great and has it's use cases they likely have massively overhyped it and it has not delivered as per their expectations. I fully expect them to start saying the same things again when it does get to a certain level of intelligence!
    • Microsoft wants to end printer driver headaches with Windows Ready Print by Usama Jawad A few days ago, Microsoft released Windows 11 Experimental build 26300.8553, bringing a ton of enhancements such as Start menu customization, search improvements, Taskbar polish, and other minor UI tweaks. Another relatively major enhancement snuck deep within the change log was related to upgrades to the Windows printing experience. Now, Microsoft has shared more details about these benefits. For starters, Microsoft has renamed its Modern Print Platform to Windows Ready Print. The company believes that this name highlights its shift in strategy, which now focuses on modernizing, securing, and streamlining the printing experience for Windows devices. Some of the upgrades present in Windows Ready Print have already been seeded to customers and partners. This includes ending support for third-party printer drivers via Windows Update and transitioning towards the Internet Printing Protocol (IPP) and the native Windows IPP printer driver. In line with these changes, new printer installations will default to Windows Ready Print on eligible devices starting from July 2026. However, Microsoft recognizes that not all environments will be able to migrate to this platform immediately, so it will allow users to choose between installing the printer via Windows Ready Print or the traditional OEM process. Users will be able to toggle this configuration through Settings > Bluetooth & Devices > Printers & Scanners > Printer preferences. This control applies only to new printer installations, and its functionality can also be modified via Group Policy as follows: Launch Group Policy Editor Navigate to Local Computer Policy -> Administrative Templates -> Printers Find and select 'Configure Windows Ready Print driver ranking' -> double click to open it Select 'Enabled' (if you wish to enable Windows Ready Print driver selection) or 'Disabled' (if you wish to explicitly disable Windows Ready Print driver selection). Select Apply Select OK Similarly, if you set up Windows protected print mode through the same setting in Windows 11, it will also default to using Windows Ready Print exclusively. Microsoft hopes that these improvements will help eradicate dependency on OEM-specific driver installation processes and simplify printer installations. We'll likely find out more about other tangible benefits in the coming months.
    • Hey what's about the proton vpn firefox extension ? It's not working today
    • On what though? Not Ray Tracing.
  • Recent Achievements

    • One Year In
      Primer1st earned a badge
      One Year In
    • Experienced
      JayZJay went up a rank
      Experienced
    • Reacting Well
      Sir_Timbit earned a badge
      Reacting Well
    • Week One Done
      rubentuben8 earned a badge
      Week One Done
    • Week One Done
      ARaclen earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      513
    2. 2
      PsYcHoKiLLa
      229
    3. 3
      Edouard
      137
    4. 4
      ATLien_0
      87
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!