WB not applying correctly

No titlebar, unloading/reloading doesn't help

I can install WB fine and 25% of the time, it's fine.  If I have to reboot my computer for any reason, there's a very high chance that WB will be messed up when it reloads.  Here are the problems:

1. Half the windows will have no titlebar or buttons.  These windows cannot be moved around or anything since there's no titlebar to grab onto.
(Screenshot: http://i72.photobucket.com/albums/i184/pumkin54/no-titlebar-2.jpg)

2. Dialog boxes will be blank with no buttons, titlebar, or text. In this screenshot, the black box in the center is a dialog box.  You can also see that my Firefox has no titlebar and half of the menu bar is gone with my wallpaper showing through.
(Screenshot: http://i72.photobucket.com/albums/i184/pumkin54/no-titlebar.jpg)

3. If I reboot my computer, a random theme will often be applied.  This is most often the skin called Diamond.  If I delete Diamond, a different skin will be randomly applied.  No, I do not have the option to randomly apply a skin selected in WB.  In this screenshot, the skin I have applied is called Organic.  For some reason, my taskbar and other random windows have Diamond applied. 
(Screenshot: http://i72.photobucket.com/albums/i184/pumkin54/not-applying.jpg)

Unloading WB does not help.  The theme will still be applied.  Applying a new theme doesn't help.  The old borked theme will still be applied.  Rebooting my computer only helps about 25% of the time.  I've installed and re-installed about a dozen times.

I am using the latest Nvidia drivers (175.19), as suggested by their automatic driver download.  This problem occurs whether I use old drivers or new drivers.  This problem occurs whether I use one monitor or two.


Here is my system information:
Your computer has a Windows Experience Index base score of 5.2
Your Windows Graphics Experience score is 5.9

WindowBlinds version : WindowBlinds 6.1 (build 97 x86 - Vista Edition)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(SyncMaster 2253BW/2253LW,SyncMaster Magic CX2253BW/CX2253LW(Digital)) 1 is attached to NVIDIA GeForce 7950 GT
(SyncMaster 204T/204Ts/204B,SyncMaster Magic CX201Ts(Analog)) 2 is attached to NVIDIA GeForce 7950 GT

Wblind.dll         2008/05/06 15:25:20
Wbsrv.dll         2008/06/13 11:24:12
Wbconfig.exe         2008/04/29 21:02:32
Wbload.exe         2008/04/28 11:35:14
Wbhelp.dll         2008/04/28 11:35:07
Tray.dll              2008/04/28 11:35:21
Wbload.dll              2008/04/28 11:34:28

 
Thanks very much for your help.  I've had this problem for about 6 months now and finally grew fed up enough that I uninstalled WB for a month.  That's the longest I've gone without it in about 5 years...  I can't stand it!
17,610 views 38 replies
Reply #1 Top
Do you have vView running? It doesn't play well with WindowBlinds.
Reply #2 Top
Along with disabling nView you could also update WindowBlinds by clicking on the blue Stardock orb (top left corner) in Impulse and check "Show pre-release versions". The latest build is 100. Perhaps this will fix it.
Reply #3 Top
I don't have nView running. I never really understood what it was for, so I never used it. I double checked startup programs, and running processes and services just in case. No nView.

I'm installing Impulse now. I was still using Stardock Central. (I had the WB problem before I installed SC, which I only used for some DLL error when using IconPackager). I'll let you know if that helps. Thanks!
Reply #4 Top
Ok, that didn't work. I waited 24 hours to test it out and 4 reboots and several borked interfaces later, I've had to uninstall WB again. I'm still having the same problem.

Does anybody else have other suggestions? :(

Edit: That being said, are there any other programs that allow you to skin Vista? Maybe I should just try one of those. I've been struggling with this WB bug for about 6 months now and am really just exasperated.
Reply #5 Top
Could you please post the WindowBlinds system info again and if you haven't already done so, email support@stardock.com and start a trouble ticket.
Reply #6 Top
The system info is in the original post. I've uninstalled WB (again), so I can't provided an updated system info but nothing much has changed.

I didn't realize I could open trouble tickets. I'll do that next!
Reply #7 Top
The system info is in the original post
End of quote

That was build 97.
you could also update WindowBlinds by clicking on the blue Stardock orb (top left corner) in Impulse and check "Show pre-release versions". The latest build is 100. Perhaps this will fix it.
End of quote

I thought you had updated to build 100.
Reply #8 Top
I did update. And had the same problem. And so I uninstalled it. So I can't provide an updated system info. I suppose I could re-install, grab the system info, then uninstall again, and do the requisite reboot... That seems silly to me, since the problem is occuring on both builds. The information I originally provided is just as pertinent?
Reply #9 Top

It [the second post of sysinfo] would have helped to ascertain that you got the correct files the second time round.

Open the help [trouble] ticket if you haven't done so already, and wait for a response. :)

Reply #10 Top
Ah, I see. Well, I opened a ticket. I'll let you guys know what response I get from tech support. Thanks again for your help so far.
Reply #11 Top
Hey, I've been following this thread and I thought I'd chime in here.
I think it more than a coincidence that you have described the problems I'm having with WB EXACTLY! Same thing has been happening to me ever since I've upgraded to OD 2008. I kept thinking maybe the next update will fix it, or maybe it was just my system, but when I saw your post I said "Ok, I have to do something about this" So, I emailed Stardock Support last week, but haven't got a response yet.
Anyway, I recently got a new hard drive and I reinstalled a fresh copy of Vista Ultimate. I reinstalled WB on it and guess what... SAME PROBLEM! So, I don't think its a problem with my computer, but if its not then what could it be? I've tried cross referencing my stardock and wincustomize accounts, and I made sure the email was the same too. Nothing worked.
The problem seems account related, or some kind of anti-piracy "feature" to keep people from stealing window blinds. I bought Object Desktop Ultimate, but maybe it's getting confused, or something on my account is messed up? I don't know. Anyway, that's my theory. I'd like to hear what you guys think.
Reply #12 Top
I'm still waiting for a response from the WB people. I sent them my dxdiag and bigger screenshots so they can really see what's going on. I'll keep you updated.

But I also have reformatted my hard drive and re-installed Vista. That's not the problem. I've tried it with old graphic drivers and new drivers. It doesn't matter if it's one of the only programs installed or if I have 30 programs installed. This is a problem I've been dealing with ever since I switched to Vista, I think. It used to occur occasionally, so that I just thought it was a fluke and forgot about it. Now it happens on a daily basis to the point where WB is no longer useable. Some WB update along the way actually made it worse.
Reply #13 Top
pumkin, have you tried installing WB from stardock central? It may be an Impulse issue. I tried doing that and it said my accounts needed to be 'merged'. I just emailed support back and asked them to do that. Haven't heard back yet, but maybe that will work for you.
Reply #14 Top
I only installed Impulse last week and I've been having this problem for like 6 months. I've tried installing WB using a manual download, from Stardock Central, and Impulse. It doesn't make any difference that I noticed.
Reply #15 Top
Hi, I am having much the same problem as well except WB4 files called Personality pop up in every opened program just about and I am thinking of giving away Window Blinds. I started a thread about it today but concentrated on the WB4 files. love Malcolm
Reply #16 Top
Hey, since I wasn't getting a response from support, I just phoned them. The guy at tech support said to try disabling AVG, and guess what... it worked! If not that, then something else must be blocking WB. If you have any anti-virus program, try uninstalling it and see if that helps.
Reply #17 Top
If that's really the cause of the problem, that's unfortunate. My virus scanner is more important than a skinning program :( I'll try it later on today and let you know if that solves the problem, though.

Thanks!
Reply #18 Top
If that's really the cause of the problem, that's unfortunate. My virus scanner is more important than a skinning program I'll try it later on today and let you know if that solves the problem, though.Thanks!
End of quote


turning off or uninstalling av is usually only needed during the install -

if it works during the install but starts going back to the way it was after turning on/running the av then depending on your scanner you might check it and see if it's blocking anything related to WB and see if you have an option to allow those files
Reply #19 Top
Here's the amazingly helpful response I finally got from Stardock support:

"Hello,

The latest version of WindowBlidns is 6.2. I would suggest removing the version you have with the following app:
http://sd.stardock.com/mike/apps/odnt_zapper.exe
and then downloading and installing the latest version through Impulse.
Please let me know whether this resolves your problem or if you have any additional questions."


Wow. Just...wow.
Reply #20 Top
Wow. Just...wow.
End of quote


bear in mind the files posted above are behind the most current which are dated in July

while the 'history' files aren't always up to date to tell what was done on newer versions, a lot of times the newer versions fix issues


you paid for WB which comes with updates....


following supports suggestion might help... not trying it won't help

just a caution... prior to running The Zapper... copy/move any downloaded skins you really want to keep, just in case... The Zapper removes all for the app selected to clean... it's not a 'run and you're done' app per se... you have to choose which app you want removed... so it won't remove everything stardock unless you tell it to...
Reply #21 Top
following supports suggestion might help... not trying it won't help
End of quote

It [the second post of sysinfo] would have helped to ascertain that you got the correct files the second time round.
End of quote

Wow. Just...wow.
End of quote

It is extremely difficult to resolve issues when suggestions are not followed or made light of. Members here and Stardock support are trying to help with your Windowblinds problem.
Reply #22 Top
I'm not making light of it. I'm expressing my lack of enthusiasm for the rote response. And I didn't write anywhere in my post that I wouldn't update, so I'm not sure why you're assuming that. Of course I update. I always do. And in six months, updating has helped nothing. He could have told me to tie my shoes and it would be as helpful. I waited almost two weeks for that response? To do something obvious that I would've done anyway? Sorry, but it feels more like a dismissal to me, rather than actual effort to find a solution. The update was released and he was like, meh, I'll just tell her to do that.

That's like another software that I use. No matter what problem anybody has, ever, the response is always "Try reinstalling."

It doesn't matter anyway. I can't even activate my WindowBlinds or IconPackager anymore. I opened a new ticket for that.
Reply #23 Top
Pumpkin, I totally agree with you. I got the same exact response from support - took over a week too. So, I just phoned tech support, and the guy a called was very helpful. The email support was the exact opposite. I recommend you try calling tech support. It's harder to dismiss someone when you're talking directly with them.
I don't have a very high opinion of stardock's support system right now. Waiting a week or two to reply to a problem is just complacent and lazy, especially when the reply gives you little or no help. It sends a message to the customer that you don't give a crap whether they have a problem or not. In my opinion, that's bad business.
Reply #24 Top
Patrick24,

There is no complacency or laziness involved. Support has been a bit backed up with Obj. Desktop issues and we're working hard as possible to get current. A lot of the issue is when e-mailing Support, we can't know all the details unless you state them. If you had said you had AVG in the beginning, we'd have advised you to try disabling it, and see if WB works for you.
Now, this is not your fault, but neither is it ours, and when you called in, we found the issue. You got your resolution, it's fixed, yet your still bashing Support?
Bad form.

Reply #25 Top
pumkin54,

You had reached a Activation limit, from trying to activate too many times. I've reset this back to 0, so you should now be able to activate.

Are you running anything like SpyBot, AdAware, etc.? If so, disable them and see if that helps. You might also try adding WindowBlinds to your anti-virus exclusion list, like patrick24 did.