I am currently using Symantec System Recovery 2013 R2 with my Windows 8.1 based desktop PC. I am planning on upgrading to Windows 10 on July 29, 2015 when Windows 10 is released. I've been relying on Norton Ghost and SSR 2013 to do full system images for years.
Is Symantec currently working on software for Symantec System Recovery 2013 so that it will be compatible with Windows 10?
Will Symantec be offering a FREE update patch to Symantec System Recovery 2013 that will make it compatible with Windows 10? Will it be called Symantec System Recovery 2013 R3 or something else like Symantec System Recovery 2015?
I would like to see SSR 2013 tested and certified as compatible with Windows 10 as soon as possible. I would prefer not to have switch to another vendor's system image backup software like Acronis. Their website is saying that you can get a free software update for Windows 10 compatibility for Acronis True Image 2015.
I am going to try again tonight since it seems it worked fine for lots of people. Mine just kept saying it couldn't install license that symantec had sent me.
Maybe will try uninstalling program and then clean registry and re-install it. Then go through steps according to cjm. If it worked for all of you there isn't a reason it shouldn't work for me - hopefully lol
@Doug3909 -- Using this work around I can still see the C: drive available when I use the "define new backup" wizard. It looks like it might be a little bit confused by drives > 2TB though. On the one I tested I have a 500 MB drive backing up to a 4TB array and it works, but it does not show the information about this destination correctly.
Now that it is licensed at least, hopefully support can help you with the issue you are seeing now.
With the new upgrade to windows 10 the license code SSR2013 is not accepted by the program. I read that more people are expiring the samen problems. I called Symanted and they told me to place an message on this post, service will than contact me.
I see that you are out at the moment---honestly, it seems unbelievable that so many have this problem and I can't upgrade to Win10.
BUT, after reading through this thread, I'm not sure what the answers are here to these questions.
If I upgrade to 2013 R. 2 (I'm now using 184.108.40.206XXX), is that a free upgrade? Will my current license WORK with that when Win 10 support is available?
---I ran LiveUpdate on my current software and it told me I was up to date. I'm not sure what the difference is here between what I'm running and what you're pointing to if the program itself says "up to date."
===I see someone posted an interesting workaround, but I'm curious for you and others---will that workaround actually maintain the integrity of the system? It makes me a bit nervous to run an image backup of a Win 10 system using software that doesn't seem compatible with Win10.
THis is cool, many thanks, but have you actually done a full restore?
That is, it makes me a bit queasy in the stomach to rely on an image backup of a Win10 system using software that doesn't entirely seem compatible with Win10--even if by some trickery I can make it think I'm on Win10. So, if I have a total meltdown and have to do a complete restore, what happens? Will it also restore Win10, even though it doesn't think that OS exists?
I have been using Ghost for many years but since upgrading to Windows 10 Ghost is not compatible and does nor work so I was advised to download and install the trial version of SSR 2013 R2 which I have. I have installed it and all appeared OK however when I try and opem the SSR 2013 R" the opening banner flashes in the centre of the screen nothing else happens. I have tried the fix suggested by cjm and this has not resolved the issue.
Any other suggestions would be much appreciated
I fully agree and thanks a lot for the workaround. On a 3 year old desktop with two samsung ssd's it worked fine, including restoration of system drives. Backup was created on a live system. Although no 100% guarantee for every situaion I feel comfortable enough to continue with it for myself.
I skipped step 3 because in my opninion it is only necessary to stop the service temporarily to change the compatibility mode.
This is absolutely no recommendation for Symantec, They should come soon with acceptable solution, otherwise I wasted my investment done 8 months ago to move from Norton Ghost 15 to SSR 2013 R2.
And again thanks for your clear stated step-by-step plan.
I was talking few days ago to symantec support. They told me the following:
We got confirmation that SSR 2013 R2 Desktop is not compatible with new Windows 10 until the next maintenance release. Unfortunately, we do not have any dates yet as to when the new patch will become available. Our technicians recommend to use previous windows version until new patch will be available.
As a result, keys are invalid due to compatibility issue.
After changing the compatibility mode to windows 8 and a successful completed backup I did restore both system drives successfully, meaning my desktop is still functioning well. I am fully aware of the fact this is no 100% guarantee at all but for the time being I can live with it.
It is up to Symantec to take responsibility now and do their job to service their customers as quick as they can.
Congrats to cjm - couldn't get his directions to work at first so I uninstalled and reinstalled SSR and tried his suggestion again and it worked. Can see my back up drive and also all my backups before and after win10 upgrade. Making boot disc as I type.
All I can say to that is, seriously Symantec?
As someone else remarked in this thread, my Win10 upgrade (from a recent 8.1 machine, an easy upgrade admittedly) was flawless. EVERYTHING worked. Everything was put back from wallpaper to icons. No driver was broken.
The only problem: here.
I'm certainly no expert in SSR, but if I correctly understand this neat activation workaround for getting SSR to work (sort of) with Win 10, then I believe you would not want to reinstall nor run LiveUpdate. My rationale is that the LiveUpdate function may very well disrupt/impact the temporary working solution you have accomplished for SSR.
If it were me, I would continue to use the workaround SSR solution, not run LiveUpdate, and wait for Symantec to issue a full and proper solution to this absurd mess.