Windowblinds 6 problem

Hi. I've installed wb6 and it shows the skin in the prev window with no per pixel but the bmp frame with its magic pink. The skin then applys in total classic mode.

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

Wblind.dll            2007/09/27 17:47:20
Wbsrv.dll            2007/09/24 19:08:43
Wbconfig.exe      2007/10/01 17:35:33
Wbload.exe         2007/09/27 17:47:44
Wbhelp.dll          2007/08/27 11:54:07
Tray.dll              2007/09/12 17:58:21
Wbload.dll          2007/09/26 14:42:28
Screen.exe         2007/10/01 11:23:24

Can anyone help me? also, after reboot, it asked to reboot again and then to reboot again. The only way i can stop getting this reboot message is by double clicking WBInstall32.exe in the wb folder and then the main exe

13,114 views 16 replies
Reply #1 Top
Sounds like something went very very wrong with the install. I hate to resort to the lame canned one but I'd suggest uninstalling and reinstalling.

Reply #2 Top
He's done it atleast two times from what he told me on MSN D:
Reply #3 Top
Oddly the same thing happended with 5.5 aswell. I've uninstalled, rebooted, installed and rebooted twice after that and repeated the process 3 times. The 3rd time i uninstalled spybot as the pop up to reboot mentioned spyware progs but it was never active or running in the backround. I am still getting the reboot screen on startup every time now. What I have noticed, if its related, is that after i did a windows update a couple of week ago and updated my NVIDIA drivers, i now have a NVIDIA control panel option on right click. Spybot gives a description of each startup item and each of the 3 new NIVIDIA startup procedures states that i can disable them, if user wishes. 1 of the startup descriptions for an NVIDIA process states: NVIDIA Driver Helper Service - installed when you change from the WDM drivers to nVidia's latest versions but not requied. Extreme shutdown delays can be encountered with this service active, but no adverse side effects with it disabled. NOTE: If using drivers other than nVidia's, such as Asus, this service may have been renamed to reflect that.

Now i noticed it states "when you change away from the WDM drivers to NVIDIA's latest drivers" am I right in thinking the its the WDM drivers i need? but if this is the case and the change away has only been recent, what would explain wb5.5 having the same issues?

The only thing i can now think of doing is taking off spybot again, uninstalling wb6, doing a complete reg and junk file clean and then installing wb6 again.
Reply #4 Top
Tried the reg clean and junk file clean, repeated everything and still getting the same issue
Reply #5 Top

The Please reboot message (even after you have rebooted) is generally caused by something blocking the WB service from running at startup. When you see that message, it's WBConfig complaining because it can't find the service to pass off the skinning duties.

Try running this and see if that helps:
http://sd.stardock.com/mike/apps/reinstall_wb_service.bat

The likely source of this service not running on startup, as you mentioned, is antispyware apps. Some tend not to like applications running at startup and will take whatever precaution to prevent that from happening. Sometimes the antispyware app(s) may have an exclusion list, but other times, the only workaround may be to uninstall them.

-Mike
[Stardock Support]

Reply #6 Top
. . .is spyware apps
Did you mean "anti" spyware apps?
Reply #7 Top
@milksama Thank you for you replying to me. I reinstalled wb6 and then ran the bat file u gave me. After i press any key, like is asks, i get an error message saying it cannot locate VistaSrv.exe in the folder and after looking, it is not there. It then throws me into classic mode. It seems this exe is not installing for some reason but im almost sure i have seen the exe when i was running wb5.1. Should i reinstall 5.1, make a copy of the exe, unistall, install wb6 and then copy this exe into the folder b4 activating the bat file?
Reply #8 Top
Did you mean "anti" spyware apps?


Wondering about that m'self, as I've had gremlins mucking about in my WB6, too, and they need exterminated! So far, I've set winamp not to run at startup, and that fixed it for now. Try going to "msconfig" and startup and disabling things that run at startup that aren't needed and see what happens. Worked for me. Thanks, Neil and Mike!   
Reply #9 Top
grr now i cant activate it anymore
Reply #10 Top

Did you mean "anti" spyware apps?

slip of the tongue... honest

seldomseen: Awesome, glad to hear things are working better for you.  

Stee03: You shouldn't need to activate again if you need to uninstall/reinstall in the future. Just save the sig6.bin file, and that should prevent the need to reactivate. I have reset your activation count though, so you should be good to go again.

As far as I am aware, you will want to be able to find a VistaSrv.exe file in your WB folder. I'm not too sure why you aren't though. Edit: I assume you're on XP? I missed that part of your WB Sys Info.

-Mike
[Stardock Support]

Reply #11 Top
milksama: I tried using wb5.5's vistsrv.exe and still didnt work. Im running vista. It seems its not installing correctly from stardock central but every installs and works fine when i use my 5.5.exe
Reply #12 Top
Ok i put 5.5 back on then installed 6. Everything went perfect. Rebooted and wb6 started up but im back to seeing magic pink on the prevs and skins applying in classic mode
Reply #13 Top

Stee03: Have you at any point set SDC to run in XP compatibility mode?

As it looks like you are installing the XP build on Vista.

You will need to right click loader.exe and sdcentral.exe in the c:\program files\stardock\SDCentral folder and ensure that run as XP is not set.

In the future could you post the entire troubleshooting text as it includes the build information of WB which would have allowed us to spot this much earlier.

Reply #14 Top
neil: neither of the exe's are set for anything. What are you reffering to about the troubleshooting text?
Reply #15 Top

The WB troubleshooting text has a line above what you posted which contains the build number of WB.

Could you run SDC and see what build number it shows in help->about.  Is it build 160?

Reply #16 Top
Neil: problem solved and wb6 running fine. It seems it was SDC even though i just updated it. I installed from wb6.exe and its perfect. So if anyone has a similar issue I would say it was SDC missing files on download or something. Ive only ever had probs with updating wb's from there and not through exe installs

*update I spoke too soon *