1.    03 May 2017 #1
    Join Date : May 2017
    Posts : 5
    win10

    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):
    Click image for larger version. 

Name:	disks.PNG 
Views:	2 
Size:	41.3 KB 
ID:	133334
    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):
    Click image for larger version. 

Name:	oem.ReAgent.xml.png 
Views:	1 
Size:	106.4 KB 
ID:	133325
    but BEFORE WinRecovery update (ver 1.0 -> 2.0), here is OEM vs updated ReAgent.xml:
    Click image for larger version. 

Name:	updated.ReAgent.xml.png 
Views:	2 
Size:	144.9 KB 
ID:	133327
    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:
    ReAgent.log
    It logged some errors, looks like it tried to do something with Y: which is strange, since it was never mounted
      My ComputerSystem Spec
  2.    03 May 2017 #2
    Join Date : Jun 2015
    Posts : 217
    trying to install win10

    Invalid attachment.
      My ComputerSystem Spec
  3.    03 May 2017 #3
    Join Date : May 2017
    Posts : 5
    win10
    Thread Starter

    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:
    Click image for larger version. 

Name:	dynDriveMess.PNG 
Views:	2 
Size:	73.9 KB 
ID:	133352
    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?
    Last edited by jfb; 03 May 2017 at 16:16.
      My ComputerSystem Spec
  4.    03 May 2017 #4
    Join Date : Jun 2015
    Posts : 217
    trying to install win10

    Did you disable it first?
    C:\Windows\System32\Reagentc.exe /disable
      My ComputerSystem Spec
  5.    03 May 2017 #5
    Join Date : May 2017
    Posts : 5
    win10
    Thread Starter

    disable first before what?
    no, I haven't touched it. I just stumbled upon another thread here which has some nice reagent /info output so I checked mine out of curiosity and noticed problems.
    I don't know if windows installer disabled it or not.
    All what can be seen in the log file started automatically. I used "reagent /info" command only.
    Last edited by jfb; 04 May 2017 at 01:18.
      My ComputerSystem Spec
  6.    03 May 2017 #6
    Join Date : Jun 2015
    Posts : 217
    trying to install win10

    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
      My ComputerSystem Spec
  7.    04 May 2017 #7
    Join Date : May 2017
    Posts : 5
    win10
    Thread Starter

    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:?
      My ComputerSystem Spec
  8.    4 Weeks Ago #8
    Join Date : May 2017
    Posts : 5
    win10
    Thread Starter

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

 


Similar Threads
Thread Forum
Connection was already enabled but failed with error 651.
Screenshot 1: Connection was already enabled as shown below. 132438 Screenshot 2: Connection failed with error 651 as shown below. 132439 Two days ago, the above problem suddenly arose. The only solution was to unplug the LAN cable and...
Network and Sharing
failed to start with the following error: 0xC0000022
Okay so after downloading the latest cumilative update, not the creators update I got this error Session "Microsoft.Windows.UniversalNotificationPlatform" failed to start with the following error: 0xC0000022. Any idea how to fix this?
General Support
Unexpected error failed installation (Windows 10)
So I've bought a new PC (Windows 10) and with the first Start I get a message saying: "The computer restarted unexpectedly or encountered an unexpected error. Windows installation can not proceed. To install Windows, click "OK" to restart...
Installation and Upgrade
Win 10 Activation failed (Error code: 0xC004C003)
ok so I was going to do a clean install of windows 10 after I upgraded using the media creation tool you can see a post I made here I used the media creation to put win 10 home on a usb then I went to install I skipped the product key part because I...
Windows Updates and Activation
Error from old software: Failed to register the DLL's
I have an old software title that will not work on the new Win10. It seems to install OK, but when I reboot and start the program, the error message is: Failed to register the DLL's that the program requires. Is there a fix for this? The...
Software and Apps
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 11:40.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums