Vista - Unpatched themeui.dll for x64?

So this afternoon I tried to patch up my system files to allow custom themes, using a combination of Vistaglazz and manual file replacement. I was more or less successful-- I could apply and use themes without any problem, although during the installation the unpatched versions of themeui.dll, uxtheme.dll, and shsvcs.dll did not take nicely to being renamed. (I'm not sure what quite went wrong, but at the time I figured that I would never unpatch them, or would be able to recover them otherwise.)
However, now when I boot up my computer in Vista, it won't load. I can go through the login screen just fine, but after logging in the screen goes black and returns to the login screen. I'm almost positive this is a result of thethemeui.dll, uxtheme.dll, and shsvcs.dll being replaced, as prior to this everything was running smoothly.
Now, my computer dual-boots Ubuntu and Vista, so I'm also quite sure that I can just boot up in Ubuntu, access the system files from there, and avoid a system restore. The only problem with this plan is that I can't get a hold of any compatible files-- the only copies of these files I can find are 32-bit versions, while I run 64-bit Vista. Google isn't turning up much aside from a year-old forum thread between programmers and this forum. I figured there would be someone here able to help me.

In short, I am looking for unpatched themeui.dll, uxtheme.dll, and shsvcs.dll files for 64-bit Vista. Can anyone help me out?

Hey Foiled,

Its illegal to distribute System Files, however I will send you them anyway as I know how hard it is to recover from a failed manual attampt at uxtheme patching...Its happened to me enough times that I created a UXTheme patcher for these reasons

I used 8 different file verification and system metric integrity checks before patching and I designed it to use the new Kernel Transaction Manager included with Vista and its currently the only UXTheme patcher using this functionality for 100% patching reliability, If even the slightst call fails then it doesnt touch anything, if you would like to try it out, I can send you a download link?

(My system hasnt been patched since Ive mainly been using Windows 7 )

Oh, really? I should've known that.
But a link would be wonderful, I'm going out of my tree trying to fix this.

Hi Foiled,

Did you get my e-mail yet?

Steven

If this is slightly old, sorry, but do you know if you're MMC.exe works after you patch it? If so, could you send me the files too? The patched files that I used both from withinwindows.com and VistaGlazz worked fine, but I couldn't use any of the MMC snap-ins afterwards. (Including disk management, device manager, task scheduler, perfmon, etc... Can still use Windows Defender and other windows programs. )

Product
Microsoft Management Console

Problem
Stopped working

Date
3/5/2009 7:57 AM

Status
Report Sent

Problem signature
Problem Event Name: APPCRASH
Application Name: mmc.exe
Application Version: 6.0.6001.18000
Application Timestamp: 47918d09
Fault Module Name: mmc.exe
Fault Module Version: 6.0.6001.18000
Fault Module Timestamp: 47918d09
Exception Code: c0000005
Exception Offset: 0007490f
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

Extra information about the problem
Bucket ID: 703794886

i had the same problem one time as well on my laptop running 32bit vista. one, you are right--since you dual boot, you could have accessed the files from linux (that's what i had to do when i messed up my laptop). the main thing, though is this: if you plan to change those files again in the future, take ownership of the files, rename them by adding something to the end of the filename, but keeping the main part of the filename intact. for example: rename themeui.dll to themeui.dll.default, or something like that. you can keep the renamed files in their directory if you choose. then, if you have a problem again, you can access the files by way of linux, delete the offending files, and change back the names of the files to their original filenames.

you may have already got your remedy, but i know from experience that this way works too.