I followed the instructions posted at https://support.symantec.com/en_US/article.TECH231698.html. I have successfully upgraded to SP3. However when I try to follow the instructions to apply the license fix, the 64-bit attachment is immediately deleted by Norton Antivirus File Insight with no way I can see to restore (this may explain why an earlier post said the 64-bit version was missing). Its also a little confusing as to whether if the license is accepted that the software will now function correctly under windows 10.
Threat name: WS.Reputation.1Full Path: e:\data files\downloads\symantec system recovery\ssr2013r2_win10\ssr2013r2orphan87\64-bit\vprosvc.exe
On computers as of
24/08/2015 at 12:14:10
24/08/2015 at 12:16:10
Threat type: Insight Network Threat. There are many indications that this file is untrustworthy and therefore not safe
vprosvc.exe Threat name: WS.Reputation.1
Very Few Users
Fewer than 5 users in the Norton Community have used this file.
This file was released less than 1 week ago.
This file risk is medium.
Source: External Media
File: e:\data files\downloads\symantec system recovery\ssr2013r2_win10\ssr2013r2orphan87\64-bit\ vprosvc.exe Removed
File Thumbprint - SHA:
File Thumbprint - MD5:
You will need to go into the Antivirus Quarantine area and restore this file which will also mark the checkbox to exclude this file from future scans.
If you can manage to click on the failed report i thinkthere is also an option to trust the file - but after the event the file should still be in quarantine so restore is still an option
Restored from quarantine and marked to ignore from future scans. Did not need to stop service as it was already stopped. Replaced file and re-launched SSR. Did not need to verify license details. The trial message is no longer displayed and I have successfully run all of my backups. This was my only significant issue upgrading to Windows 10 so nice to get it resolved.
Just for completeness I did have to input my license details and I used the ones I received when I upgraded to R2 - I was expecting to have to input before I made my backups but I was prompted afterwards.
Booted from SRD and got into recovery environment - restored a file from one of my complete disk backups. Saw all my possible restore points and browsed the backups. I do not have an environment to try a full restore but otherwise everything looks okay.
I successfully created boot disks (CD) with SSR 2013 R2 22.214.171.124088 in Windows 8.1 and in windows 10 and was able to boot from both cd’s in Windows 10.
But USB Recovery Disks don’t work.
I booted into the recovery environment and restored a Windows 10 image to its original location and onto a new HD. No problems: for me it works.
I have managed to create a backup disk using the SRD Creator disk in Windows 10 as well as restore a full backup of my system C:\ drive - without any issues apart from having to manually fix the created SRD disk.
There is an issue with the SRD disk for some PC's for the SRD disk iso that is created as it is missing a copy of oledlg.dll without which the SRD disk won't proceed passed SrdEULA.EXE being accepted as it boots. This only happens when you are required to use Advanced mode SRD creation due to Typical mode SRD creation failing with ECA3232B and ECA3232C errors.
However, it is possible, as I have done and proved, to add the missing oledlg.dll back onto the boot disk using a manual process within 10 minutes and I do not understand yet why it isn't added as per normal like in Typical mode creation whereas in Advanced Mode SRD creation the file is omitted. My main desktop had this issue whereas my laptop was able to create the SRD disk with the oledlg,dll automatically in Typical Mode.
Other users are having the same issue in Windows 8.1 with SSR 2013 R2.2 and, by disabling their Anti-Virus during SRD Advanced Creation mode found that the oledlg.dll file was added properly. This workaround does not work in Windows 10 for me and does only in SRD Creation using the System Recovery Managament Console mode of SRD creation using a separate Management Console to create the disk.
There is also at present a user with SSR 2013 R2.2 that reported this problem to Symantec in April this year and unfortunately Symantec still doesn't have a fix for SSR to add the file without the manual extract, addition and re-creation process I used to manually path the iso file with the missing dll. This issue is currently one of the top threads in this forum.
There is also a problem with encrypted files as from what is reported they won't restore - but as I do't have any that I am aware of, this hasn't been an issue for me as yet.
So for some users SSR 2013 R2.3 is working ok under Windows 10.
With my laptop only needed fix for license and easier fix for SRD Creation permissions. have performed full laptop C: drive backup without any issues under Windows 10.
With my desktop needed the license fix as well as SRD Creation fix and the mod to the SRD disk created in Advanced mode. I have performed a full windows disk backup and restore under Windows 10 without any issues.
Has the fix for SSR 2013 RS and Windows 10 been released yet? I have many customers waiting to upgrade to Windows 10 and will not proceed until this issue is resolved. They have been trained in Ghost and Back-Up Recovery and do not want to go with a different vendor.
To answer your question a quotation from the email from Symantec Support I received today:
"Recently the new version of the Microsoft OS, Microsoft Windows 10 has been released.
At this point in time this OS version is not supported by the Symantec System Recovery 2013 R2 or prior versions.
This situation will be addressed in future releases of the software, but for now we are not in the situation to provide any specific dates of when the compatibility with the latest Microsoft OS will be added."
I have an open case number with Symantec for about one week now. I have yet to receive the promised telephone support call or even as much as a follow up email. This total lack of support is unacceptable especially when I have paid for it as a part of the cost of the software. I am now exploring other software options, several of which are far less exspensive than SSR. I've had and used Symantec products going back to the Peter Norton days and it is clear they have lost focus. Time to move on.
Case # 09320798
Like many of you here, I and my employer are long time users of SSR. The response Harry350 received from Symantec Support is both sad and frustrating. The development team was late for Windows 8, Windows 8.1, and now Windows 10. I participated in some of the BETAS. Long term, I see nothing but future problems and delays as as Windows 10 will be constantly improving and changing with the new Microsoft philosophy of Windows as a service. My biggest concern is SSR will be working fine today but the next Microsoft Update causes the software to fail. Will we have to wait months for a fix?
1. Is the SSR team understaffed? Why were they not ready for Windows 10 particularly with home users now in the mix?
2. Is the consistent pattern of being late a sign this product is ultimately heading for discontinuance?
3. With the pending sale of Vertitas (which includes SSR I believe), what will the new ownership's philosophy be toward SSR?
4 Does the devlopment team need new management?
On a positive note, thank you Chris Riley for all you do. It is tough being the man in the middle.
Yes, Chris has been as helpful possible. Comments should not be taken as an attack on him personally.
In regard to the substance of your comments, I have regretfully drawn the same conclusion.
I 100% agree. All points are very much correct. I feel I will be moving to another provider. Looks like Symantic has been invaded by Obama Care.
Chris has been helpful and I am sure he wishes he could have done more. I have supported Norton/Symantec for years but my faith in them has sunk to a new low.
@CQ: Thanks for your contribution and professional attitude.
@Symantec staff: Each concern expressed by QC ends up with a questionmark. A constructive response to all five concerns about current and future policy towards SSR is required now to restore (some of) the confidence in Symantec/Veritas support.
@Chris, since you are in the middle can/will you pass through CQ's concerns to your staff (and above)? Many of us here, especially including me, apparently appreciate your contributions.
Thanks in advance,
@CQ: I Totaly agree with you!!
I upgraded from Ghost 15 to SSR 2013 when I had problems with Windows 7 and Disk that were to large for Ghost.
Since being repairing and programing computer since before DOS 1. I know what happens when you loose a hard drive, realise you need file(s) that was deleted months ago. My home backups are saved on 2 different hard drives and copied onto 25GB BD-R disk for longer term recovery.
If Symantec or whoever now is getting Vertitas wants to be the insustry leader in System Recovery they must be on the cutting edge. Since I only use the Desktop Edition at home I want software that keeps up with the release of Windows upgrades, or make software that is not limited to only run on OLD operatiting systems.
I have found 2 other companys (and am still looking) that make backup solutions (and I'm not looking at the FREE ones) that run on Windows 10.
Since I will NOT upgrade my primary bootable partition to Windows 10 until I find an exceptiable backup application, I'm loosing my interest in Symantec. If I don't like SSR I will not recomend it to my supervisor for company purchase.