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.
VistaGlazz and how to make Vista a bit more transparent. If you feel uncomfortable with these kind of patching utilities, you can always create a system restore point. VistaGlazz will never delete your original files. Instead it will make a copy of the original file, patch the copy and rename the orginal to a backup extension.
The KB933928 doesn’t break any of the functionality offered by VistaGlazz. You might encounter problems with custom visual styles based on the Aero visual style. Before KB933928 was applied, Windows Vista didn’t really care about the name of the visual style folder, .msstyles filename and the MUI. After applying KB933928, your visual style folder, .msstyles filename, MUI and folder structure must be correct, or Windows Vista will drop back to classic mode when you try to apply a custom style.