Themes, like flyakite and other msstyle themes have to do one thing first. They modify the uxtheme.dll file to allow the native WindowsXP theme service to use themes that are not digitally signed by Microsoft. So, flyakite alters a system file to allow you to use a different theme. Windowblinds runs its own theme engine to sking the UI. No, you cannot start it, load a theme and then unload it and still have the theme stick. So, yes, you have to have Windoblinds running at all times. Now, it has been bundled more into the OS with more recent versions, so you don't have the process wbload.exe running as you used to have. But here is the deal. Even if you are using WindowsXP's inherent themes service, you have an extra process running, the Themes Service (just go to Run->services.msc and you will see that the Themes service is enabled. This is hidden in one of the many svchost.exe processes that you have running right now (just check, you have a bunch of them running I bet, everyone does.) So, if you are using Windoblinds you can simply disable the Themes Service and let WB do the work. Either way, you have a process running in RAM, either Windowblinds or or the Themes Service. And the truth is, using the same theme, Windowblinds will use less system resources because it dishes much of the work off to your graphics card. Afterall, the Themes service is many years old now, but Windoblinds has continued to be updated and improved. Long post short, it doesn't matter which you use, themes like in flyakite or Windowblinds, both use RAM, both load a process. Just one of those (Windowblinds) has come a long, long way since the Themes service was implemented.