Windows 1909 Configure Fences doesn't load

from Stardock Forums

Here is a link to a video rather than trying to describe my problem. Any help would be most appreciated. 

In short same software on windows 10 1803 works fine, but on windows 1909 it doesn't work. 

https://youtu.be/bZYPwT1cfiU

Here is event viewer, pretty much get this same error when trying to perform configure fences. 

Application: SdDisplay.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.IO.FileLoadException

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" />
  <EventID Qualifiers="0">1000</EventID>
  <Level>2</Level>
  <Task>100</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2020-12-23T23:11:38.047370100Z" />
  <EventRecordID>20989</EventRecordID>
  <Channel>Application</Channel>
  <Computer>redacted</Computer>
  <Security />
  </System>
- <EventData>
  <Data>SdDisplay.exe</Data>
  <Data>1.8.0.1511</Data>
  <Data>5a8c1e1f</Data>
  <Data>KERNELBASE.dll</Data>
  <Data>10.0.18362.1139</Data>
  <Data>6a8e6b97</Data>
  <Data>e0434352</Data>
  <Data>00114662</Data>
  <Data>61d8</Data>
  <Data>01d6d980f71015d1</Data>
  <Data>C:\Program Files (x86)\Stardock\Fences\SdDisplay.exe</Data>
  <Data>C:\Windows\System32\KERNELBASE.dll</Data>
  <Data>c7e1c3a2-0c2e-49d4-8c83-1537f63d3297</Data>
  <Data />
  <Data />
  </EventData>
  </Event>
 
Fault bucket 2294721618642658180, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
 
Problem signature:
P1: SdDisplay.exe
P2: 1.8.0.1511
P3: 5a8c1e1f
P4: KERNELBASE.dll
P5: 10.0.18362.1139
P6: 6a8e6b97
P7: e0434352
P8: 00114662
P9: 
P10: 
 
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC3E.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC8D.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC9E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDC9C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD1A.tmp.txt
 
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_SdDisplay.exe_05cfbbc9562165563a954dd9c1ecbf22e4f2556_822d19d1_5c29e374-bc2a-4ab7-b8d4-8fa765157b6e
 
Analysis symbol: 
Rechecking for solution: 0
Report Id: d76f8d13-0361-43d3-840c-1021529588ac
Report Status: 268435456
Hashed bucket: aa7220fcbb7348d6ffd87d27799ae384
Cab Guid: 0
 
I don't know what all this means, but figured you'd know.
fences
6,763 views 6 replies
Reply #1 from WinCustomize Forums Top

Hello,

Sorry to hear you are having issues.

Fences is updated as needed to stay up to date with

Windows , so your still running older version of Windows 1909.

You should think of updating to the latest version of Windows 20H2.

 


AzDude
Stardock Community Assistant

Reply #2 from Stardock Forums Top

It's a corporate environment so 1909 would be as current as I can get for the next year. 

TouchTasks - Access tasks with ease on Windows touchscreens.
Reply #3 from Stardock Forums Top

 Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

 

AzDude
Stardock Community Assistant

Reply #4 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Please try purge and reinstall steps as mentioned here: https://forums.stardock.com/486084/fences-support-faq#reinstalling Just make sure to redownload the latest version from your account. Reboot after the purged. Reinstall, and Reboot again after the installation. Retest it. Report back here.


Basj,
Stardock Community Assistant.

Reply #5 from Stardock Forums Top

Hello,

Sorry to hear you are having trouble.

Please see this thread:

https://forums.stardock.com/502301/page/1/#3793493

Sean Drohan
Stardock Support Manager

Reply #6 from Stardock Forums Top

I am assuming you guys pushed out an update. My version of fences is now 3.0.9.11 and it seems the functionality is restored because it actually asked for my product key. Previously your installer never did, so you can mark this as fixed.