Posts: 522
Threads: 42
Joined: Dec 2022
Reputation:
51
07-30-2026, 11:22 PM
(This post was last modified: 07-31-2026, 12:16 AM by Froggie.)
Greetings... strange phenomena today.
I run a multi-BOOT System (Win10, Win11, Linux) and my main backup configuration is Disk-based rather than System-based, including the normal System partitions to recover the Win10 System (that's where I run the imaging from) plus the Win11 OS partition... 5-partitions in total).
Today I decided to restore just my Win11 OS partition from Win10. Since the Win11 partition was not active at this time, I expected to be able to do this without any required reBOOT into the Emergency Disk. It did exactly that but at the end of the process, while in HBS, the LIVE Win10 System shot up a disk error (Restart to repair drive errors!) that would require a checkdisk on the next reBOOT. I reBOOTed the System and the Checkdsk ran on Win10 for a while and finished, no major issues. ReBOOTed into Win10, all OK... reBOOTed in Win11 and the restoration was fine.
Anybody have any ideas what may have happened and why? Normally, recovering a non-Active partition on the same disk that holds the LIVE OS is never an issue.
Posts: 3,442
Threads: 20
Joined: Feb 2014
Reputation:
323
@Froggie,
It is indeed quite rare to suddenly get a disk error prompt while Windows 10 is running, at least I have never encountered it myself. Are you sure the prompt was indicating a file system error on the current C: drive? Could it have been a file system error on the newly restored Windows 11 volume instead?
In principle, HBS writes data blocks directly to the target partition through the underlying disk driver, and it does not touch the current system partition. Moreover, Windows itself protects the running system partition and does not allow other programs to write to critical system files arbitrarily. So from both a permission and operational object perspective, it should not trigger a "repair disk" error on Windows 10 itself.
Given that the restoration ultimately succeeded and both systems are running fine, it is most likely not a serious issue. However, if you want to get to the bottom of it, the most straightforward approach is to check the Event Viewer logs around the time of the restoration. Look for error events from disk, ntfs, or volmgr sources, along with specific error codes, that might provide some clues.
Have a nice day!
Best regards,
Posts: 522
Threads: 42
Joined: Dec 2022
Reputation:
51
08-02-2026, 03:59 PM
(This post was last modified: 08-02-2026, 04:35 PM by Froggie.)
Greetings... sorry, just got around to this! Below are the two relevant EVENTs occurring at the time of the SYSTEM error. The GUID mentioned is the very same Win11 OS partition that was recovered while running LIVE under Win10. Since the Win11 OS partition was not locked at the time of the Recovery, the Recovery completed fine under the LIVE Win10 System but threw the errors below.
The Win10 SYSTEM sees the Win11 OS partition but has it unlettered to protect it from any Win10 casual use. Apparently the restoration of the Win11 OS partition caused Win10 to throw the error below.
I'll be happy to repeat the operation if needed.
Event#98
Volume \\?\Volume{9ff86e28-fea6-4ae3-99ec-1e135ae2fe96} (\Device\HarddiskVolume12) needs to be taken offline to perform a Full Chkdsk. Please run "CHKDSK /F" locally via the command line, or run "REPAIR-VOLUME <drive:>" locally or remotely via PowerShell.
Event#55
A corruption was discovered in the file system structure on volume \\?\Volume{9ff86e28-fea6-4ae3-99ec-1e135ae2fe96}.
The exact nature of the corruption is unknown. The file system structures need to be scanned and fixed offline.
Posts: 522
Threads: 42
Joined: Dec 2022
Reputation:
51
08-02-2026, 04:34 PM
(This post was last modified: 08-02-2026, 04:36 PM by Froggie.)
(08-02-2026, 03:59 PM)Froggie Wrote: I'll be happy to repeat the operation if needed.
This issue is completely repeatable. I have no idea what HBS is doing to the unlocked Win11 OS partition to cause Win10 to throw this error.
Remember, the error is coming from Win10, not Hasleo... Hasleo completes its operation just fine.
What would you like me to do to help?
Posts: 3,442
Threads: 20
Joined: Feb 2014
Reputation:
323
The NTFS partitions created by Windows 11 might be a bit different from those created by Windows 10, so we need some time to look into the issue.
Posts: 522
Threads: 42
Joined: Dec 2022
Reputation:
51
08-03-2026, 07:19 PM
(This post was last modified: 08-03-2026, 07:21 PM by Froggie.)
Some food for thought... when I do the exact same thing from the LIVE Win11 side of the dual-BOOT (restoring the unlocked Win10 partition) there are no errors  . Both Systems are running ENTERPRISE LTSC IoT Windows versions (shouldn't really mean anything).
Posts: 3,442
Threads: 20
Joined: Feb 2014
Reputation:
323
@Froggie,
Please boot into Windows 10, then open Windows Explorer and navigate to the Windows 11 partition. After that, run chkdsk on that partition and check whether any error messages are reported.
I will install both Windows 10 and Windows 11 on the same computer tomorrow for testing.
Thanks.
Best regards,
Posts: 522
Threads: 42
Joined: Dec 2022
Reputation:
51
As the Wn11 partition is hidden under a LIVE Win10, I will unhide it and run your requested CHKDSK.
Following that, I will do the restore that creates the condition. At that point I will unhide the hidden Win11 OS partition and run the requested CHKDSK once again. After that I will perform the repair.
I will pass on my observations...
Posts: 354
Threads: 16
Joined: Nov 2024
Reputation:
84
Would be interesting to know if the partition was actually corrupted somehow or if Windows just sets the dirty bit.
Also: Does chkdsk find any errors that need repairing? Or does it simply quit without doing anything except for removing the dirty bit?
I would assume the partition is healthy after the restore but Win10 sets the dirty bit wrongly.
Posts: 522
Threads: 42
Joined: Dec 2022
Reputation:
51
08-04-2026, 04:42 PM
(This post was last modified: 08-04-2026, 04:43 PM by Froggie.)
@al3x, you may be right.
I run a CHKDSK on the hidden Win11 OS partition, no changes since image, prior to a restore... no issues. Run the restore, Win10 kicks out the ERROR and orders the repair upon reBOOT. I run CHKDSK once again, no issues. reBOOT the Win10 System for the repair operation, no repair done.
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).
This just may be some obscure Win10 bug... only guessing here. I'm not sure I'd be spending too much time chasing it down.
PS- I can supply CHKDSK output if needed (all the checks came out the same).
|
