Anyone else getting the Classic Startbar revert?

Tired of this.

Hello again. After finally getting a confirmation of activation and the updated version of 7.2, every skin I have tried including the default packaged skins will revert the start bar to Classic Windows 98. The only way I have found to get it to change is to kill wbvista.exe and change it via personalize. I'm very sick of this and bought the program some time ago now and have been working for days just to get it to work. I appreciate the support on the forums and have gotten quick replies (I havn't gotten a single ticket reply after all of this time from my previous problem..) Anyhow. If anyone else is getting this error and has found a solution, please let me know. I also heard disabling Nview could fix this, and have done that.

Here is the information

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

WindowBlinds version : WindowBlinds 7.2 (build 297 - Windows 7 Edition) - 64 bit OS

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(Generic PnP Monitor) 1 is attached to NVIDIA GeForce GT 240

Wblind.dll 2011/06/11 15:55:20
Wblind64.dll 2011/06/11 15:55:08
Wbsrv.dll 2010/08/11 16:48:56
SevenConfig.exe 2011/06/14 14:47:27
Wbload.exe 2010/10/20 16:08:35
Wbhelp.dll 2010/10/20 16:08:34
Tray.dll 2009/10/23 20:12:19
Wbload.dll 2010/06/07 15:59:25
Screen.exe 2010/06/07 15:59:43
And here is a picture. Notice how it will skin other things occasionally, but not the start bar.

14,430 views 43 replies
Reply #1 Top

Impatient133  ...if all/any skin fails to skin the taskbar then it's not a skin-specific issue [some skins exist that do not specifically alter the taskbar...I did some that way as I was then using a different shell], but is more likely some other installed program interfering with WB's 'access' to the skinnng of the bar.

I'll point WB's coder at this thread [when I catch up to him] and see if he can shed some light on the cause/s ...;)

Reply #2 Top

you might want to try updating to the beta 7.02c, build 303 and see if that helps

Reply #3 Top

Update, I disabled startup and services in msconfig and attempted it, still the same thing.

Reply #4 Top

try this don't know if it will help.

apply Win 7 default  the first one in the list (Windows Aero) then run Ccleaner and any other cleaner and Spy ware you have. restart PC

then apply a WB Skin... if no go.

 

If you can try a system Restore a day or 2 before it happened.

 

did you install any programs that do anything to you taskbar.. if so uninstall them...

did you add any context menu to the registry or (as in did you edit in Regedit) if so undo them

Example:  I used (Disable Full Row Select Windows 7) and some WB skins will not let me use the Explorer Backgrounds in WB's

undid it but still will not let me ...

 

hope something here will help good luck...

Reply #5 Top

another question(s)....

Did you have the trial installed before getting the full version?

If so..did you uninstall the trial before installing the full version?

The full version will not "update" the trial. You must uninstall the trial before installing the paid version. It's also important that you reboot the computer after installation.

 

Reply #6 Top

^ That is a very good question.

Reply #7 Top

Quoting DrJBHL, reply 6
^ That is a very good question.
End of DrJBHL's quote

And probably why there is difficulty.

Reply #8 Top

Sorry about the delayed response.. I posted one, but it must not have properly hit Post Reply.

I did not have the trial version installed. I've also uninstalled it, cleaned the registry, manually searched through for any remnants, rebooted, re installed, rebooted, and no avail. I've also repeated the procedure after going into Msconfig and disabling services and startup.

Reply #9 Top

question again.....have you ever installed any other customization software? (non-Stardock)

Reply #11 Top

There seems to be a number of people with Nvidia cards (like yours) posting issues with the latest set of Nvidia drivers like in THIS thread. Not the same problem but indicative of an issue.

I suggest you try an earlier driver release and see if it makes a difference. If the problem was more widespread I'd think it was a Windowblinds problem but all the posts I've seen about 7.2 include Nvidia cards.

Reply #12 Top

I took your advice and downgraded to 270, and no changes resulted.

Reply #13 Top

Somethings missing methinks.

Reply #14 Top

Quoting Uvah, reply 13
Somethings missing methinks.
End of Uvah's quote

Something? Pray tell, as I'd love to get this working.. As of now, I could have bought many games on Steam's Sales with $19.99..

Reply #15 Top

Do you have MyColors installed?

Reply #16 Top

Quoting DisturbedComputer, reply 4
system Restore a day or 2 before it happened.
End of DisturbedComputer's quote

Reply #17 Top

I was comparing the info from my WindowBlinds to Impatient 133's. These are his.

