Try using Stardock Central, it's stuck on a version of WB6.  Not sure if the download works, but it's worth a try.

Stardock will email you links to everything that you have ever bought from them.

Why do you want to go back to WB6?

What do you dislike about WB7?

i guess i'll roll back to v6 also. No more random wallpaper, can't cahange the texture color, dreams no longer work, & wb7 has frozen my system a few times (always when i too much of a hurry to get & save details). The new interface is Kuel but the features & stabilty of v6 win. 

PurrBall: I cannot download WB6 (or anything else) through Stardock Central.  I get an error message that (this is a paraphrase) that Stardock is no longer using the Stardock Central platform and downloads/updates are exclusively through Impuse now.

Chasbo: Still waiting for a reply from Stardock.  I'm guessing it is delayed because of the holiday, but I expect a reply Monday or Tuesday.

Neil: There are several problems I have with WB7.  A minor issue is one that I also had with WB6 - the applet that applies a background to Windows Explorer windows has simply never worked, not only on this machine (before and after a video card upgrade), but on a previous Windows XP machine (which, I'll admit, is anemic in video power).

An issue that I consider major, but is probably more annoyance to anyone else, is that SkinStudio 6 is no longer able to skin the Windows Explorer backgrounds either.  No matter which background I try, there is no effect.  WB Skins to which I have already added Explorer backgrounds no longer skin either.

Something I consider a biggie is a problem I have when renaming files in Windows Explorer.  Normally, you can move the cursor around when renaming files, so that you need only change the parts of the file names you need to.  Since WB7, I can't do that anymore; the entire file name blanks out when I try that.  I have to manually place the cursor in every place I need to change a file name, or type the new file name in from scratch.

That said, I love the new interface, and the ability to alter fonts directly in WB7 is great (and would be even greater, if I could skin my Explorer backgrounds).  But I agree with CHris -- the wallpaper changing applet is missing a few basic features, such as the ability to look in subdirectories, and that makes it useless for my purposes.  (That's a WB6 problem as well, to be fair.)

Anyway, let me give you the stats on my machine as given by WB7:

Your computer has a Windows Experience Index base score of 3.6
Your Windows Graphics Experience score is 3.6

WindowBlinds version : WindowBlinds 7.0 (build 230 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(Acer V223W ) 1 is attached to NVIDIA GeForce 8400 GS  
(ACER X223W ) 2 is attached to NVIDIA GeForce 8400 GS  

Wblind.dll         2009/11/16 11:43:20
Wbsrv.dll         2009/11/12 08:19:07
SevenConfig.exe         2009/11/12 10:16:53
Wbload.exe         2009/11/06 11:44:12
Wbhelp.dll         2009/10/07 14:35:07
Tray.dll              2009/10/21 08:13:19
Wbload.dll              2009/09/25 07:41:28
Screen.exe         2009/11/07 11:39:26

The WE score is based on the video card -- everything else is in the high fives.  WB6 worked fine with my current configuration, and I simply can't afford to upgrade my video card right now. (Too many plumber calls lately.)

What do you mean by dreams no longer work?

WindowBlinds does not run dreams, but if you have Deskscapes it should work fine with it.

I am confused about the texture colour issue as WB6 didn't do textures at all, and WB7 will recolour a skin including the texture when the correct modes are set (disable the option to use the texture colour when applying a texture and it will use the skin colour which can be recoloured)

The lack of random wallpaper is something we have noted as being something users would like to see back and this will be investigated.

It sounds like transparent explorer backgrounds are being stuck on which is causing it to ignore the skin defined backgrounds and the blanking filename issue.

I suspect there is a leftover key from WB6 thats confusing WB as WB7 uses different regkeys.

You shouldn't need a newer graphcis card to use WB so thats ok.

Is there a solution for this?  I had a feeling that some files were left over from WB6.  I wish to roll back to WB6 also as before updating to WB7 I had recolored my Explorer Background a light green and now any and all skins have Exlorer Backgrounds that are this light green.  I would sacrifice all the great features in WB7 just to get rid of that green. 

Have emailed support and hope they can help me with the problem or allow me to have MY WB6 back. 

Add me to the list of those wanting to roll back to WB6.

jb0615

Looking through the Registry, there are a lot of references to WB6 -- but I don't want to start pulling out keys without knowing exactly which ones I need to remove.  The Registry is a strange beast and you never know how altering or removing one key will mess up something else.  I need an expert opinion.

We have located some keys which were not being blanked and the next WB update will force these to blank.  The keys in question are the ones for controlling the explorer backgrounds colour & saturation from WB6.  If set they will override any skin provided explorer backgrounds.

This is correct... SDC's download functionality has been permanently disabled. It exists at this point only as a tool for restoring .sdc archives.

If anyone absolutely must use WB6, you can email [email protected] and we can set you up with an archive of the latest release version. However, we tend to prefer you continue using the latest version and provide feedback about your experience so we can continue to improve it for everyone. (Business standpoint aside, I'm a huge advocate of WB7 )

Mike

Can you give me an advance secret about those keys?

Certainly. 

HKEY_CURRENT_USER\Software\Stardock\WindowBlinds\wb5.ini\WBLiteFX

forceActiveHueGlass
forceInactiveHueGlass
forceActiveSatGlass
forceInactiveSatGlass

Just delete those values.

Unfortunately, this seems to have had no discerable effect.  Sorry.

OK, here's something strange...I just checked for updates on Impulse and the update for WindowBlinds 7 says "WindowBlinds 7 - Previous Version Installed."  Since I have WB7 installed, I don't know what to make of that, except that it's telling me that it wants to remove some WB6 elements that shouldn't be there.  Is that what Impulse is trying to tell me?

Well, I ran the "update." It didn't even ask for a reboot, though I rebooted anyway.  No discernable effect, however.

Well, it seems that Stardock simply wants me to give up on WindowBlinds 7.  They sent me a link to WindowBlinds 6, sent detailed uninstallation instructions for WB7 (basically uninstall, check to be sure all related files are gone, and then manually delete all registry entries), instructions on how to fix the damage this will do to Impulse -- all with no guarantee that any of this will actually work.  I could end up with no version of WB that actually works -- or possibly worse.  This is really fun.  Stardock is using me to test a possible fix theory, and I've pretty much decided to leave the partially-working WB7 alone.  Maybe they'll actually fix it one day.  My subscription is current till June, but after that...I can't see keeping a subscription current if Stardock is unwilling to fix problems.

How about doing a backup of your system with this program [trial version] Acronis Home 2010 . Then try the fix with wb6... Somehow I see you still having an explorer background problem with wb6 installed.

The reason would be with the drivers being used for the graphics card you have. That and a few other things that I can think of... but I would need to evaluate your system myself to understand completely what is wrong.

My best suggestion is to try and work with the support people at Stardock and see what they will do for you before making rash decissions about what they are trying to do for you. Also to say anything like that is very rash considering I have wb7 and other versions tested and running here on several OS's with no problems. I have noticed an explorer issue with XP... but only that it is using a bit more than usual amount of cpu memory for the process.

There are several things to consider when you have a program issue. One that it is not just the program; when there are other people that do not experience the same issue. It is usually dependant upon your problem with other parts of your OS. Thus a driver not installed correctly or even just a bad driver completely. Along with the possiblity there is some other issue present and working against anything you may do with the system. Namely [Vista]

Do a complete backup with the software I've given you a link to so you can restore the system if need be the case and follow the instructions to reinstall wb 6. Then if it works you may even try to install wb 7 again to see if it works like it should. You can even do another backup before you do that install of wb 7 again so as if it does not you can easily go back to the working model.

If you work with the support people at Stardock in a proper manner you will find they will get you fixed up. They are the best and work very hard to get anyone's problems resolved.