Fence 3 & 4

windows 11

I have problems with fence 3 on different computers in Windows 10 & 11.

2 windows 11 and 4 windows 10.

Problem: I lost all my keys and fence became a "30 days free test product".

I mailed to support (which one?) but they didn't understand the issues.

By moving from Windows 10 to Windows 11 thru media2tool I was able to create a stable environment with the exception of products such as Fence and Winzip Disk Suite. Same issue ==>all keys lost to 30 days free testing.

Going back to Windows 10 I could pick up the keys of Window10 fence 3.4. A stable fence. Back to Windows 11 all keys are gone and I got a 30 days free testing environment.

I uninstalled Object desktop with Fence 4 in it. Windows 11 and Fence 4 was stable. 

Cost was USD 54,00 vs €10,00 Fence 3 only.

After a while and probably going thru a UEFI boot sequence I lost my Object desktop keys again.

I asked to reimbuse Object desktop. As soon as the product is gone I unstalled either Fence 4 or Object desktop again. Hopefully Fence 4 is now stable and key is not a "30 days free".

There is something wrong with key management of Stardock products in Windows 11.

The best is to remove Fence X in Windows 10, convert it with mediatool to Windows 11 and reinstall Fence 4 in Windows 11.

Stardock support didn't answered correctly. I got the wrong support department or the wrong error chapter. A pity, cause I could use some help here.

Anybody else with similar issues?  

Kind Regards

Marc.

I worked for years with several products from Stardock. I even have a Fence 2 working well.

 

 

1,864 views 1 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. But, not really sure I am clear on your issue. If you have issue on activation. It might be because you need to deactivate old activation. You can use this guide to deactivate old activation and reactivate it again later. https://forums.stardock.com/486311/accounts-and-activation-support-faq#deactivateproduct.

Try that and let us know if you still need our assistance.

Thanks
Basj,
Stardock Community Assistant.