Hours after I activate it,

either on my old windows seven years ago,
or on my current windows ten, just months ago,

WindowBlinds10 has had critical bugs that brought chaos in my explorer:

- it starts on boot, but the skins are all disabled, jsut the color schemes remain changed
- it displays different styles from one program to another
- it consums too much ram (through I have a gamer PC that can run about any game)
- at one point, file explorer just crashes on boot, and I have to start it in command line.

Until now, links to explorer'exe seem messed up in my registry: If I try to start the exe without providing a folder parameter it trigger a ststem error! 

This had happened twice now, and the bug is so huge that I thought that other users must encounter it too, since there has been little to no update to correct them or communication/warning about such a bug in years...

Since few users apparently reported this; there are no official topics about that on the forum, and no warning or tutorial advising us on how to avoid that in the software,

I thought it was because other had better skills at skinning and it's not useful to report them again. 

So I always end up installing three skins, then disabling WindowBlinds10, reskinning the three skins, and applying one of them (Auralis Premium usually) with SkinStudio10, since, anyway, the design of the only three skins that I love has some elements that remain not skinned and with discordant grey colors.

Then, when I realize that whether I use WindowBlinds10 alone, 

WindowBlinds10 and SkinStudio10,

or SkinStudio10 alone, the bugs are exactly the same.

So both times, I had to uninstall everything and realize that I spent a lot of money to learn about manual skinning.

Learning was cool, but the software is not functional on systems mlike mine.

I don't know if it's a rare bug or not, but it seems important enough to mention.