update failing

Any idea how to clear this pothole in the road whilst (serially) attempting to install Fences update please?

5,215 views 7 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Please try purge and reinstall steps as mentioned here: [Link] Just make sure to re-download the latest version from your account [Link] . Reboot after the purged. Reinstall, and Reboot immediately after the installation. Retest it. Report back here.

Thank you,

Basj,
Stardock Community Assistant

Reply #2 Top

No change other than the existing fences seem to have now disappeared.  Oh and a new error message:-

Reply #3 Top

Now it having partially uninstalled (half the screen has now gone) - the site is now telling me to buy the software again.  No reinstall option - just pay up or go away.  Mmm

Reply #4 Top

Please try cleanboot [Link]. And report back here.

Thank you,

Basj,
Stardock Community Assistant

Reply #5 Top

this operation has been cancelled due to restrictions in effect on this computer. Please contact your administrator.

I am the administrator,  and I have searched the internet for a way to resolve this. I have tried the regedit htmlfile route, also the group route, unfortunately, none of them worked. I was wondering if it could have anything to do with me installing it on a new computer, I was having a lot of problems with my laptop so I purchased a new desktop and installed the program on that, would that cause the problem?

Regards, Billy

Reply #6 Top

hi bas, I did as you suggested & created a new Administrator account signed in to that and fences loaded without a problem so did object dock although I did not put in the key etc for that, it did load no problem. However, when I switched back to my account and tried to update fences I got the same problem.

This operation has been cancelled due to restrictions in effect on this computer. Please see administrator

 

Reply #7 Top

Hello,

This thread and steps offered in there might able to help you : https://forums.stardock.com/502301 The solution came around reply#15-16.

Thank you,

Basj,
Stardock Community Assistant