{REAGENTC.EXE: Unable to update Boot Configuration Data} presumably due to multiple system partition
Hello everyone,
About half a year ago I cloned my C: drive to a 2TB HDD using macrium reflect, since then, every time I try to enable ReagentC in CMD this error appears: “REAGENTC.EXE: Unable to update Boot Configuration Data”.
Doing some research I stumbled along this thread of somebody having the same issue. The person with the marked answer on that thread noticed that OP had 2 partitions on his drive functioning as system partitions, the C: partition and the EFI System partition (which should be the lone system partition).
This seemed to be the underlying issue that was causing the earlier mentioned ReagentC error because after OP resolved this, ReagentC /enable worked just fine. The only issue is that the solution provided in the marked answer didn’t work for me and I still have 2 partitions acting as system partitions which, I believe, are conflicting with one another. I haven’t yet experienced any signs of a corrupted recovery partition but want to make sure everything with it is in order to be on the safe side. I’m not even really sure what ReagentC does and if it is essential to have it enabled to be honest.
I could be totally wrong on any assessment I made in this post, if so, feel free to point this out. If you have any further suggestions, advice or commands to run to make ReagentC /enable work, please share.
Thanks in advance!
Hello everyone, About half a year ago I cloned my C: drive to a 2TB HDD using macrium reflect, since then, every time I try to enable ReagentC in CMD this error appears: “REAGENTC.EXE: Unable to update Boot Configuration Data”. Doing some research I stumbled along this thread of somebody having the same issue. The person with the marked answer on that thread noticed that OP had 2 partitions on his drive functioning as system partitions, the C: partition and the EFI System partition (which should be the lone system partition). This seemed to be the underlying issue that was causing the earlier mentioned ReagentC error because after OP resolved this, ReagentC /enable worked just fine. The only issue is that the solution provided in the marked answer didn’t work for me and I still have 2 partitions acting as system partitions which, I believe, are conflicting with one another. I haven’t yet experienced any signs of a corrupted recovery partition but want to make sure everything with it is in order to be on the safe side. I’m not even really sure what ReagentC does and if it is essential to have it enabled to be honest. I could be totally wrong on any assessment I made in this post, if so, feel free to point this out. If you have any further suggestions, advice or commands to run to make ReagentC /enable work, please share. Thanks in advance! Read More