Thank you all for the feedback on VistaGlazz 2.0
We’re glad to see that it enables a lot of people to use custom themes on their systems. With this post I’d like to address a few questions we’ve got by email or on the forum:
It says my system is not supported, what does that mean?
We try to make VistaGlazz compatible with a lot of systems. However there are a few culture specific Windows versions that have their own unique files that need patching, which are hard for us to support. Another reason your files might not be supported could mean that Microsoft released a small update. Late January or early February we’ll release VistaGlazz 2.1 with enhanced patching routines.
I can patch my system but not my aero style
Aero patches are only available on Windows Vista (Aero editions: Home Premium, Ultimate etc.). Microsoft introduced Aero with Windows Vista, that rules out Windows XP support. In Windows 7 maximized windows are already transparent, so there’s no need for a patched Aero.
If you have any problems installing visual styles or patching your system please have a look at the VistaGlazz help file. You can find it in your Start Menu or by pressing F1 in VistaGlazz.
I went through the forums and noticed 
a post by UK.Intel regarding the text color and glow in full screen glass mode. How I missed that post we might never know, but I decided to add it to VistaGlazz two weeks ago to see if it would work. It didn’t. For some reason the addresses seemed to be off by a few bytes, not sure why. Anyway, using the screen shots I was able to retrieve the correct addresses and the patch works marvelously on my Vista x64 SP2 system and on my virtual Vista32 SP1. UK.Intel: Thank you for your post!
Meanwhile Yvo improved the diagnostic screen by adding auto repair functionality to fix the most common of VG related problems. He also managed to fix some minor general UI and reboot screen glitches.
Download VistaGlazz 1.3 now!
(we’re still updating our mirror servers, in the meanwhile use this link)
Microsoft has released Windows Vista Service Pack 2 
and as we’ve come to expect custom style are still not supported. Therefor it’s my great pleasure to announce the release of VistaGlazz 1.2. In this version we’ve changed the following:
- Windows Vista SP2 support
- Major changes to the patching technique
- Asynchronous (read: speedier) start-up
- Few bug fixes/optimizations to both installer/VistaGlazz
I’ve tested the new release with my trusty virtual machines (SP1 and SP2 in both x86 and x64), but the new patching technique of course might not for your specific system. Remember to create a system restore point before you start patching. Refer to the VistaGlazz help file for more information.
To everyone using an earlier version of VistaGlazz. You can uninstall your old version and install the new version. You don’t have to unpatch your system, the new and the old version are compatible.
Get the latest version of VistaGlazz here: VistaGlazzSetup.exe
Mirrors aren’t up to date yet, please use CodeGazer.com download link only
Get Windows Vista Service Pack 2 here: 32 bit and 64 bit
Last weekend we had some problems with the server that hosts the CodeGazer website and downloads. All problems should have been resolved now. The site, downloads and forum are fully operational again. Sorry for the inconvenience.
No news on VistaGlazz yet, we’re trying to get it released as soon as possible, but we have to ask for a bit more of your patience.
We’ve received numerous reports on RunDll32 errors after patching your system with VistaGlazz beta 2. We are looking into the problem, until then we advice (the brave among you) to await beta 3 or our next well tested release version of VistaGlazz.
Read the forum and comments in the VistaGlazz beta 2 post for more information. This issue seems to occur on SP1 systems only.
Update 2008/05/10:
We like to note that VistaGlazz isn’t compatible with Vista Home Basic. Microsoft has deliberately removed Aero from Vista Home Basic, and we would violate probably 10 pages of Terms of Use if we were to make it Vista Home Basic compatible.
Also make sure that you are using Beta 2. Unfortunately the link on our download page linked to Beta 1. Beta 2 should fix any errors caused to you by Beta 1 after patching.