Recommended Posts

Works fine here too! (Win7 32bit) I don't know why people think patching system files is saver then using UXStyle... I mean think of it from a logical side:

If you patch your theme files itself you gonna have a mess whenever a update updates them.

With the Unsigned Theme Service however it's more likely that it's able to patch the new files too, since the memory values it needs to patch might only be shifted around a bit and UXStlye is still able to find them.

With the Unsigned Theme Service however it's more likely that it's able to patch the new files too, since the memory values it needs to patch might only be shifted around a bit and UXStlye is still able to find them.

Is it able to do that? I assumed that if Microsoft updated the files in such a way that the patching no longer works, then UXStyle would need to be updated to accommodate this change. Am I wrong?

Is it able to do that? I assumed that if Microsoft updated the files in such a way that the patching no longer works, then UXStyle would need to be updated to accommodate this change. Am I wrong?

Actually UXstyle is created by the same person who did all the manual patches to begin with. It worked fine for me on Windows 7 Ultimate x64 when I tested it. You have to keep in mind that most people who re-distributed the manual patches and the patching programs based their work on this one guy. He has stopped making pre-patched files in favor of an in memory way of doing it since that one doesn't affect the digital signatures for the files. It is apparently easier to patch it in memory than to have to hunt it down in the files as well.

Actually UXstyle is created by the same person who did all the manual patches to begin with. It worked fine for me on Windows 7 Ultimate x64 when I tested it. You have to keep in mind that most people who re-distributed the manual patches and the patching programs based their work on this one guy. He has stopped making pre-patched files in favor of an in memory way of doing it since that one doesn't affect the digital signatures for the files. It is apparently easier to patch it in memory than to have to hunt it down in the files as well.

Oh, I'm well aware of Rafael's work in patching Windows' system files. My question was whether or not UXStyle would need to be updated when Microsoft pushed updates to the uxtheme.dll and other relevant system files. SkyDX implied that UXStyle could sift through slightly-shifted memory values and adapt to changes in the themes service, and I wasn't aware that it was capable of doing this.

Also, I'm glad it works fine for you. Unfortunately, it seems to be hit-or-miss, and hasn't been updated since July. Also, the more I think about it, the more I'd rather just patch my system files anyway. This: link makes it just as easy as UXStyle and doesn't require a separate service running at all times.

  • 1 month later...
  • 2 months later...

Yes, but how often do we have updates to uxtheme.dll? And if it does get updated, then the re-appearance of the classic theme is a bit of a giveaway.

I'm more of the "fire and forget" type, and would simply re-patch the updated file, rather than have another service running.

Yes, but how often do we have updates to uxtheme.dll? And if it does get updated, then the re-appearance of the classic theme is a bit of a giveaway.

I'm more of the "fire and forget" type, and would simply re-patch the updated file, rather than have another service running.

Always: Every SP

Occasionally: Some random update.

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

    • No registered users viewing this page.