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

    • Microsoft kills AI-powered history search feature in Edge by Usama Jawad In June 2025, Microsoft began rolling out AI-powered history search functionality with Edge 138. The idea was simple: allow customers to use natural language phrases and synonyms to find their desired history items rather than matching keywords exactly. Although the company had already rolled out this capability in a phased manner, it has now decided to cancel it. In an update on its Microsoft 365 Roadmap, Microsoft has announced that it has decided not to move forward with AI-powered history search. The company has not detailed the exact reasoning behind this move, but it has apologized to customers for the inconvenience. The move is rather interesting as it seemingly could have improved user productivity. Edge users wouldn't have to worry about typos or exact keywords, and just focus on what they were trying to locate in their browser history. Microsoft had also assured users that an on-device AI model would be leveraged for this functionality, and no data would be sent to the cloud. IT admins also had the ability to control its availability through the EdgeHistoryAISearchEnabled policy. When the feature began rolling out last year, many of our readers called it creepy, noting that they couldn't trust Microsoft to keep their data on their device. Others also questioned its usefulness, saying that it's simply a way for Microsoft to insert more AI bloat into its products. Although the Redmond tech giant had stated that it will be more mindful about surfacing Copilot features in Windows 11 apps, we later discussed how this is mostly a rebranding exercise rather than an actual axing of AI functionalities. Indeed, a Microsoft executive later emphasized how they want to reshape Windows for the agentic AI era. That said, it does seem like at least AI-powered Edge history search isn't a part of that vision.
    • For you to jump on and defend your sweetheart? I agree, it didn't.
    • Not likely, of course, that we will see routine citizenship checks as they only involve compliance with existing federal voting laws already on the books for decades. This seems a non-issue entirely. Only fools would have the government rush headlong into an AI program few can understand or predict, or even debug...
  • Recent Achievements

    • Week One Done
      tuben earned a badge
      Week One Done
    • First Post
      OffsetAbs earned a badge
      First Post
    • Reacting Well
      OffsetAbs earned a badge
      Reacting Well
    • First Post
      Kolakid60 earned a badge
      First Post
    • Week One Done
      xvvxcvv earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      424
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      Steven P.
      72
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!