W10 C: partitions are in an odd order

Restore
1

All my backups and restore testing seems to work EXCEPT the machines that have this issue.
If the Windows10 C-drive is showing in Disk Management as:
Works: Boot partition + Recovery partition + OS partition.
Errors: OS partition + Boot partition + Recovery partition.

Whenever I try to do a restore with the partitions in a strange order… UrBackup seems to be trying
to install the big 400GB OS partition… into the small 100MB boot/recovery partitions. I get the “wrong size error”.

Does anyone have a solution for that? I’m not sure how some of our computers got their partitions arranged in an odd order… but they did… and they boot/function normally… but they can never be restored with UrBackup.

2

Could you upload the .mbr files of the images? They contain the partition number to restore to and the partitioning data itself (MBR + GPT).

W.r.t. to finding the SYSVOL correctly the output of “C:\Program Files\UrBackup\sysvol_test.exe” (as admin) should be interesting.

3

This is the output of Sysvol_Test.exe on a Windows Server 2019 machine.
Disk Manager shows the partitions in this order: Recovery, boot, OS
(Sysvol_Test.exe never fully exited, even after running for 5 minutes.
I had to hit Ctrl-C to get out of it.)

Filesystem. Vol="\?\Volume{ef31f6d4-fb6a-47ce-9164-5e5a4d114d56}" Name=“recovery” Type=“ntfs” VPaths=0 Size=523235328
GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775807
Do not automount is set
System partition is set
Bootable flag set for volume
Found potential candidate: \?\Volume{ef31f6d4-fb6a-47ce-9164-5e5a4d114d56}\ Score: 3
Filesystem. Vol="\?\Volume{b7223eb4-9fd1-423c-b94f-923f3e7b3af3}" Name="" Type=“ntfs” VPaths=1 Size=249413234688
Filesystem is System partition. Skipping…
Filesystem. Vol="\?\Volume{e16c6ab3-f2fe-4923-8e5a-474ba6e02216}" Name=“1tb” Type=“ntfs” VPaths=1 Size=1000203087872
GPT formated hard disk encountered. No bootable flag. Attributes = 0
Bootable flag not set for volume
Filesystem. Vol="\?\Volume{74c80bab-1cb7-4af4-bd7e-db0d3766af68}" Name=“ssd500gb” Type=“ntfs” VPaths=1 Size=500090007552
GPT formated hard disk encountered. No bootable flag. Attributes = 0
Bootable flag not set for volume
Filesystem. Vol="\?\Volume{9c5be13a-87d4-401b-85f9-911f3338dc8b}" Name="" Type=“fat32” VPaths=0 Size=100663296
GPT formated hard disk encountered. No bootable flag. Attributes = -9223372036854775808
Do not automount is set
Bootable flag not set for volume
Found potential candidate: \?\Volume{9c5be13a-87d4-401b-85f9-911f3338dc8b}\ Score: 3
Filesystem. Vol="\?\Volume{b9aa8fc7-d2b2-11eb-9b0e-d8bbc112ed53}" Name=“raid0-striped” Type=“ntfs” VPaths=1 Size=3000558940160
Error reading partition information for bootable flag (Volume=\?\Volume{b9aa8fc7-d2b2-11eb-9b0e-d8bbc112ed53})
Errno 1
Bootable flag not set for volume
Selected volume \?\Volume{ef31f6d4-fb6a-47ce-9164-5e5a4d114d56}
Found sysvol “\?\Volume{ef31f6d4-fb6a-47ce-9164-5e5a4d114d56}” Path: “”
Trying to open SYSVOL(\?\Volume{ef31f6d4-fb6a-47ce-9164-5e5a4d114d56})…
Successfully opened SYSVOL.
System dir: C:\Windows
Volpath: \.\C:
EFI partition with type UUID {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}
EFI partition with type UUID {C12A7328-F81F-11D2-BA4B-00A0C93EC93B}
EFI System Partition is at \?\GLOBALROOT\Device\Harddisk0\Partition2
Found EFI System Partition “\?\GLOBALROOT\Device\Harddisk0\Partition2” Path: “”
Trying to open EFI System Partition(\?\GLOBALROOT\Device\Harddisk0\Partition2)…
Successfully opened EFI System Partition.