cancel
Showing results for 
Search instead for 
Did you mean: 

Error EC8F1C25: Your trial version of Symantec System Recovery 2013 R2 has expired

unimatter
Level 3

I upgraded from 2013 (activated) to 2013R2, and now SSR fails to run.  Upon bootup, the splash screen flashes briefly, and nothing happens.  Same thing if I run it from the shortcut.  The event viewer has an error:

Error EC8F1C25: Your trial version of Symantec System Recovery 2013 R2 has expired.
To continue system protection please visit our web site.
Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'Operation aborted.' (UMI:V-281-3215-7205)

I know that R2 has a separate activation key, but it never asked me during setup for a new key.  Now I can't even get into the software to enter a key.  My system is now unprotected, please help!

Windows 7 Pro x64.

 

1 ACCEPTED SOLUTION

Accepted Solutions

unimatter
Level 3

I filed a support ticket and the tech resolved the issue by simply changing ShowWelcome=1 to ShowWelcome=0 in  C:\ProgramData\Symantec\Symantec System Recovery\Settings.ini

Seems to be a known issue with the upgrade.  I had the same issue a year ago when I upgraded to R2, had to downgrade, and was hoping upgrade issue was fixed in latest R2 version so I tried again.

In any case, hope the fix above helps someone else.

View solution in original post

4 REPLIES 4

Markus_Koestler
Moderator
Moderator
   VIP   

unimatter
Level 3

The license seems to have installed, I no longer get those event viewer errors...but still same behavior (rebooted just in case).  Nothing in event viewer now.  Very frustrating.

Markus_Koestler
Moderator
Moderator
   VIP   

Are you runnig SP4?

unimatter
Level 3

I filed a support ticket and the tech resolved the issue by simply changing ShowWelcome=1 to ShowWelcome=0 in  C:\ProgramData\Symantec\Symantec System Recovery\Settings.ini

Seems to be a known issue with the upgrade.  I had the same issue a year ago when I upgraded to R2, had to downgrade, and was hoping upgrade issue was fixed in latest R2 version so I tried again.

In any case, hope the fix above helps someone else.