WB failure to launch

I just purchased and installed Windowblinds 7 on Windows 7 32 bit. I used the Impulse program to download and install. 

Every time I try to start WB it crashes. "WindowBlinds 7 Configuration APP has stopped working." It shows the program and sometimes will start to show the themes at the bottom and then stops with the above message. I've updated and verified and run as administrator without luck. WEI score 4.0. Intel pentium 4, 3.2GHz. NVIDIA GeForce 7600 GS. 4 GB RAM. 

Any thoughts or suggestions?

8,962 views 32 replies
Reply #1 Top

First question, did you have the free version and did you uninstall it prior to installing the full version?

Second question, have you been able to use WindowBlinds to apply any skins?

If you haven't been able to apply any skins, I will take it that you are still seeing Windows 7 GUI.  Use Impulse to uninstall WindowBlinds, run a clean up program like CCleaner, turn off your A/V and other security programs and reboot.  Reinstall using Impluse, reboot and turn back on your A/V and security. 

If that doesn't work and no one comes along with any other ideas you may have to email support@stardock.com.

 

Reply #2 Top

Thanks for the reply.

 

Clean install full version.

WB will not even open to apply or look at anything including settings.

Tried turning off security programs and clean up. Uninstall/reinstall and still crashes out of the gate.

 

 

Reply #3 Top

If you haven't done so already then email support@stardcok.com and start a trouble ticket. They will be able to work with you and get this issue resolved.

Reply #4 Top

Is this 7.0 or 7.01?

Do you have any additional themes included as well as it may be a problem generating the thumbnails for them.

Reply #5 Top

I have started a ticket.

The version would be 77.01.022_02.04.2010 for the .impulse file.

Versions of wbconfig.exe and wbload.exe are both 7.0.0.0. SevenConfig.exe is 7.0.1.0 version 7.01

I haven't been able to load the program to add any themes.

 

Reply #6 Top

Do you have any other theme software installed, or other applications that might interfere with WindowBlinds, specifically things that would load into explorer?

Reply #8 Top

disable nview

Reply #9 Top

Thanks for the idea.

I've checked and I don't have Nview.

The only Nvidia service running is nvsvc for the display driver and 2 Nvidia precesses nvvsvc.exe for driver helper service. Nothing Nvidia in the usual start up locations.

 

Reply #10 Top

Do you havre a process set to run at startup called nwiz.exe?  If so, try disabling it.

Reply #11 Top

No Nwiz.exe. The only service and process running are as noted above. The startup locations are devoid of Nvidia software.

 

 

Reply #12 Top

I got it working.

I uninstalled WB again, and used VistaGlazz 2.0 to patch the Uxtheme.dll. Reinstalled WB and it started working. For the most part.

I can't apply or view the stock Microsoft Aero Theme without it crashing. So right now there is no way to go back to original theme. Also when trying to apply a windows themes through desktop, context menu, personalize.  The colors don't exactly match anymore.

So, I'm one step closer.

Reply #13 Top

Spoke too soon.

Booted up today and WB crashed. Same error message. Can't get WB to start.

Well maybe Stardock support will be able to figure something out.

Reply #14 Top

As was mentioned in another reply, WindowBlinds doesn't not play very well with other GUI changing programs, especially ones that need to run a patch to work. 

Reply #15 Top

Actually if you read the rest of the thread, you would have seen that It wouldn't work at all before apply the uxtheme patch. Now It works on an off. It's back on now. I've changed the themes and add some to try. Still crashes with stock Aero theme. But now will come back because it remains loaded with the OS.  So this situation appears to be something different. As I stated above, there are no other GUI changing programs, aside from the patch which I just applied as an experiment and seems to have done some good. There is still something going on.

The program crashes when it starts and tries to load the list of themes.

Reply #16 Top

Did you upgrade to Windows 7 or install the OS fresh? If you upgraded....had you ever patched the uxtheme.dll before (while on XP) the upgrade. It's likely if you had patched the dll that the windows upgrade would have ignored the patched file and left it on the system.

My personal opinion is the upgrade path is always problematic.......I would always opt for a fresh install.

Reply #17 Top

It was a clean/primary install. I haven't had any problems with the OS other than a sound card driver issue.

Reply #18 Top

I uninstalled WB again, and used VistaGlazz 2.0 to patch the Uxtheme.dll. Reinstalled WB and it started working. For the most part.

 

I can't apply or view the stock Microsoft Aero Theme without it crashing. So right now there is no way to go back to original theme. Also when trying to apply a windows themes through desktop, context menu, personalize. The colors don't exactly match anymore.

End of quote

 

Any software that patches Uxtheme.dll pretty much guarantees you issues with WindowBlinds.  These patch apps also tend to not un-patch themselves as much as you'd like them to.  I would suggest checking the integrity of this file (I believe an SFC scan should work).

Reply #19 Top

You are missing the point of the theme patch. I applied that as a test after having the problem noted above. WB would not start at all!! The original install was clean OS and clean full WB install. No patches or other  gui theme programs, etc were on my computer. 

It was only after applying the patch that WB would even start. It pretty much works fine except for trying to apply or view the stock Aero theme.  And again this is after the patch. The program works after  and NOT before. So, it didn't guarantee a problem. It partially solved a problem and has giving me more information to try and track down the real problem.

But thanks for the information.

Reply #20 Top

The patched dll's are easy to remove. All the patching software does is rename the original 3 dll's and patch a copy. These remain in the same folder. To get back to the originals you can use the patching program or manually delete the patched dll's and rename the originals by removing whatever was appended to the end. Then reboot.

I've done that and WB would not start. Same problem as before. I've extracted clean copies of the 3 dll's and replaced the originals. Still WB would not start. I repatched the dll's and voila... WB starts.

The issue with selecting MS Aero still exists but there is a workaround. The color hue issue it turns out has to do with WB being loaded while trying to select an MS theme. If I unload WB and then use desktop context, personalize to select an MS theme it goes back to normal. While WB is loaded any MS theme selected retains the underlying color hue of the last WB theme running.

So, workable but not ideal. I'll keep experimenting. Just updating this for anyone else that might have this issue. I have not heard back from stardock support.

Reply #21 Top

It certainly sounds like the UI is having issues previewing the Aero Theme.  Does the same problem happen if you try to click on any of the other Aero themes included with WB such as Aero Colours?

Reply #22 Top

That's an odd thing as well. It can preview and load any other theme. Including added themes. Just not Window Aero, Microsoft. "WindowBlinds 7 Configuration app has stopped working".  It works on Classic,  Modified Aero, Aero colours, Aero Clay, Aero Metals, Aero Woods, AeroGlass, etc.

And once loaded WB config app will crash but WB remains loaded and can be instantly reopened from the taskbar or start menu. But initial loading from full unload my require a few of attempts.

 

Reply #23 Top

What language is your Windows 7?

I am wondering if the problem is loading up the list of OS provided ThemePack files.

Reply #24 Top

It's US English.

I was thinking along the same lines. Are you referring to MS provided themes or WB provided themes/skins? Are MS themes supposed to show up in WB list of Visual Styles? They don't.  I could remove WB or MS themse/skins for testing? Then I could add them in one at a time and see if there is a problem with anyone specific theme. I know how to remove MS themes, not so sure about WB skins.

Reply #25 Top

I am referring to the MS provided themes.  WB will be showing them in the substyles page when Aero is selected, so it sounds like the code that reads those has a problem with one of the themes on your machine.

Do you have just the standard included ones, or have you installed some additional themepacks from Microsoft?