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 6)
6 PagesFirst 4 5 6 
on Oct 07, 2007
Hope this gets fixed, I'm having the same problem.
on Oct 07, 2007
Restarted three times now. Waiting to do a "Shut Down"/"start" 'til this eve and a.m. So far, so good.
on Oct 08, 2007
It's not only on startup that's things are broken, but about every (well i'd say around) 30 mn or something like that ... you can check that in launching either the WindowBlinds Configuration Panel either the Desktop rightclick / Properties / appearence, where (if the skin is no more correct) you won't see the Startmenu or the Taskbar, though of course on reboot it won't be correctly displayed ...


BTW, for me the wblind.dll Neil send me is still working fine for THIS problem ..."NameOffSkin.uis_BLOCK.WB4" seems to be no more overided by a wrong rebuild

on Oct 08, 2007

BTW, for me the wblind.dll Neil send me is still working fine


Same here!   
on Oct 08, 2007
Maybe Neil can hook me up with the updated wblind.dll. If it's working for you folks, I'll give it a try.
on Oct 08, 2007
Psst!  Yeah you.  You got the good stuff?

  Whaddya think?

Is it pure, uncut?

  I got it straight from teh lab.  It's good shit.

Can you hook me up?

  Man!  If I got caught passing this stuff out it'd be my ass.

But I NEED it man!

  Chill.  You'll get it when you get it.

I heard the pusher is blind.

  Something like that.

You know when it'll hit the street?

 No one know that.  But he pushes stuff pretty fast these days

I heard that.  And I heard his stuff is always worht waiting for.

  He's had soem bugs in his shit before but it all works out.

Cool man.  Thanks.  I guess I'll wait.

  Not much else to do.

Peace.

  Peace

      
on Oct 08, 2007
This has been posted somewhere else or maybe here but there's so many threads about this I lost track.

It worked for me.

If you have access to SkinStudio 6 you can open the skin, save it, apply it, and it heals. To me, this supports a theory I read: something gets corrupted (cache?) & saving the skin overwrites the bad thing with a good one (refresh?) I'm trying to be as generic (geriatric?) as possible.

Hope it helps.
on Oct 08, 2007

We have put a new beta on OD which should resolve this problem.

on Oct 08, 2007
ROFLMAO
on Oct 08, 2007
Go to: System properties -- advanced tab -- settings -- data execution prevention:

be sure to check: turn on dep for essential windows programs and services only.

remember to apply -- and to restart. That should do it.
on Oct 10, 2007

We have put a new beta on OD which should resolve this problem.



Yep that's Ok for Startmenu and Taskbar   

Now still remaining that:

In another way i've also noticed that some (not so old skins) which are "qualified" as Perpixel UIS2 skins, are skinning correctly the ShutdownDialog panel but not the LogoffDialog panel ... It's pretty strange as both are defined the same way in the .uis file ... (yep it's another weird trouble )

6 PagesFirst 4 5 6