Skip to main content

Just updated with disastrous results!

Thread needs solution

I just updated my Acronis 2016 which worked perfectly well to Acronis 2017.

I have installed the new version but it refuses to accept the serial number which was sent to me by email.

In frustration, I uninstalled 2017 and temporarily switched off my Norton AV and then reinstalled 2017.

It still will not accept the serial number and I now have no Acronis at all because 2016 was uninstalled too!

There is some registry work around mentioned but I don't feel confident with messing with the registry.

 

I am using windows 10 Home Edition.

 

help!

0 Users found this helpful

Brian, you will need to contact Acronis Support directly for help in resolving why your serial number is not being accepted as we have no ability to resolve this type of issue here in these user forums.

Please see article: 18623: How to get Technical Support: Tips, Tricks and Useful Information

1.    Customer Service
Related to
- Administrative license/serial number issues (lost, fails to get registered, etc.)
- Web navigation
- Download
- Promotional offer issues

- free of charge 
- unlimited
- 24x7
- provided via e-mail and chat. 
Response time:  
-  3 business days via e-mail
 - immediate via chat

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Brian,

Thank you for your posting! Could you please send me your serial number in PM (the first two blocks of the key are enough) and a short description of your actions\screenshots illustarting the issue. 

Thank you in advance!

Problem sorted!

I logged into Support and had an Online Chat with a Customer Support Agent called Vicky.

She discovered that I had been using the wrong email address to login.

The problem was solved in minutes.

It would have good if the failure message that I kept receiving had detailed the fact that the email address was the problem!!!!

Brian, thanks for feeding back, glad to hear the issue is solved.