[quote who="Lord Simonicus" reply="14" id="2006556"] Has anyone had any success in sorting this out yet? It's driving me crazy! Is anyone using Vista 64 Home Premium + Windows Blinds & not experiencing these issues?[/quote] Simple answer, No! I've had over 100 explorer 'stop working' errors with Wblind64.dll and even occasionally Wbhelp.dll since August last year, I'm beginning to wonder what Microsoft does with all the reports it asks me to send them. It interferes with AVG,
Caoimhghin
I too, am still experiencing this problem. There has been no peceivable improvement with v6.3. It mainly, but not exclusively, happens after Vista has loaded. One thing I have noticed is that after explorer crashes, AVG anti-virus scanner starts up although it isn't really running as such. This is quite weird and may be significant!
I have the same problem with WindowBlinds 6.1/6.2. In fact, in the past month Windows Explorer has crashed no less than 36 times with the same exception (0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT). The fault module being identified as WBLIND64.dll. The 'crash' is predominently at Windows start up, but not exclusively. System information: Your computer has a Windows Experience Index base score of 5.7 Your Windows Graphics Experience score is 5.9 WindowBlinds ve
I can assure you as well as Stardock that it is not a virus. After watching task manager as I change a skin screen.exe starts then stops almost instantly. It's My Secret I agree, it isn't a virus it starts as soon as you change the skin in WB. Right, just to make sure it wasn't an installation issue, I uninstalled WB, rebooted, reinstalled WB, rebooted then applied a skin. Screen.ex
Screen.exe is an app belonging to WB and instantiated on a skin change. Could you post your WB System Info here? -Mike [Stardock Support] WindowBlinds version : WindowBlinds 6.0 (build 32 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. (LG FLATRON L191
In task manager (XP) I have 22 instances of screen.exe running! According to Windows Defender these are all part of WB 6 and I assume these haven't been closed down when changing themes? If I unload WB, they still remain 'active'. I deleted all instances of these and restarted WB and I now seem to have only one instance of the screen.exe running again. I take it this is a bug?