Multi-BOOT Partition Anomaly

[Froggie]

@al3x, you may be right.


Same as above, this time with a single change to the Win11 OS partition prior to the above process.  No CHKDSK issues prior to the restore, no CHKDSK issues after the restore (only the Win10 disk ERROR msg like before).  reBOOT the System for ordered repair operation, no repair done.  This was different from yesterday as Win10 always did the repair scan during the reBOOT (never found any errors though).

As @al3x has suggested, the "no repair scan" following the reBOOT may have been caused by my CHKDSK scan (none of this was done yesterday), which found nothing... may have cleared the dirty bit prior to the reBOOT so no repair scan done this time.

Who knows... Win10's DIRTY may not be the same as everybody else's "dirty" 

[Froggie]

@al3x, you may be right.


Same as above, this time with a single change to the Win11 OS partition prior to the above process.  No CHKDSK issues prior to the restore, no CHKDSK issues after the restore (only the Win10 disk ERROR msg like before).  reBOOT the System for ordered repair operation, no repair done.  This was different from yesterday as Win10 always did the repair scan during the reBOOT (never found any errors though).

As @al3x has suggested, the "no repair scan" following the reBOOT may have been caused by my CHKDSK scan (none of this was done yesterday), which found nothing... may have cleared the dirty bit prior to the reBOOT so no repair scan done this time.

Who knows... Win10's DIRTY may not be the same as everybody else's "dirty" 

Indeed I always create the required reBOOT repair process if I don't run CHKDSK prior to the reBOOT.  Something's "dirty" but I have no idea what since I don't know what Win10 uses for its "dirty" criteria... and HBS definitely tweaks it whatever it is.

[admin]

@Froggie,

Strangely, I wasn't able to reproduce the issue. Do I need specific steps, or special restore options, like the Delta restore option? 

I checked the dirty bit, and it doesn't seem to be problematic.

Thanks.

Best regards,

[Froggie]

No special sequence other than my description above.  Yes, I used Delta Restore but I believe it wouldn't make any difference either way.

Let's chalk this up to a personal System Win10 anomaly (the results are always good so it's not critical in any way), no more effort on your part until you hear more from this end on exactly what may be going on.

Thank you for your effort up until now!  Onward & upward (v6...?)... 

[admin]

@Froggie,

I wonder if this issue is related to specific Windows 10/11 build versions. I've already tried both with and without the Delta Restore feature, but still couldn't reproduce the problem on my end.

Although this anomaly doesn't have any real impact on the restore functionality itself, it would still be great to identify the root cause if possible. Otherwise, some users might mistakenly assume it's entirely an issue with Hasleo Backup Suite, which could lead to a loss of trust in the software.

Also, just wanted to say - thanks for your continued attention to V6!

Have a nice day!

Best regards,

[Froggie]

Greetings!  I have built an identical multi-BOOT System on a different hardware platform (AMD Ryzen) and cannot reproduce the error in question.  While I do not believe that the Intel HP platform is the reason for throwing the error, I will be doing a REPAIR UPGRADE on that platform to try and eliminate any corruption that may have occurred over a very long period of time.

I'll report the results when done...

[admin]

@Froggie,

Thank you for your further testing and feedback.

I'm personally more inclined to suspect that this is an issue related to a specific Windows 10 build version. Could you please let us know the exact build number of your Windows 10 system?

We'll be waiting for your update after the repair upgrade as well.

Have a great weekend!

Best regards,

[Froggie]

Windows 10 IoT Enterprise LTSC (21H2 OS Build: 19044.7548)

The REPAIR UPGRADE went as well as could be expected (it broke lots of small things along the way) BUT... it no longer throws the original error upon the HBS Restore.

I guess that's a good thing...   

I think we should just move on from this (and maybe I should REFRESH my System every few years)...

[admin]

@Froggie,

Thanks for the details! Great to hear the repair upgrade fixed it. Agreed, let's move on. Have a nice day!

Best regards,