Blackkatt Blackkatt

Fences 3.0.3 fails to recover when explorer is restarted

▼

Fences 3.0.3 fails to recover when explorer is restarted

Windows 10 x64

https://goo.gl/photos/xxpdBsKX3EGvqYLD6
from Stardock Forums

Hi!

So everytime I restart windows explorer there is about 80% chance "Fences" don't recover (restarts). If I restart explorer once again most of the time Fences starts again ...

If I try to start "Fences" manually after it has failed.

I get  "Fences does not appear to be loaded. You may need to reinstall Fences" (see external link above)

 

UPDATE:

I created an easy workaround  :pout:

 

Follow these simple steps

1. open notepad

2. copy and paste

@ECHO OFF

TASKKILL /f /im "explorer.exe" /im "rundll32.exe"

START "" "C:\Windows\System32\rundll32.exe" "C:\Program Files (x86)\Stardock\Fences\FencesMenu64.dll",StartFences

EXIT

3. Save as LazyStardockDevs.bat

4. Double-click "LazyStardockDevs.bat" to restart Fences when it doesn't show up after you restarted explorer (or crashed) without having to log off / reboot!

 

Note: if you for some reason have other things running "as RunDLL32.exe" you would have to restart them as well.

fences
122,086 views 29 replies +1 Loading…
Reply #26 from Stardock Forums Top

If you are not using the new beta of Fences it might be a good time to try it.  It is available via teh Object Desktop manager and https://store.stardock.com/myaccount/products

Reply #27 from Stardock Forums Top

I've been seeing Explorer crashes a lot lately when Fences is running. The faulting module is DesktopDock64.dll. I'm running Windows 10 Enterprise, build 14393. I can recreate this crash by using certain functionality in Explorer, such as snapping an application to the edge of the screen or using the go-to-desktop button at the far right of the taskbar.

Faulting application name: Explorer.EXE, version: 10.0.14393.0, time stamp: 0x57899981

Faulting module name: DesktopDock64.dll, version: 3.0.3.0, time stamp: 0x57dc461f

Exception code: 0xc000041d

Fault offset: 0x0000000000085327

Faulting process id: 0x18f0

Faulting application start time: 0x01d2be8156e4d7ce

Faulting application path: C:\WINDOWS\Explorer.EXE

Faulting module path: c:\program files (x86)\stardock\fences\DesktopDock64.dll

Report Id: 50ffa348-3d04-4705-a009-5c7e532f93ed

Faulting package full name: 

Faulting package-relative application ID:

Object Desktop - Get all of our enhancement utilities in one suite
Reply #28 from Stardock Forums Top

Quoting MaximusMMIV, reply 27

I've been seeing Explorer crashes a lot lately when Fences is running. The faulting module is DesktopDock64.dll. I'm running Windows 10 Enterprise, build 14393. I can recreate this crash by using certain functionality in Explorer, such as snapping an application to the edge of the screen or using the go-to-desktop button at the far right of the taskbar.


Faulting application name: Explorer.EXE, version: 10.0.14393.0, time stamp: 0x57899981

Faulting module name: DesktopDock64.dll, version: 3.0.3.0, time stamp: 0x57dc461f

Exception code: 0xc000041d

Fault offset: 0x0000000000085327

Faulting process id: 0x18f0

Faulting application start time: 0x01d2be8156e4d7ce

Faulting application path: C:\WINDOWS\Explorer.EXE

Faulting module path: c:\program files (x86)\stardock\fences\DesktopDock64.dll

Report Id: 50ffa348-3d04-4705-a009-5c7e532f93ed

Faulting package full name: 

Faulting package-relative application ID:


End of MaximusMMIV's quote
Please update to the beta 3.0.4.x and let us know if you still see the errors.

Reply #29 from Stardock Forums Top

This still happens in version 3.0.4.12.

The workaround Blackkatt provided works fine, but it would be better if Fences could recover itself.