Fences is crashing my user and reboot profile in a loop

'Fences has detected that Explorer was not closed properly'

from Stardock Forums

Hello,

I have been using "FENCES 3" on a PC for a few years, and I am very satisfied.
For a laptop under Windows 10 64 bits last up -to -date system:

Windows 10 professional edition
Version 21h2
Build of the operating system 19044.1706
Windows Feature Experience Pack 120.2212.4170.0

At the restart following battery failure, I had the famous message:
'Fence has deteced that explore was not close to properly ...' '

At this time, the display of the message disappears on its own and the loading applications and the crash profile. And the process is constantly reproducing in a loop.


Impossible to do anything. Only CTR-alt-del allows you to close the transfer.


I created another administrator account, it starts with FENCES without problem.


I followed the uninstallation and cleaning procedures described on the forum: tools, register, scannow & co ...


The open message of the FENCES dialog has disappeared, but the crash profile always and restarts in a loop ...


Do you have a solution for me and to help out my profile without having to break it and redo entirely?


Awaiting your reply.
Cordially.
Edgar

 

fences
5,835 views 6 replies
Reply #1 from Stardock Forums Top

PS : I also tried the start -up in Windows safe mode, but the profile restart loop also persists in this mode.

Reply #2 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. You currently on Fences V3 or V4?

Thanks
Basj,
Stardock Community Assistant.

Sins of a Solar Empire II
Reply #3 from Stardock Forums Top

Hello,


Fences 4 

and I also tried with a reinstall of Fences 3.

what is weird is that even without having Fences (after uninstallation) the profile continues to crash

Reply #4 from Stardock Forums Top

Please try purge and reinstall steps as mention here : [Link]. Just make sure to redownload the latest version 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.