Windows 10: [SetupPlatform.exe] failed to set WinRE settings, error:0xb7

2022-08-28 15:44:30, Error CSI 00000001 F STATUS_OBJECT_NAME_NOT_FOUND #12# from Windows::Rtl::SystemImplementation:irectRegistryProvider::SysQueryValueKeyflags = 0, key = 9a8 '\REGISTRY\MACHINE\SYSTEM\Setup', vn = [l:7 ml:8]'Compact', kvic = 2, kvi = 2, disp = 0[gle=0xd0000034]2022-08-28 15:44:30, Error CSI 00000002 F STATUS_OBJECT_NAME_NOT_FOUND #11# from Windows::Rtl::SystemImplementation::CKey::QueryValueflags = 0, kn = [l:31]'\Registry\Machine\SYSTEM\Setup\', vn = [l:7 ml:8]'Compact', ic = KeyValuePartialInformation, info = {l:0 b:}, disp =

:)

 

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

re-attached.
To sum it up, basically I am stuck with unusable half disk free space now.
This is the error message trying to convert to dynamic drive:



I want either convert to GPT/dynamic disk or swap RecoveryPartition4 for DATApartition4 and stay with MBR disk. In either case I want to keep current windows 10 installation bootable and preferably resolve Windows Recovery issues and have it functional with at least one (=Dell) or more (=Dell + any Windows created) recovery images mapped.
What options do I have and how can I do it?

 

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:

after WinRecovery upgrade:
Code:

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

 

Sound card amplification settings

Yeah unfortunately ASUS and Realtek are not stepping up and fixing this it seems. Wherever I see such problems mentioned on forums some users are suggesting just uninstalling the Realtek driver and using the Windows audio driver.