Reagentc.exe WinReSetConfig failed: error 0xb7, error 0x3

Hi *,
I have upgraded hdd in laptop and run into some problems, he is my situation:
cloned the oem Dell laptop hdd to a new ssd, which went fine, here is the configuration (disk1/O: is the old C: on hdd, disk0/C: is the C: clone on ssd):

After that I upgraded preinstalled Win7 to Win10, which went also fine.
At some point after the upgrade Windows recovery started some update and messed with the new ssd drive and Windows recovery configuration, created new recovery partition (now 4 in total), so now I am left with half a drive free space and cannot add another partition for data (as D: drive), because the drive is MBR type, which support only up to 4 partitions. Windows Computer management can add a new partition by converting the ssd to dynamic drive, but before the conversion starts it says there is not enough free space for the conversion conversion to complete (and it gets cancelled before it starts). I also noticed that reagent log has logged some errors and configured to recover from the newly created partition4 instead of previously configured partition2 from Dell.
What can I do about it? How to clean things up and resolve those errors?
Could I just remove the partition4 on disk0 and revert changes made to Windows Recovery to restore OEM state and create new partiotion4 for data (drive d: ) What command do I need to use for that? Or can I just copy the OEM ReAgent.xml? Would it suffice to revert the changes made by WinRecovery (remember partitions 1-3 are cloned from oem hdd so offsets and everything should fit, not sure about WinreBCD id and the bumped version 1.0 -> 2.0)?
Also I would like to set up multi boot with some Linux after resolving windows Recovery issues (will need even more partitions) so conversion to GPT/dynamic disk is preferred anyway.
OEM:

Code:

C:\WINDOWS\system32>reagentc /info /target O:\Windows /logpath c:\temp\reagent.temp.log
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: 0c86fbed-dcb5-11e5-b801-9cebe82b2096
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

after WinRecovery upgrade:

Code:

C:\WINDOWS\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: a35f7539-129e-11e7-af3f-b5a839488f9e
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

here is the OEM ReAgent.xml compared to ReAgent after Windows upgrade (7->10, binary identical):

but BEFORE WinRecovery update (ver 1.0 -> 2.0), here is OEM vs updated ReAgent.xml:

On the old hdd the is no ReAgent.log file, in win10 on the ssd there was one created in the process of updating the Win Recovery in C:\Windows\Logs\ReAgent\ReAgent.log:
Attachment 133331
It logged some errors, looks like it tried to do something with Y: which is strange, since it was never mounted

Invalid attachment.

Did you disable it first?
C:\Windows\System32\Reagentc.exe /disable

I would copy the recovery folder from the 813mb partition into the 11.73gb partition,. You may have to make it a bit larger. Then configure reagentc.

Next I would delete the 813mb.

If you don't have a partition manager, you can use this Free Partition Manager Software - AOMEI Partition Assistant Standard

Are there any other options?
What about errors in the log, why it tried to access Y: ? Can I repeat those steps manually with corrected path? Where was it configured to access Y:?

I may end up doing new partitioning from scratch and clean install win10. How to bind that original DELL recovery partition?