Shadowprotect 4.2.7 Keygen

12/4/2017by
Shadowprotect 4.2.7 Keygen

Problems are reported with this version, especially when restoring from RE. This is reported in the (new) Storage Craft Support Center!

I made a backup with 4.2.7 and restored the boot partition (C:) with 4.2.7 RE. The result was disastrous! All of a sudden Windows update and MSE did not work anymore: lt said latest Windows and MSE backup was 3-11-2012 (3 March 2012) Impossible. Even with an earlier 4.2.7 backup I had the same problem. I am now reverting to 4.1.5 and hope sincerely it can restore a 4.2.7 backup.

Regards, Teunis Post=82149 3StarLounger Posts: 214 Joined: 02 Feb 2010, 23:10. Cpm-100 Windows 7 Driver on this page. Teunis wrote. So it seems that 4.2.7.

Is OK for Backup but not for restoring, certainly not in RE (at least for the time being). I have a question that was prompted by reading a thread at their support forum. Did you make the backup using the RE CD or did you do it from within Windows 7? I never run images from the CD. I always do it from within windows, using the RE CD only when a restore is necessary. I'll be watching StorageCraft's forum but I see there that they haven't been able to replicate the problem that folks like you are having. I'm very nervous about this and trying to decide if I too need to go back to an earlier version.

Cannot deactivate serial number from an unbootable hard drive, 2, 4 years 37 weeks ago. Where to get correct VirtualBox version for ShadowProtect Desktop 4.2.7, 8, 4 years 35 weeks ago. ShadowProtect Desktop v4.2.7.19756 - Cannot access VDIFF tracking state / Cannot enable VDIFF, 5, 4 years 33 weeks ago.

Post=82179 PlatinumLounger Posts: 3757 Joined: 24 Jan 2010, 11:00 Location: Lexington, KY, USA. Big Al, Since I restored the bootable partition (C:) I had to use the RE CD (I use Win7 64 HP SP1). I have done this in de past many times and it always worked flawlessly. It was therefore a nasty surprise that 4.2.7 RE did not work, it hanged the first time at 69%, continued a second time.

However, t then turned out that although all programs ran ok, Windows (and MSE) update lists gave 3 March 2012 as latest update date, old entries did appear in the programs and features list that had long before removed (how did RE find the traces anyway?? The old MS install cleanup tool found them also, but I did not pay too much attention since we are not supposed to use it anymore!), it was impossible to update Windows and MSE. I then went to an earlier backup image: same problems. I spent a lot of time to try to repair this before I checked the forum and found out that others were having problems too with the 4.2.7 RE.

I then decided to try the 4.2.5 RE CD, which, after a hickup, worked with the latest backup made with 4.2.7. No more old entries in Programs and Features list and the MS Install Cleanup Tool. If I had known before, I would have just restored the individual virtual OS vcm file which was causing problems in the first place. But since my positive experience with RE in the past I decided to use that way.

At least now we know there is a problem with the 4.2.7 RE. Regards, Teunis Post=82182 3StarLounger Posts: 214 Joined: 02 Feb 2010, 23:10. I have now opened a ticket with them, but not received an answer relating to my specific findings: Quote ShadowProtect will do a 1:1 copy of the original system. The errors you mentioned should not occur. In most cases these errors occur if: 1. You have more than one partition restored and the drive letters are not the same as there were before 2. You choosed an older point-of-time to restore (If you have a backup set with incrementals It has nothing to do with the RE version 4.2.5 and 4.2.7 Unquote @1 I did not change the drive letters @2 I did not use a backup set with incremental It obviously - in my case - has to do with RE 4.2.7 since RE 4.2.5 worked all right.

I'll keep you informed, Regards, Teunis Post=82578 3StarLounger Posts: 214 Joined: 02 Feb 2010, 23:10. The answer from Storagecraft, today: ----- There is a know issue on the 4.2.7 RE. Form some system, even if you don't do an HIR, there can be problems on the restored system. You you encounter these issue please use the 4.2.5 version:.iso ----- Not a very satisfactory answer.

So, until the problem is really resolved, do not use RE 4.2.7 to restore a boot partition. Rather use RE 4.2.5. This will even restore a 4.2.7 image as I found (non HIR full backup) out.

Regards, Teunis Post=83328 3StarLounger Posts: 214 Joined: 02 Feb 2010, 23:10.

Comments are closed.