let me guess - deleting the 529-partition will break winre for sure. its still "harddisk0" = disk 0, but no longer "partition 5" so its needed to set winre again with reagentc. user diskpart > select disk 0 list partition to get the proper partition. i dont see any evidence to use additional software for what can be fixed within windows.
Correct, but easily fixed. Diskpart couldn't be used to satisfy Krusty's requirements. Diskpart can't do Slides.
My advice for anyone going through this, take it slowly, one step at a time. Read instructions carefully. If you aren't sure, stop and ask whom ever is helping you. If I can do it I'm sure most Wilders' members can. Many thanks again to @Brian K .
The thing is, Bill, at a certain point it becomes a personalised experience, similar in my opinion to malware removal. I don't have a problem posting step by step the exact struggle, but this isn't a protected forum, and everyone is free to post whatever they want in the thread. As you probably can imagine, that can cause confusion.
i never wrote that: after cloning and moving partitions on my secondary machine, i had to set winre for all windows (3) again. it need some trialing how it works, and it do NOT harm the windows installation itself. for the winre i need some files from the ISO file but that can be done with 7-zip. reagentc is performing the rest. bcdedit /enum all >c:\bcd#.txt will show up all settings, valid or not. (# is a placeholder for numbers counting up: 1, 2, 3 to compare after each action) anyhow only one windows 10 refused kb5034441 because of wrong set winre ("unknown"). and winre is different for efi and mbr - for mbr its on the windows partition, for efi its another partition by default. that far about the update issues with kb5034441 where the partition was too small. but its also possible to put winre on mbr on a different partition, reagentc need to know about at least
