WindowBlinds5 / WinFX3 block logging out

User must negotiate 1 or more 'end program now' dialogs when logging out

WindowBlinds5 / WinFX3 appear to be intermittantly preventing programs from exiting during logout.  I get from 1 to 5 requests to force termination of applications when logging out if this happens (usually 1 or 2).


This intermittant problem appears to happen more often when WinFX is enabled, and/or FUS is used.  Most commonly, it is Windows Explorer and WindowBlinds that get stuck and put up dialogs to force closure alternately, as if each is waiting for the other to exit.


This problem was also apparent with WB4/WinFX2.


WindowBlinds 5.0 System Information Report:


STATUS : WB+ SRV+ HLP+ UI+ TRAY+


WindowBlinds is installed correctly on this PC.


WindowBlinds appears to be activated on this PC


You have Stardock WindowFX running.  Please be aware that WindowBlinds 5 is not compatible with WindowFX 2.11 or 2.19.  WindowFX 2.5 beta which is compatible with WindowBlinds 5 will be released later this year


Your machine supports per pixel borders on WindowBlinds skins.


You have one monitor in total.


(L768) 1 is attached to RADEON X800 Series 


Wblind.dll      2006/03/21 12:33:46
Wbsrv.dll      2006/02/05 11:58:22
Wbconfig.exe      2006/03/19 13:33:44
Wbload.exe      2006/03/13 16:54:12
Wbhelp.dll      2004/09/18 15:37:00
Wbui.dll      2005/12/06 20:29:06
Tray.dll      2005/11/02 12:28:26


 

4,483 views 2 replies
Reply #1 Top

WindowBlinds doesn't have a process to end.  What is the exact text of the message about WindowBlinds?

Reply #2 Top
This is probably related to WindowFX - it's been reported by multiple users and I see it about 8 out of 10 shutdowns, with a message about explorer not responding and have to kill it (often twice) and then a message about the Hidden Fax Window not responding & have to kill it, then shutdown finishes normally. Doesn't happen when WFX isn't running, but I like WFX so still use it. The problem isn't destructive, but can be annoying.

I don't believe this has been resolved yet; at least the WFX changelog doesn't mention it.