I found a workaround for getting WB working in my firefox, by using "old" menu bar instead of dropdown menu bar.

1) The app name

     WindowBlinds

2) The OS you are using

     Windows 8.1 Pro with Media Center

3) The theme you are using

     Any WindowBlinds theme

4) The problem you have encountered

     After reboot I cannot log back into my computer.  I enter the login info and Windows takes me back to the launch screen.

5) If you did report it to support a ticket number would help.

     Not reported to tech support

Just a quick report.

I am using Celestia, which is a free (open source) astronomy software. I am also running WindowBlinds 8.02 on Windows 8.1. When the Win8 skin is selected, Celestia's title bar and menu are not displayed properly (a screenshot is attached). To fix this, I launch Celestia, then I launch WindowBlinds and switch to the Default Theme. The application is then properly displayed. The menus will keep being displayed correctly after switching back to the Win8 theme. Yet, when Celestia is relaunched, the artifacts reappear. Celestia can be obtained here:

http://sourceforge.net/projects/celestia/files/Celestia-win32-bin/1.6.1/celestia-win32-1.6.1.exe/download

Thanks!

1) Adobe Reader XI

2) windows 8.1

3) all of them

4) the program is not skined.

This is normal as Adobe reader uses a sandbox by default which prevents WB from being able to access skin files, so it leaves it as Windows 8 themed.

1. chrome beta

2. windows 8.1

3. all of them

4. memory leak when loading pages causing browser to stop responding. with memory on one of chrome processes reaching 2.7gb

sometimes happens while listen to music on youtube video and facebooking and would happen alot throughout the day.

telling windowblinds not to skin chrome fixes the problem. 

extensions in chrome

adblock plus

weatherbug

roboform.

smooth wheel scroll.

disabling extenstions had no effect on the memory leak.

!. Virtualbox

2, Windows 7 64 bit

3. Endeavour, I haven't tried any other themes.

4. The title bar is completely invisible including the close, minimize, and maximize buttons. The title and little icon do show up, though. This problem persists even if I exclude it from themeing. I even tried excluding the VboxSVC application, and it didn't work.

Hi, I'm new here and a happy new year to you all. Good information here and really nice stuff.

I'm using windowsblind, but only the Default Theme is working. Trying all other themes and with all programs/windows explorer, the minimize, maximize and close buttons aren't visible. Only when I hoover with my mouse there and just click, I see them very briefly and the command is executed.

I already tried a lot from the information I got here and on the wincustomize forum (reinstalling WB, reapplying the themes, restarting etc), but I'm stuck.

I have an Object Desktop subscription with all the programms installed from the suite and so far those do run fine so far. Running W8.1 x64. BTW I filed a ticket about this just now.

Update:

Stardock support send me a special bat file to uninstall wb8, after a restart and a new install of wb8 everythings works now

Windows 7 64 bit Ultimate, OD+ 2.1 and latest WB.  When I click the Start icon I get only half the start menu.  The right half is cut off.  This only happens when running a non-MS blind in WB.  Sometimes, if the PC is slightly slow, I can see it actually paints the entire menu and then blanks the right side so it's completely transparent.  I haven't found a Stardock or 3rd party blind that doesn't exhibit the problem.  Reinstalling OD, WB and even WFx has had no effect.  This problem did not happen when I was running Vista 64 bit Ultimate, but that was with the Vista version of WB.  Stardock support was unable to help.  My workaround is for the strt icon to invoke the start menu through a script rather than the built-in OD docklet.

Anyone else experiencing this?

1) Anuko World Clock (http://www.anuko.com/world_clock/)

2) Windows 8.1 64bit

3) Lantana (but applies to any skin)

4) With both WindowBlinds 8.02 and worldclock loaded, windows explorer continuously freezes display of the taskbar (no taskbar)(taskbar set as unlocked and autohide) with high cpu useage of > 50% for explorer.exe. If explorer.exe restarted in task manager then the taskbar unfreezes and becomes available again. However, as soon as a process uses explorer.exe the freeze and high cpu issue recurs and, usually, I have to go into Task Manager and restart explorer.exe to regain the task bar. Occasionally, explorer.exe can recover on its own but if it does it requires several moments waiting, and then more often than not, it just remains at high cpu and an unusable task bar. The system itself does not freeze, I can continue using programs etc, I just have no access to the taskbar and/or explorer.exe directly and, of course, responsiveness is affected due to high cpu usage.

The only way I was able to get the two programs to work together was to completely exclude the skinning of explorer.exe in WindowBlinds configuration - tried various and sundry combinations of exclusions but the only one that worked was to exclude the entire thing. Excluding any or parts of worldclock did not work. Of course, excluding exporer.exe meant no taskbar skinning or skinning of any other explorer.exe system windows. Finally I disabled Anuko World Clock from auto starting, removed explorer.exe from any exclusions and, voila, everything under Windows 8.1 and WindowBlinds 8.02 now skin nicely with no further hangs of the taskbar or high explorer.exe cpu usage. Has been working stably for a couple days now. But as soon as I start-up or reload Anuko World Clock, the tasbar and explorer cpu issues are back.

Conclusion: Anuko World Clock, however it hooks into Windows Explorer, is not compatible with WindowBlinds. As a note, prior to using WindowBlinds I encountered no issues with World Clock and have used it under XP, Vista, Win7 and Win8/8.1 for a few years now.

 5) Issue not reported to either vendor.

1. Anuko world clock

2. W8 Pro 64 bit

3. Innomatum

4. Same exact problem as beboyer listed above

5. Issue not reported