Fences 3 & 4 doesn't work after update

Till a few weeks ago I was using Fences 3 in a Windows 11 pc, and it worked fine.

I was away for a while and when I returned, Windows automatically get two updates KB5019351 and KB5018418.

After restarting, Fences stopped working. I couldn't create a fence, I couldn't customize, nothing. Tried uninstalling, tried purging and reinstalling, nothing.

So i decided to purchase Fences 4 hoping to fix the issue. Again, exactly the same problem. Then I decided to update my Windows to 2022H2 (22621.674) and still nothing. Tried purging again, nothing.

I install the app, but the only thing I can do is use the default fence. I can't create new ones, there is no "Customize Fences" option when I right click, nothing.

Please help!

17,055 views 17 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Please check if you have not locked Fences. If it is lock please unlock it and try again.

Thanks
Basj,
Stardock Community Assistant.

Reply #2 Top

Just as there is no "Customize Fences" option, no "Lock Fences" either.

Reply #3 Top

Click the "Show more options"

Thank you,

Basj,
Stardock Community Assistant

Reply #5 Top

Please check your Taskbar Manager (right click on taskbar->Task manager-> Startup apps tab) and check if both Fences.exe status are enabled to start on Startup. If not please enable it and restart.

Thank you,

Basj,
Stardock Community Assistant

Reply #6 Top

There is only one Fences.exe and it was in fact disabled. Enabled it, restarted but no change.

Reply #7 Top

It need to be enable twice for Fences to work properly. Please try purge and reinstall steps as mention here : [Link]. Just make sure to re-download 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.

Reply #8 Top

Nothing seems to work, but if it matters, something doesn't seem to go right in purging.

Here is what I get:

 

SUCCESS: The process "explorer.exe" with PID 7524 has been terminated.

 

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

    Fences    REG_SZ    "c:\program files (x86)\stardock\fences\Fences.exe" /startup

 

The operation completed successfully.

 

HKEY_CURRENT_USER\Software\Stardock\Fences

    LastConfigSyncAttempt    REG_SZ    15/10/2022 1:02:02 pm

    DateInstalled    REG_SZ    15/10/2022 4:01:58 pm

    LastLangID    REG_SZ    en-US

    ProVersionEverInstalled    REG_DWORD    0x1

    LastConfigDate    REG_SZ    15/10/2022 1:02:04 pm

    LastConfig    REG_SZ    <Configuration>

 

<BugSplat>

CrashReporting-BuildEnabled-3.0.5

CrashReporting-BuildEnabled-3.0.6

CrashReporting-BuildEnabled-3.0.7

CrashReporting-BuildEnabled-3.0.8

CrashReporting-BuildEnabled-3.0.9

CrashReporting-BuildEnabled-3.0.10

CrashReporting-BuildEnabled-3.0.11

CrashReporting-BuildEnabled-3.1.0

CrashReporting-BuildEnabled-3.1.1

CrashReporting-BuildEnabled-3.1.2

CrashReporting-BuildEnabled-3.1.3

CrashReporting-BuildEnabled-3.1.4

CrashReporting-BuildEnabled-3.1.5

CrashReporting-BuildEnabled-3.1.6

CrashReporting-BuildEnabled-3.1.7

CrashReporting-BuildEnabled-3.1.8

CrashReporting-BuildEnabled-3.1.9

CrashReporting-BuildEnabled-3.1.10

CrashReporting-BuildEnabled-3.1.*

CrashReporting-BuildDisabled-3.0.*

</BugSplat>

 

<Telemetry>

TrialTelemetry-BuildEnabled-3.0.5

TrialTelemetry-BuildEnabled-3.0.6

TrialTelemetry-BuildEnabled-3.0.7

TrialTelemetry-BuildEnabled-3.0.8

TrialTelemetry-BuildEnabled-3.0.9

TrialTelemetry-BuildEnabled-3.0.10

TrialTelemetry-BuildEnabled-3.0.11

TrialTelemetry-BuildEnabled-3.0.*

TrialTelemetry-BuildEnabled-3.1.0

TrialTelemetry-BuildEnabled-3.1.1

TrialTelemetry-BuildEnabled-3.1.2

TrialTelemetry-BuildEnabled-3.1.3

TrialTelemetry-BuildEnabled-3.1.4

TrialTelemetry-BuildEnabled-3.1.5

TrialTelemetry-BuildEnabled-3.1.6

TrialTelemetry-BuildEnabled-3.1.7

TrialTelemetry-BuildEnabled-3.1.8

TrialTelemetry-BuildEnabled-3.1.9

TrialTelemetry-BuildEnabled-3.1.10

TrialTelemetry-BuildEnabled-3.1.*

</Telemetry>

 

 

<Pulse>

Pulse-BuildEnabled-3.0.5

