Fences 6.20 upgrade run issues

from Stardock Forums

Stardock Fences 6 upgrade installed on win 11 PC multi-monitor (3 screens)

issues after boot:

Message window : "Fences has detected that Explorer was not closed Properly. As a precaution , Fences has been temporarily disabled."

Enabled Fences 3 times over 10 minutes. on the 3rd re-enables fences started and worked as normal/properly.

one crash report submitted following re-enable Fences.

After Windows PC shutdown and reboot, the same issue occurs after Windows starts. 

Is there a fix , patch or update to fix this issue?

 

 

fences 6.20 multi-monitor win11 fences
189 views 5 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Not sure about your issue, there are similar reports on Fences 6.44 but not on 6.20 (refer to this thread). If you actually have issue with Fences 6.20, perhaps, it has something to do with installation not done properly. 

Moving forward, please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload version 6.2 from your account page. Reboot after the purge. Reinstall and reboot again after the installation. Retest and report back here.

Thank you,
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Solution

Copy the folder: %AppData%\Stardock\Fences\Backups

Copy the file: %AppData%\Stardock\Fences\fences.xml (This contains your custom rules and folder portal paths).

https://cdn.stardock.us/support/uploads/Purge_Fences.zip

Save the file to your downloads folder.

Unzip the Purge .BAT file

run as Administrator.

let it finish.

then Reboot.

Download the current download version fo Fences 6 and reinstall.

 

 

Elemental: Reforged
Reply #3 from Stardock Forums Top

Thanks Basj, I did and it worked.

Something (Fences)  seemed to crash explorer as it was loading - stopped other interface elements to load. 

Reply #4 from Stardock Forums Top

Hello,

If you refer here: https://forums.stardock.com/541311/get;3991789, reply#53, there is a newer version released which should resolved this issue. Please use the link posted in there to download the latest build and see if the issue still appear. Remember, you need to reboot right after the installation is done.

Thank you,

Basj,
Stardock Community Assistant