Fences 6 212 Error Activation Issues.

***Reserved***

We suspect there might be an issue preventing Fences from writing to a specific folder. This could be due to permission restrictions or interference from antivirus or security software.

Please follow these steps to help us diagnose the issue:

1. Press the Windows key and "R" simultaneously to open the "Run" dialog box.
2. Copy and paste the following path into the "Open" field: %ProgramData%\Stardock\, and then click OK.

This action will navigate to the directory: C:\ProgramData\Stardock.

We need to verify a few things:

• Confirm if the directories C:\ProgramData\Stardock and C:\ProgramData\Stardock\Fences6 exist.
• Check if you have write permissions to these folders.
• Identify if any antivirus or security software might be blocking Fences from accessing these folders.

Additionally, if you are familiar with the Event Viewer:

• Please examine the Windows "Application" log for any errors related to writing to these folders or issues with Fences activation.

Furthermore, please check the SasLog.txt log file located at %localappdata%\stardock\Fences6\. Let us know if there are any errors related to writing or setting permissions for these folders.

Should you encounter any permission-related issues, you might need to adjust the write permissions for these folders or seek assistance from your IT department.

In addition to what T-Man said, please ensure that 'Windows Controlled Folder Access' is not enabled (as a test).

Sean Drohan
Stardock Product Lifecycle Manager

Hello

I have this error.
OS: Windows 11
Path: C:\ProgramData\Stardock
Directorys: Fences4, Fences5
Rights: DI
Owner: *currently logged on user

I had the same issue on Windows 10. To fix it, I manually created a Fences6 folder in ProgramData > Stardock. Then, I right-clicked that, went to the Security tab, clicked on Users (System and Administrators were also listed), clicked Edit to change permissions, turned on (checked) Full control, Modify, and Write, and saved. Then, I was able to activate.

*** Carry over from https://forums.stardock.com/535188/page/1/#3964209 ***

Answers

Directory: C:\ProgramData\Stardock.

Confirm directories exist:

1.       C:\ProgramData\Stardock CONFIRMED PRESENT [Set at Read Only]

2.       C:\ProgramData\Stardock\Fences6 NOT PRESENT

Antivirus exempts Fences

Firewall exempts Fences

Application Log: Not sure how to filter this to find if there are log errors

SasLog.txt =
\WINDOWS\Explorer.EXE'.

[2025-03-12T17:43:11] Error   : SetFilePermissions: Unable to get security info for C:\ProgramData\Stardock\Fences6

[2025-03-12T17:43:11] Info    : Loaded package file 'c:\program files (x86)\stardock\fences\Default.spak', Version '6'.

[2025-03-12T17:43:12] Info    : Initialize: Product ID '2688', Product Name 'Fences6', Version '5.9.8.9', Company Name 'Stardock', Process Name 'C:\program files (x86)\stardock\fences\Fences.exe'.

My actions:
1. Will uninstall Fences 6
2. Reinstall and run as administrator
3. will validate

Confirm directories exist and write access 

1.       C:\ProgramData\Stardoc

2.       C:\ProgramData\Stardock\Fences6 

I will repost results

FIXED

I uninstalled
I deleted both of these files manually

C:\Program Files (x86)\Stardock

C:\ProgramData\Stardock

I ran the installation as Administrator
I was able to register the product successfully.

ISSUE RESOLVED!
Thank you Team

Very pleased to read that you were able to resolve it.

That could only mean that it was not asking you for Admin when installing normally?  I cant think of anything (other than something someone manually changed) that would prevent that from happening.  Do you know of any such changes you made?

Sean Drohan
Stardock Product Lifecycle Manager

I am having this error 212 as well. I had my v5 set to auto take a daily rollback picture. If I uninstall beta 6, and reinstall v5 will I have access to these snapshots? See: How to go back to Fences 5 from Fences 6

Reply #2 was the key - something was preventing the installer from writing to the folder to create the "Fences6" folder - saslog.txt was the key in confirming that. I did what was suggested in Reply #5 above (manually creating "Fences6" and setting the permissions) and that worked.  I actually tried that before, but didn't set "Users" permission to "Full".

Issue resolved (at least for me!)

Yes, I tried that. Thanks. Did not work. I just did it again and opened the Fences folder and it was empty. I found it here [along with all of my Stardock installations]: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Stardock - this is just where Stardock installed all my software by default. In any case, Fences 5 now works [version 5.88]. However, OD keeps wanting to update it. Can't find any setting to turn off downloading betas. I know it used to be there, but at the moment I can't seem to find it. I do not want to go through this again.

For turning off Betas, please turn off this setting in OD.

Thank you,

Basj,
Stardock Community Assistant

Thanks. I guess that has changed. Appreciated.

Edit: Actually, I already have that option UNchecked, yet OD wants to download version 6 again. There used to be a setting that specifically said "Betas." If it's still there, I can't find it.

Actually, If I remember correctly, It was Betas before now it call "Insider Builds"

BTW, do you still have issue running Fences 6?

Thank you,

Basj,
Stardock Community Assistant

I actually haven't tried, but OD sure wants me to. In the screenshot you can see that I have "two" Fences ready to install. This is with the Insider Builds option unchecked. That's how I inadvertently installed it in the first place. I just thought it [the first option] was a regular update. It wasn't. I don't know if I am a lone wolf, but I think it might be a good idea to have a look-see. 

After the Stardock site came back up, I began having issues again with activation of Fences [all other Stardock software are fine]. On a whim, I uninstalled v/5, rebooted, installed v/6, then followed Post #5 above. Bingo! Thanks.

That's wonderful to hear!

Thank you,

Basj,
Stardock Community Assistant

I ended up modifying the security settings for my windows account and set it to full control before i was able to activate Fences 6.

Hello everyone...
If anyone has this stupid -212 error and support can't figure it out...
I finally managed to solve it...
It's so stupid it's ridiculous...

The problem occurs if you have Windows 11—there, the path “C:\ProgramData” has system rights. In plain language, this means that NO tool is allowed to write to it. Unfortunately, the activation does not display any message.
You must manually create the “Fences6” folder and give the ‘Users’ group “full access” to this folder. After that, registration is possible without any problems and the tool works completely normally.
This is a bug within the software. The developers should really fix this, but unfortunately they don't.
Unfortunately, support doesn't “understand” it either....

Dear Support...

Instead of annoying users with weird stuff, fix your software and build in sensible error messages. What you're delivering is absolute junk!
PS: Yes, I'm a developer myself—that's the only reason I was able to solve it so quickly!

Hello,
I have forwarded your observation/suggestion to Stardock Support Team for their review. We appreciate your input. Thank you.

Basj,
Stardock Community Assistant

Thank you. That fixed my issue. I agree. Development should fix this. 

If we knew what was causing the 0.0001% of people to see this, we most certainly would - if it's even something we can address.  This reads like an over-active AV or Malware product, or at the very least, an example of someone who has tinkered with permissions - what can write to where.

Sean Drohan
Stardock Product Lifecycle Manager

I have used endless hours to try to solve this exact problem. Thanks sdRohan!

You are most welcome.

Sean Drohan
Product Lifecycle Manager

I am experiencing the -212 error code. I have created the folder in Program Data and given the Users group Full Control (which is weird, I have other apps create folders in Program Data folder). I still receive the -212 error. I am upgrading from Fences 3.

Nevermind. I found my error.