Pulse-BuildEnabled-3.0.6

Pulse-BuildEnabled-3.0.7

Pulse-BuildEnabled-3.0.8

Pulse-BuildEnabled-3.0.9

Pulse-BuildEnabled-3.0.10

Pulse-BuildEnabled-3.0.11

Pulse-BuildEnabled-3.0.*

Pulse-BuildEnabled-3.1.0

Pulse-BuildEnabled-3.1.1

Pulse-BuildEnabled-3.1.2

Pulse-BuildEnabled-3.1.3

Pulse-BuildEnabled-3.1.4

Pulse-BuildEnabled-3.1.5

Pulse-BuildEnabled-3.1.6

Pulse-BuildEnabled-3.1.7

Pulse-BuildEnabled-3.1.8

Pulse-BuildEnabled-3.1.9

Pulse-BuildEnabled-3.1.10

Pulse-BuildEnabled-3.1.*

</Pulse>

 

 

</Configuration>

    CrashReportingEnabled    REG_DWORD    0x1

    UserLang    REG_SZ

    LastDebugHeader    REG_SZ    4.0.7.2 5400344 - 17/08/2022 8:34:53 pm 3190552 - 17/08/2022 8:34:53 pm 3584792 - 17/08/2022 8:34:53 pm 3671832 - 17/08/2022 8:34:53 pmNone

 

HKEY_CURRENT_USER\Software\Stardock\Fences\Groups

HKEY_CURRENT_USER\Software\Stardock\Fences\Icons

HKEY_CURRENT_USER\Software\Stardock\Fences\InitialSnapshot

HKEY_CURRENT_USER\Software\Stardock\Fences\Rules

HKEY_CURRENT_USER\Software\Stardock\Fences\Settings

HKEY_CURRENT_USER\Software\Stardock\Fences\Stats

HKEY_CURRENT_USER\Software\Stardock\Fences\Tips

The operation completed successfully.

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

ERROR: The system was unable to find the specified registry key or value.

 

SUCCESS: Sent termination signal to the process "Fences.exe" with PID 17436.

SUCCESS: Sent termination signal to the process "rundll32.exe" with PID 13324.

SUCCESS: Sent termination signal to the process "rundll32.exe" with PID 13232.

C:\Program Files (x86)\Stardock\Fences\FencesMenu64.dll

Access is denied.

C:\Program Files (x86)\Stardock\Fences\SdAppServices.dll

Access is denied.

C:\Program Files (x86)\Stardock\Fences\SdDisplay.exe

Access is denied.

C:\Program Files (x86)\Stardock\Fences\Stardock.ApplicationServices.dll

Access is denied.

C:\Program Files (x86)\Stardock\Fences\FencesMenu64.dll - Access is denied.

C:\Program Files (x86)\Stardock\Fences\SdAppServices.dll - Access is denied.

C:\Program Files (x86)\Stardock\Fences\SdDisplay.exe - Access is denied.

C:\Program Files (x86)\Stardock\Fences\Stardock.ApplicationServices.dll - Access is denied.

Access is denied.

The directory is not empty.

 

Reply #9 Top

After the purge is done, with error and all, if you restart your system. Does Fences still appear in your task manager start up tab? If not, please install Fences 4. reboot and retest.

Thank you,

Basj,
Stardock Community Assistant

Reply #10 Top

No, after purge, it doesn't appear. Reinstalled, rebooted and still the same.

This time, the Configure Fences option does appear when i right-click, but still it does nothing. An the "Lock Fences" option is unticked.

I also have two Fences in my startup apps and they are both enabled. No change.

Reply #11 Top

Okay, do you have "360 total Security" or something similar, which installed its own desktop organizer utility which is conflicting with Fences. If so you will need to disable that desktop organizer. Check it and report back.

For reference: https://forums.stardock.com/494957

Thank you,

Basj,
Stardock Community Assistant

Reply #12 Top

No, I have no such utility. Just Windows defender.

Should I try uninstalling any of those two windows updates (KB5018418 & KB5019351) that started this mess?

Reply #14 Top

Home edition, so no sandbox unfortunately

Reply #16 Top

Finally it works!

I tried the cleanboot solution, created a new account, installed Fences 4 and the activation window suddenly appears! It NEVER appeared in my main account, no matter how many time i installed it, uninstalled it, purged it, and I did all these things many, many MANY times these last few days. I enter my license key and it works just fine!

I immediately uninstall it, didn't even have to purge, I go back to my main account, install it and there is the  damn activation window!! I enter the key and finally I have Fences again!

Something was seriously stuck with that activation window, but thankfully we 're ok now.

Thank you for all the help.

Reply #17 Top

Great, glad it get resolved.

Thank you,

Basj,
Stardock Community Assistant