Anyone else seen this?
Published on September 21, 2007 By Asmodean_dk In

First of all a disclaimer: I am not at all sure that the following problem is related to WB - nor do I blame Stardock in any way, should it be. I am aware that this is a beta version, and as such cannot be guaranteed to function 100% in all areas.

Then to my problem:

Yesterday afternoon, I updated WB to 5.92.090. SDC prompted me to restart my computer, and I did. Upon restarting, Windows Data Execution Prevention (nice name for a service, eh?) closed Windows Explorer. I went huh??? But then Windows Explorer started again the next second, and all was fine.

Since then, though, about 50% of the times I reboot my computer I get the exact same thing. Windows Explorer gets closed by Windows Data Execution Prevention, but starts again right after.

Anyone else seen this?

Asmodean
Comments (Page 5)
6 PagesFirst 3 4 5 6 
on Oct 05, 2007
boot shot...   

on Oct 05, 2007
It's begining to seriously make me board ... I think about 90 % of my skins are concerned on 2 different PC's (well nearly the whole apart from the very new ones drawned for WB6 in fact ...)

I'm on the way to do a definitive roll back to WB5 and do not move from it. Really board of spending days and days on testing, while i'm not sure on the other side (mean Stardock) the problem is really taken seriously.
In fact what brings WB6 better than WB5 ?? For me on XP and with my prefered skins and suites, i don't really know ... apart troubles ...
on Oct 05, 2007
C'est vrai, mon ami. Bon chance.
on Oct 06, 2007
My little finger is telling me we'll probably get soon THE correction   
on Oct 06, 2007
One can only hope. This is at reboot today... [grumble...uninstall LEXAN, reinstall LEXAN...back in business...'til...?]
on Oct 06, 2007
seldomseen -

Have you tried going into the Transparency & Blur section, resetting everything to defaults, deleting all the skin cache files (~*.*, *.wb4, *.*~), and then rebooting? That has restored the StartPanel to the Preview Window here & corrected the display issues I was having after the initial update. For reasons unclear, settings were changed in that section during the update (not by me) and the update process does not appear to handle or update the cache files properly - seems to me it would be smart if they were deleted by the update engine.
on Oct 06, 2007
Daiwa,
Thanks a bunch!   Running out the door at the moment... snow's loading tree branches over the house & I've got to deal w/that first.. where's the rest of summer!!   
on Oct 07, 2007
Booted today a.m. and no problem! Could it be that the prob. only occurs on "restart" and not on "shut down" then a later "start" from the power-on switch? I'm going to try both of these now and get back with the results (if my short-term memory will comply...)
on Oct 07, 2007
Y'all could just do what I do and never shut down or restart your computers... 

Definitely a bizarre problem... Are there any similarities in terms of system specifications that might be leading to this being a common problem?
on Oct 07, 2007
Y'all could just do what I do and never shut down or restart your computers...


I'd like to, but local DSL service and local intermountain power going off and on all the time preclude that. My APC is only as good as its battery, and that's good for about 1/2 hr. to shutdown if electricity goes out. Solar, maybe? hmmmm... Built a residential solar power system once for about $1000, but the batteries had to be replaced after each year's use.

As for this non-skinned taskbar deal, a "shut-down/restart" just now resulted in an unskinned taskbar and startmenu again. Now to uninstall/reinstall LEXAN to start the day.   

...and so it goes...
on Oct 07, 2007
Everyone here is running WindowsXP. Curiously, it doesn't appear that users running Vista are experiencing this problem. It seems like since the beta update that moved the skin directories to the Shared Documents folder, when WB6 loads at startup, it cannot locate the graphic files necessary to skin the taskbar and start menu. Why other elements remain skinned is a mystery to me. I'm just wondering if the changes made to WB6 so it could receive Vista certification somehow broke something in the program on XP machines. Just my $.o2 worth.
on Oct 07, 2007
It's not only on startup that's things are broken BillyBob, but about every (well i'd say around) 30 mn or something like that ...

BTW, Neil had send me yesterday a new wblind.dll file which i'm testing, and good news (for now) that problem seems to be fixed (i cross fingers it will keep on same way, but with all tests i did, i think it will be ok ...)
on Oct 07, 2007
when WB6 loads at startup, it cannot locate the graphic files necessary to skin the taskbar and start menu. Why other elements remain skinned is a mystery to me.


That's the deal, huh.

Now it works...
on Oct 07, 2007
Neil had send me yesterday a new wblind.dll file which i'm testing, and good news (for now) that problem seems to be fixed


Same here. Glad you having good results. I used that dll/old_dll method, also. It worked. Then I rebooted and it it didn't work. Reset theme in WBconfig window[Delete Visual Style/Add Visual Style...getting rather adept at this manoeuvre...], Shut Down. Started from Power-Up button on case. WB I had applied before Shut Down was alive and well! Shut Down, Started from Power button again. No joy. No skinned tb or sm, even with new/test dll. [Delete Visual Style/Add Visual Style...Delete Visual Style, Add Visual Style...delete...add... ...]
on Oct 07, 2007
You'all are working so hard to remedy this spook. Would it at any point be beneficial to perhaps offer-up a small animal in sacrifice?




[edit: stardate: 30min. later: Seems to be working well, now! Been thru two Restarts and the taskbar/Start Menu runs every time!]

[...a hush falls over the crowd...he restarts, again...]

Now for this!
6 PagesFirst 3 4 5 6