Fences PRO Causing Explorer to fail and restart

I have had this problem also see Stardock Response here

https://forums.stardock.com/380097/page/1/#2603336

If Impulse verifies that Fences is installed correctly, I recommend sending an email to [email protected] referencing this thread.

Do you have anything else that would modify explorer, or any security apps running?

The new update fixed this problem for me

Windows explorer is now crashing sometimes on bootup for me now too. Even with this latest update. I restored an earlier disk image that had the previous fences version, and it still crashed. Seems to always crash when logging off and logging back on the same account in Win7 32bit.

I'm going to restore some older images and see what happens. I

Problem signature:

I forgot to say I suspected the app Actual Windows Manager  and was going to test logging and booting with this disabled.

So with Actual Windows Manager disabled on startup, explorer has not crashed yet.

So if this is the problem, I can see Stardock blaming Actualtools, and Actualtools blaming Stardock. How can this be fixed?

I can fix it by adding a 30 second startup delay to AWM.

It's not so much which one is to blame, as most likely it's both.  It's like both programs are reaching for the same donut and getting there at the same time.  Because of this, the donut gets knocked on the floor.  It's not exactly anyone's fault, but that doesn't help the donut.

I reinstalled Win7 with all the same software and there is no crashes or conflicts even with no delay. There was something wrong with that Win7 install.

Wanted to see if any updates and keep this topic active.

I do not have AWM and I am getting exactly the same issues of Explorer having to restart whenever change it seems something on desktop and the 3 times thing when reboot. A more detailed description by many others is at https://forums.stardock.com/380097

I am not yet using pro just evaluating the non pro version, I like Fences but not the nuisance of all the Explorer restarts.

I am not going to do a Win 7 reinstall, its easier just to turn off Fences and never have the issue except when Fences running.

Since I don't have Pro I assume that is why there is no option in Impulse to verify program or what someone else suggseted on the other thread Impulse doesn't list Fences (or any) in My Software other than some "Free version available's."   Impulse to me is just a nuisance it seems needed to get updates,  but think I got it to stop nagging me. 

I am a serious business user, I have no time or interest in TV and have never played any game - but I like Fences to help organize -

I also have 5 Samsung monitors all 22-24" But the issue seems to be common with Win 7 (I'm using 64 bit). My desktop is all on one so don't think that is any issue.

I think I recognize Stardock from way way back in my OS2 days and like many of the ideas.  But I have no time or interest in having to a computer "geek" I just need things that work.

As I recall like 15-20? years ago I liked Stardock's things but never used due to all the problems getting it to work right.  Back then OS/2 was far better than the first Windows which as I recall was about the only option vs DOS with no graphic GUI before the 1st Windows which was terrible vs stable and much better OS/2. Times have a changed for us old guys.

It's not enough to say "it's broke."

if you want a quick resolution to your problem, tell them WHERE/HOW it broke;  they can at that point (at the very least) know where to look for their "epic-fail."

If you've installed ObjectDesktop like I did (Fences-PRO is part of the suite)  as you can see the issue relates to "C:\program files (x86)\stardock\fences\DesktopDock64.dll"

....or does it?

As I worked my way through the list of programs that came w/ ObjectDesktop, I came to "Deskscape 3"  ---- this seemed to work; uninstalling it SOLVED my problematic annoyance of having windows explorer crash/restart everytime I went to right-click or interact with my desktop.  Also as I uninstalled Deskscapes, I INSTALLED the "Impulse Dock," as an extra step (thinking maybe desktopdock64.dll was part of <that> install/program option.   Whether it was my first or latter steps that resolved the issue remains to be said ---- however, at this point in time it is as of now "fixed."

Interesting.  And worth watching.