Windows RestorePoints not shown anymore after IFW diskimage

[Byterate]

After restoring the Win10 system partition with IFW, Windows System Restore reports “No restore points have been created…”.
However the RestorePoints are still present in the System Volume Information folder but not shown in Windows System Restore.
New restore points can be created without problem. But all earlyer RP’s are not shown anymore.
Happens after every IFW diskimage restore.

[attachment=2]Windows System Restore images before IFW restore.png[/attachment]
[attachment=1]Windows System Restore images vanished after IFW restore_1.png[/attachment]
[attachment=0]Windows System Restore images vanished after IFW restore_0.png[/attachment]

[TeraByte Support]

That is a feature of VSS, although even if you tick off Skip Files to Not
Backup it will still skip any VSS Provider files if using VSS (shouldn't be
any left in the system volume information after restore).

Use PHYLock to get restore points restored.


"Byterate" wrote in message news:14677@public.image...

After restoring the Win10 system partition with IFW, Windows System Restore
reports "No restore points have been created?".
However the RestorePoints are still present in the System Volume Information
folder but not shown in Windows System Restore.
New restore points can be created without problem. But all earlyer RP's are
not shown anymore.
Happens after every IFW diskimage restore.

[attachment=2]Windows System Restore images before IFW
restore.png[/attachment]
[attachment=1]Windows System Restore images vanished after IFW
restore_1.png[/attachment]
[attachment=0]Windows System Restore images vanished after IFW
restore_0.png[/attachment]

[Byterate]

IFW backup and restore are created from WinPE bootable ISO, so i.m.h.o. VSS or volume lock shouldn’t be an issue or relevant.
While IFW creates and restores a image, partition before and after should be identical. They obvious are NOT.

[TeraByte Support]

If you have any backups that used vss or used "read from volume" then those
files would be skipped and deleted on restore.

As far as the restore point interface, the volume guid and other information
are stored in the restore point, if you choose to have it change the disk
id's and/or guids (or you have duplicates and windows access it and changes
it) it's possible that's what it's trying to match on won't be found. But
restoring normally from using offline or phylock leaves the restore points
in place.

Provide a partinfo export listing (installed with IFW or via free downloads
(partinfg) ) of both the source and target drives. Also the log from
restore if you have it. And the output from "mountvol" for each booted
instance (before / after).


"Byterate" wrote in message news:14679@public.image...

IFW backup and restore are created from WinPE bootable ISO, so i.m.h.o. VSS
or volume lock shouldn't be an issue or relevant.
While IFW creates and restores a image, partition before and after should be
identical. They obvious are NOT.

[TeraByte Support]

It's also important to note that vss / restore points are block oriented
from start of volume. Any changes that occur outside of the windows
environment that is logging the changes won't be logged. This can lead to
corrupt to a volume upon using an older restore point. Upon any unmonitored
changes to a volume, a new restore point should be created and all prior
deleted. You may get away with it for a number of things, but it's not
going to be totally reliable in those cases.

[Byterate]

The problem is in imagew64.exe version 3.16.
Nothing wrong with the WinPE created v3.16 backup image.
After WinPE restoring the image with imagew64.exe v3.16, the Windows Restore Points are present in the Volume Information Folder but not shown in Windows System Restore, as already stated and illustrated before in this topic.
After WinPE restoring the image with imagew64.exe v3.13 everything is fine and the restore points are shown in Windows System Restore.
So it's a 3.16 issue

[Brian K]

Byterate wrote:

> So it's a 3.16 issue

Byterate,

I just ran this test. Win10 IFW 3.16. System Restore was turned ON and 3 Restore Points were created.

An Entire Drive image was created in TBWinPE. The image was then restored and Win10 loaded. The 3 Restore Points were present.

[Byterate]

Brian K wrote:
> Byterate wrote:
>
> > So it's a 3.16 issue
>
> Byterate,
>
> I just ran this test. Win10 IFW 3.16. System Restore was turned ON and 3 Restore
> Points were created.
>
> An Entire Drive image was created in TBWinPE. The image was then restored and Win10
> loaded. The 3 Restore Points were present.

Brian, Try a partition image backup and restore instead of entire disk

[Brian K]

Byterate wrote:
>
> Try a partition image backup and restore instead of entire disk

Byterate,

I did as you suggested. Created a Win10 partition image in TBWinPE and then restored the image. I saw the same result as your second screenshot. The restore points were gone.

Edit... I repeated the same test but using IFL for the partition backup/restore. The restore points were still present.

The partition image created by TBWinPE was restored by IFL. The restore points were still present.
The partition image created by TBWinPE was again restored by TBWinPE. The restore points were NOT present.

This suggests the TBWinPE restore is the culprit.

[TeraByte Support]

again, providing the partinfo export listing, restore log, output from
"mountvol" for each booted instance (before/after) or (exist/don't exist).


"Byterate" wrote in message news:14693@public.image...

Brian K wrote:
> Byterate wrote:
>
> > So it's a 3.16 issue
>
> Byterate,
>
> I just ran this test. Win10 IFW 3.16. System Restore was turned ON and 3
> Restore
> Points were created.
>
> An Entire Drive image was created in TBWinPE. The image was then restored
> and Win10
> loaded. The 3 Restore Points were present.

Brian, Try a partition image backup and restore instead of entire disk