If you have experienced BSOD then Windows will have pointed you to the offending component on reboot.  I suspect you have defective video drivers and the bug in them is only being shown up by WindowFX.  WindowFX itself is not capable of being the root cause of a BSOD (only kernel mode things can cause a BSOD)

You must remember this is beta software and it is expected there will be bugs.  If you are uncomfortable with the possibility of there being bugs then do not use it.

Regarding missing windows, that is all linked to an issue with close animations.  Disable those and it should be fine.

This is a wonderful update to a great app!

I'm particularly happy to see the dimming/fading of inactive windows. I don't know if I had any influence on getting that feature added (see my thread in https://forums.wincustomize.com/166992), but I sure am glad to see that Stardock also thinks that it would be a useful feature.

One issue I experienced with that feature:  If I have two instances of the same program open (e.g., two Firefox windows), then selecting one window will bring both into spotlight focus. Clicking elsewhere will dim both.

Of note, I have x-mouse functionality activated such that a window achieves focus when the mouse is over it, but is not raised to the foreground (i.e., you can type in a window in the background). Don't know if that affects things. Perhaps an x-mouse toggle could be added to the WindowFX console?

Best wishes an congrats on a great Beta!!!

Unless I am missing something you have only reported a single issue which is missing windows.  As I explained this is probably linked to the close animation bug which can be avoided by not using close animations in beta 1.

There is an updated beta due to go out later today.  I cannot promise it addresses all issues as sometimes the information provided is insufficient to reproduce the issue but it has a number of bug fixes based on internal testing along with beta user reports.  It also adds in some new animations.

As with all betas it may still contain bugs.

Overall the feedback has been positive on WindowFX 4.

My laptop wakes up from hibernation instantly now. Thanks Neil.

Is there any intention of reinstating the window animations in XP?

Seems odd that WFX3 could do this but WXF4 tells us we need Vista/7.

Yowza - that's just scary.  That'll teach me for un-installing WFX3 before I installed WFX4.

OK, I've got v3.99 (v4.0 RC) installed and everything's working great except Windows Flick.

I have all options off except Windows Flick and movement momentum. The default options

for flicks are set ("Fill 50% of left screen on left flick", etc.) Then, I tried flicking an explorer

window left, right, top and bottom but nothing seems to happen. Flicking means dragging a

window and then throwing it around the screen, right? I'm positive that WFX is enabled and

that the window I'm flicking is a re-sizable one. Can somebody please tell me what I'm

doing wrong? I'm using Win7 Ultimate x64 by the way.

Thanks Neil, I got it! I didn't realize the flick is like the one on a touch screen.

I had been trying to drag the window and throw it around when all I needed to

do was make a flick using the cursor in place of a finger as I would on a touch

screen. Thanks very much for a great app! It's all the more reason for renewing

my OD subscription when the time comes around in January.