Humble Bundle Fence 3.x Licence

entering serial number not possible

from Stardock Forums

Hi!

Just bought a licence and downloaded the Fence-installer from HumbleBundle.

 

When I move the mouse, the "enter serial number now"-dialog shows - but when I click (or do anything else), this error box shows:

 

What's wrong?
How do I get Fence to work properly and how to finally register it?

 

Thanks,

Steve

 

fences
19,724 views 7 replies
Reply #2 from Stardock Forums Top

Hi AzDude,

 

thanks for your link.

 

Sadly my problem is not concering my serial number but more this error message, that shows as soon as Fences is running, and the fact that the "Stardock"-windows with the link "enter serial number" is not working.

 

Any idea how I can fix that?

 

Thanks again!

Best,
Steve

Galactic Civilizations IV
Reply #4 from Stardock Forums Top

Hello again,

 

bat-file downloaded, run - and uninstalled. Rebooted and re-installed: same problem:

 

Enter serial key: error message comes up, no possibility to enter serial. Same with 30 day trail.

Only buy key brings me to the website - without error message.

 

Any ideas how finally fix this - if not I will try to cancel my purchase, as it seems it will not work on my PC.

 

Thanks in advance.

Best,

Steve

 

 

 

 

Reply #5 from Stardock Forums Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

 

 

AzDude
Stardock Community Assistant

+1 Loading…
Reply #7 from Stardock Forums Top

Hi Basj,

Thanks for your tips and the links.

Finally, I give up. Extra account: error message. Clean boot: error message.

 

With all this testing and "cleaning" I found out that I had installed some weeks ago the 30 days trail, which got uninstalled while Win 10 Upgrade 1803 performed some further updates.

Maybe there's an easy solution if someone already hat Fences as trail installed?

 

If not, I'll give up and retry with the next Microsoft Update. I spent so much time on several possible solutions and not a single one worked - maybe the error within my OS will be "cleaned" with MS next upgrade.

I can wait! :-)

 

Best,

Steve