0

I am trying to get some visual styles working completely on my computer.

They say I need to patch some files, install the theme, and to get the style working 100%, I also need to replace explorer.exe, shell32.dll, and a few other files.

The problem is, when I do this, after restarting, the computer gives a shell32.dll is missing error and won't load. I have restored my computer to a working state, but that's not the problem. The problem is I want the visual style to work completely, all bells and custom start button included.

If this is a duplicate(I couldn't find a question similar to this on Google or Super User with an answer), please link me in a comment.

studiohack
  • 13,468
  • 19
  • 88
  • 118
Blue
  • 101
  • 1
  • ok, so I figured it out. I booted into safe mode, did all the regular steps, and now it works. this is a nice theme. smiley face. – Blue Jun 05 '11 at 09:16

3 Answers3

0

If the visual style operates by hacking the shell, and the hack failed, it's unlikely that it's going to work on your computer. My guess is that whatever custom theme you're using is built for x86 and you're running x64, or vice versa.

Either way, what you're doing is not supported by Windows. You'll have to contact whoever built the theme and ask why their hack is not working.

Billy ONeal
  • 8,141
  • 14
  • 61
  • 91
  • bummer, because it was the 64 bit dlls and exe that I was copying over. – Blue Jun 05 '11 at 07:57
  • @Blue: Just copying them over shouldn't work. The system has access control lists by default set to prevent exactly what you tried to do -- replacing system files with unsupported versions. It's possible to override but it's more than just "copy this over"... you'd have to remove the TrustedInstaller permissions. Really, any kind of modification like this is a bad idea. You really want to give whomever supposedly wrote that theme complete control over your computer? Because the shell is one of the programs that can take over the Secure Desktop (and the machine) quite easily. – Billy ONeal Jun 05 '11 at 07:59
  • yes, I know it's dangerous, but I want to install the themes completely anyway, and yes, I did do the permissions thing and replaced the files. And that's when windows get's all bummy at me and gives the error(after I restart of course). – Blue Jun 05 '11 at 08:06
  • @Blue: Yes. It's Windows' fault that you replaced the shell binaries and the replacements don't work. Oh wait. – Billy ONeal Jun 05 '11 at 08:07
  • That's not what I'm talking about, isn't this supposed to be a place for people who play around with their computers? – Blue Jun 05 '11 at 08:12
  • I've done stuff like this, and have had no problems. I'm running a custom theme right now, in fact. The only thing I can think of is that your archiving program might be 32-bit, and so does not extract the files to the 64-bit System32 folder, leading to the error. Try extracting the files elsewhere and then copying them over using Windows Explorer. – Soumya Jun 05 '11 at 08:15
  • @Blue: Yes, it is a place for that. It's not a place for ripping on any particular products though. That would be considered subjective or argumentative, neither of which are allowed here. If you spread FUD, people like me are going to call you on it. – Billy ONeal Jun 05 '11 at 08:17
  • @Soumya92: Why not post that as an answer? – Billy ONeal Jun 05 '11 at 08:17
  • hmm, theres a system32 folder and a sysWOW64 folder. If I understand correctly, WOW64 is the thing which lets 32 bit programs run on 64 bit windows 7. But the thing is theres also an explorer.exe in the sysWOW64, do you think it would be a good idea if I also changed the files in the sysWOW64 folder? – Blue Jun 05 '11 at 08:21
  • @Blue, Yes. But in all probability the provided DLLs are 64-bit, and should go in the System32 folder. However, it is possible that your archiving program (being 32-bit) is seeing the SysWOW64 folder AS system32, and so you may have deleted the shell32.dll from System32, but it is being extracted to SysWOW64, hence the error. – Soumya Jun 05 '11 at 08:23
  • no that's not it, I extracted the files to my downloads folder, then copied them from there to the system32 folder. HMM. – Blue Jun 05 '11 at 08:24
  • @Blue, try point 2 in my answer. Although it is odd that you see a "missing" error instead of a normal BSOD. – Soumya Jun 05 '11 at 08:30
0

I have never faced any problems (Windows 7, 64-bit) when trying many of the themes that require such replacements. However, I can still think of a few things you can try:

Make sure your archiving program is 64-bit. If not, it will end up extracting the files into the virtual storage folder SysWOW64 instead of System32. I recommend 7-Zip. If you cannot obtain a 64-bit version of your archiving program, extract the files to another folder (Desktop works best), and copy them using Windows Explorer.

In the off-chance that this fails as well, or if you do not want to risk compromising your system, you can also use something like Anolis Resourcer to extract the relevant resources from the patched system files, and add them to your versions. This may also reduce incompatibilities with Service Packs or other updates between your computer and the theme author's computer.

Soumya
  • 997
  • 1
  • 6
  • 15
0

Have you tried the Uxtheme Multi Patcher?, usually works for me.

CGA
  • 3,809
  • 21
  • 15
  • Yes, I've already patched my system. The problem is when I want to complete the theme by changing the start button, folder icons, etc. I have to replace files, and that results in problems. – Blue Jun 05 '11 at 08:51