Seppchen: The last thing you posted was that the explorer crashing issue had stopped with the 6.09e(.126 build.

Is this not the case?

Yes and no, I am now using WB 6.09 (.135 and WB is still crashing. Apart from that, there are other WB problems which I reported in other threads. Like incorrect skinning of system windows, garbled icons in the notification bar. Upon your advise I reverted to the latest non-beta version, unfortunately at no avail. So I kept installing the betas hoping that at least some problems were resolved.

@Zubaz: I don't have unique system interactions on my two Vista x64 machines !!! Two different computers, with two different processors and two different graphic cards. Oh yes, maybe you are right: I use the same Samsung monitors my Vista boxes. I use WB and Adobe CS3 Master Collection, that's it. Nothing else.

OK! Wizard1956 is right, we should contribute in a positive way. Here is my first crash of today at 07:30. The unique interaction was that I tried to open a Windows Explorer window to view pictures. It seems that both Wizard1956 and myself are using Windows Vista SP1 (6.0.6001.18000). However, Wizard1956 uses Windows Vista x86 (WBlind.dll) and I am using Windows Vista x64 (Wblind64.dll).

@Neil: just a suggestion, maybe you should look at Vista SP1 issues. Then there are also other problems with SP1, like DestopX crashing when UAC is off. In my case UAC is off and I don't want to switch it permanently on. However, just a test I will switch UAC on for a day or so.

Problem Event Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 6.0.6001.18000
Application Timestamp: 4791970c
Fault Module Name: WBLIND64.dll
Fault Module Version: 6.1.0.0
Fault Module Timestamp: 47dbc0ec
Exception Code: c0000005
Exception Offset: 0000000000060eb6
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1031

Your computer has a Windows Experience Index base score of 5.1
Your Windows Graphics Experience score is 5.5

WindowBlinds version : WindowBlinds 6.1 (build 91 x86 - Vista Edition) - 64 bit OS

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
(SyncMaster 740N/179N,SyncMaster Magic CX721N/CX714N) 1 is attached to ATI Radeon HD 2600 PRO
(SyncMaster 740N/179N,SyncMaster Magic CX721N/CX714N) 2 is attached to ATI Radeon HD 2600 PRO

Wblind.dll 2008/03/17 12:45:20
Wblind64.dll 2008/03/17 12:45:05
Wbsrv.dll 2008/03/11 06:56:22
Wbconfig.exe 2008/02/20 13:52:33
Wbload.exe 2008/02/14 11:05:14
Wbhelp.dll 2007/08/27 11:54:07
Tray.dll 2007/09/12 17:58:21
Wbload.dll 2007/09/26 11:53:28
Screen.exe 2008/02/13 16:15:18

I use SP1, and this happened before I upgraded, too. Stardock gives great support for GC2, but for this, it's horrible. I've had this problem for about a month now, and the only "help" I've gotten was a suggestion to use the stable version. That would be great if THAT didn't crash too. You guys keep asking about what your doing at the time, which doesn't help much, cause with *ME* atleast, I get it no matter WHAT I do, run, ect. The problem is WB making Explorer crash. I can get it by looking at a picture, or talking to my friends on msn, or listening to music on iTunes, or typing stuff in Word. I can understand your trying to help, but your doing it backwards. You should figure out how to make WB NOT crash Explorer, instead of asking us what we do, as if we all trigger it by doing the same things. It's a great program, but the crashes make me wanna uninstall it, and forget I ever wasted my money on it. :/

Seems to be happening less frequently,only this one from this morning since 3/28.I just launched IE7 and Explorer said "c-ya later"
Problem Event Name: APPCRASH
Application Name: Explorer.EXE
Application Version: 6.0.6001.18000
Application Timestamp: 47918e5d
Fault Module Name: WBLIND.dll
Fault Module Version: 6.1.0.0
Fault Module Timestamp: 47dbc151
Exception Code: c0000005
Exception Offset: 00047850
OS Version: 6.0.6001.2.1.0.768.2
Locale ID: 1033
Additional Information 1: fd00
Additional Information 2: ea6f5fe8924aaa756324d57f87834160
Additional Information 3: fd00
Additional Information 4: ea6f5fe8924aaa756324d57f87834160

Extra information about the problem
Bucket ID: 697268706
I haven't changed anything on my end except a little processes management and dumping some HP bloatware.I hope others are seeing an improvement as well, maybe it's stabilizing. I have been reading the forums and it looks like there are/were glitches with XP on some peoples machines as well, so should we say that Windowblinds are not compatible with that OS either? I've come to the conclusion that 99% of the time computers do what we want and expect,the other 1% they do as they damn well please!(See my post about SDC forums)I can certainly see how this would interrupt ones workflow , seppchen,so I hope a solution is found quickly but I realize that Stardock does have a lot of irons on the fire.Patience,everyone. P.S. Fantastic job on Impulse!!!

This..sttill crashes explorer all the fucking time... can I just get a exe for a old stable version emailed to me? I was gonna quit uninstall, and go back to aero, but with vistaglazz SP1 in beta, I can't.

Neil (or anyone) I realize this thread focuses on stability mainly; but I would really like to know if any of the limitations below have been addressed:

https://forums.stardock.com/310458

Thanks!
Michael

Neil...one problem I am having is this. After applying a different skin...Windows gets skinned...but the taskbar doesn't and everything except my cursor freezes up...even Objectdock freezes. The only thing I can do then is reboot...and then the taskbar is skinned. I talked with Dave there a few days ago and we "thought" we figured it out but apparently not. I also have a support ticket on this with info sent to Milksama.

WindowBlinds version : WindowBlinds 6.03 (build 45 x86)

WindowBlinds is installed correctly on this PC
WindowBlinds appears to be activated on this PC
Your machine supports per pixel borders on WindowBlinds skins.

(Dell 2007WFP (Digital)) 1 is attached to NVIDIA GeForce 7600 GS

Wblind.dll 2008/03/31 12:21:20
Wbsrv.dll 2008/03/31 16:25:10
Wbconfig.exe 2008/03/30 11:29:34
Wbload.exe 2008/03/30 11:27:14
Wbhelp.dll 2007/08/27 12:54:07
Wbui.dll 2007/11/06 11:13:05
Tray.dll 2007/09/12 17:58:21
Screen.exe 2008/03/29 15:09:18