Wblind.dll     	2011/06/11 15:55:20
Wblind64.dll 2011/06/11 15:55:08
Wbsrv.dll 2010/08/11 16:48:56
SevenConfig.exe 2011/06/14 14:47:27
Wbload.exe 2010/10/20 16:08:35
Wbhelp.dll 2010/10/20 16:08:34
Tray.dll 2009/10/23 20:12:19
Wbload.dll 2010/06/07 15:59:25
Screen.exe 2010/06/07 15:59:43

These are mine. I don't know if it makes any difference but look at the Tray.DLL Mine is 2010/04/01 His is 2009/10/23 .
 We have the same one WindowBlinds 7.2 build 297. Hope this helps.

Wblind.dll         2010/12/03 13:50:20
Wblind64.dll         2010/12/03 13:50:08
Wbsrv.dll         2010/11/29 14:40:56
SevenConfig.exe         2010/11/29 14:40:27
Wbload.exe         2010/11/29 14:40:35
Wbhelp.dll         2010/11/29 14:40:34
Tray.dll              2010/04/01 17:40:19
Wbload.dll              2010/06/07 15:10:25
Screen.exe         2010/06/07 15:10:43

 

Reply #18 Top

Quoting DisturbedComputer, reply 16

Quoting DisturbedComputer, reply 4system Restore a day or 2 before it happened.
End of DisturbedComputer's quote

It was doing this ever since I installed it.

Also, I have not installed Mycolors 

Reply #19 Top

I almost thought this was my post.  I just posted it yeasterday, but I hadn't seen it yet.  I HAVE this every same issue since I installed WB7 and I had to uninstall to get it back the way it was.  I did this twice and won't reinstall, until I see a solution.

I was thinking it may be another program I am using, that does Visual Styles.  It is called TuneUp Utilities 2010.  This program is what got me intersted in customized Desktop's and thus StarDock.  I have tried to ask TUU Support if this would be an issue from them.  But, since I did get most of the skin applied just fine, I am thinking less that it is a problem with the TU U 2010 and possibly WB or the actual skin - Edge.

I don't know and I will be reading this thread.  By the time you get this post, I would have read it.  Please remember, I don't know what is in this thread yet.

Thank you,

BarJabba

Reply #20 Top

Tune Up Utilities might be the problem if you have it, Impatient 133.

Reply #21 Top

Quoting BarJabba, reply 19
I was thinking it may be another program I am using, that does Visual Styles. It is called TuneUp Utilities 2010.
End of BarJabba's quote

Almost a dead certainty that is your problem...;)

Reply #22 Top

"question again.....have you ever installed any other customization software? (non-Stardock)"

I would say a big bingo on that.  But, funny, in my case, I immediately uninstalled the WB and rebooted (x2).  I was given back my orginal Visual Style that TuneUp Utilities 2010 had put up.  That and the fact that the 'Edge' skin I tried to put on the desktop was mostly there (no taskbar or start menu).  This makes me think that it may be ja WB originated problem.  Maybe, it has a problem with something I am not aware of.  Maybe the fact TUU has this Visual Sytle functions or could be my general setup that WB is expecting.  A .DLL or other support file that isn't there?

I definantly see why this "trial" WB or other Customizing functions might give way to some problems.  Hope a solution shows up.  WB was one of the main apps I bought the OD Subscription on.|-)

 

Reply #23 Top

Quoting Impatient133, reply 12
I took your advice and downgraded to 270, and no changes resulted.
End of Impatient133's quote

Thanks for that info, I was thinking that it is better to wait and see if it truely is a Nvidia software issue.  I would wait until thier newer update before going backwards.  I would though, if I see that it is riot with troubles.  I was hoping someone would verify that it work under a downgraded driver.  I still would like to see this ncidia issue the other poster talked about.  I am not changing my card for nothing at this point.

Reply #24 Top

Quoting Jafo, reply 21

Almost a dead certainty that is your problem...
End of Jafo's quote

 Hmmm, here's to some verification from DC 133 that he has TU U or some other Visual Styles kind of functions all ready running.  I hope to hear from the TU U support on how to "turn off" the Visual Styles functionality.  Not willing to part with the whole thing though.  I rather depend on some of it.  Beside, it was there first before WB 7.  Seniority you might say...;)

Reply #25 Top

Quoting BarJabba, reply 24
I hope to hear from the TU U support on how to "turn off" the Visual Styles functionality.
End of BarJabba's quote

Prior to my comment I had a look at TU-U and its Visual Styles option....it 'should' be removable...and certainly is inferior to the capabilities of WB.  I expect it's another rendition of ye olde dll 'hack' that allows unsigned Visual Styles, something neither sanctioned nor supported by MS.