Windows 10: REagentC went mad

Discus and support REagentC went mad in Windows 10 Installation and Upgrade to solve the problem; I want to set up recovery image location for Windows to custom partion but REagentC went mad. 1. Query info C:\windows\system32>reagentc /info... Discussion in 'Windows 10 Installation and Upgrade' started by User919, Dec 24, 2019.

  1. User919 Win User

    REagentC went mad


    I want to set up recovery image location for Windows to custom partion but REagentC went mad.


    1. Query info


    C:\windows\system32>reagentc /info


    Windows Recovery Environment Windows RE and system reset configuration

    Information:


    Windows RE status: Disabled

    Windows RE location:

    Boot Configuration Data BCD identifier: df4df9ad-2675-11ea-a53d-f4d0b4349d0d

    Recovery image location:

    Recovery image index: 0

    Custom image location:

    Custom image index: 0


    REAGENTC.EXE: Operation Successful.


    2. Enable agent


    C:\windows\system32>reagentc /enable

    REAGENTC.EXE: Operation Successful.


    3. Disable agent


    C:\windows\system32>reagentc /disable

    REAGENTC.EXE: Windows RE is already disabled.


    4. Enable agent again


    C:\windows\system32>reagentc /enable

    REAGENTC.EXE: Operation Successful.


    5. Query info again


    C:\windows\system32>reagentc /info


    Windows Recovery Environment Windows RE and system reset configuration

    Information:


    Windows RE status: Disabled

    Windows RE location:

    Boot Configuration Data BCD identifier: df4df9ad-2675-11ea-a53d-f4d0b4349d0d

    Recovery image location:

    Recovery image index: 0

    Custom image location:

    Custom image index: 0


    REAGENTC.EXE: Operation Successful.


    Previously agent had problems writing to BCD – REAGENTC.EXE:Unable to update Boot Configuration Data.– that was worked around by specifying the BCD guid using/osguid parameter.


    1. Loaders query


    C:\windows\system32>bcdedit /enum osloader /v


    Windows Boot Loader

    -------------------

    identifier {df4df9aa-2675-11ea-a53d-f4d0b4349d0d}

    device partition=C:

    path \windows\system32\winload.efi

    description Windows 10

    locale cs-cz

    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \windows

    resumeobject {df4df9a9-2675-11ea-a53d-f4d0b4349d0d}

    nx OptIn

    bootmenupolicy Standard


    2. Agent write


    C:\windows\system32>reagentc /enable /osguid{df4df9aa-2675-11ea-a53d-f4d0b4349d0d}

    REAGENTC.EXE: Operation Successful.


    3. Loaders query again


    C:\windows\system32>bcdedit /enum osloader /v


    Windows Boot Loader

    -------------------

    identifier {df4df9aa-2675-11ea-a53d-f4d0b4349d0d}

    device partition=C:

    path \windows\system32\winload.efi

    description Windows 10

    locale cs-cz

    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}

    recoverysequence {df4df9b1-2675-11ea-a53d-f4d0b4349d0d}

    recoveryenabled Yes

    isolatedcontext Yes

    allowedinmemorysettings 0x15000075

    osdevice partition=C:

    systemroot \windows

    resumeobject {df4df9a9-2675-11ea-a53d-f4d0b4349d0d}

    nx OptIn

    bootmenupolicy Standard



    Windows Boot Loader

    -------------------

    identifier {df4df9b1-2675-11ea-a53d-f4d0b4349d0d}

    device ramdisk=[X:]\Recovery\WindowsRE\Winre.wim,{df4df9b2-2675-11ea-a53d-f4d0b4349d0d}

    path \windows\system32\winload.efi

    description Windows Recovery Environment

    locale cs-cz

    inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}

    displaymessage Recovery

    osdevice ramdisk=[X:]\Recovery\WindowsRE\Winre.wim,{df4df9b2-2675-11ea-a53d-f4d0b4349d0d}

    systemroot \windows

    nx OptIn

    bootmenupolicy Standard

    winpe Yes

    custom:46000010 Yes


    4. Agent info


    C:\windows\system32>reagentc /info /osguid {df4df9aa-2675-11ea-a53d-f4d0b4349d0d}


    Windows Recovery Environment Windows RE and system reset configuration

    Information:


    Windows RE status: Disabled

    Windows RE location:

    Boot Configuration Data BCD identifier: df4df9b1-2675-11ea-a53d-f4d0b4349d0d

    Recovery image location:

    Recovery image index: 0

    Custom image location:

    Custom image index: 0


    REAGENTC.EXE: Operation Successful.

    :)
     
    User919, Dec 24, 2019
    #1
  2. cseabrook Win User

    ReagentC "operation failed: 32"

    Hello.

    What, exactly, does "operation failed: 32" mean when it comes from ReagentC?

    Is their a published list of all of the ReagentC failure numbers, and what they mean or what triggers them?
     
    cseabrook, Dec 24, 2019
    #2
  3. Reagentc failed

    Empty recovery image location string. Setting image path before winre enabling needed.
    perform these steps:

    1. set drive letter to recovery partition
    2. reagentc /setreimage /path F:\Recovery\WindowsRE
    ...winre.wim registration (use proper drive letter)
    3. reagentc /enable
    ...winre activating
    4. remove drive letter from recovery partition

    Can't enable Windows Recovery Environment
     
    muchomurka, Dec 24, 2019
    #3
  4. topgundcp Win User

    REagentC went mad

    How does Windows boot to advanced recovery option e.g. command prompt?


    - that gives me a 454 'Unexpected error' This tells me that the BCD is partially corrupted.

    The commands: shutdown.exe /r /o /f /t 00
    or: %SystemRoot%\System32\Cmd.exe /c reagentc /boottore&shutdown /r /f /t 00
    should boot into Recovery if everything is configured correctly.
    FYI, If Windows is configured correctly:
    1. If Reagentc is disabled, you still can get into Recovery but with limited options.
    2. If Reagentc is enabled, you'll get all options.
    3. If you boot Windows using Recovery USB stick, You'll get into Recovery with couple of options missing.

    Here's my suggestion if you want to try:
    OPTION 1: Will save the trouble of re-install Windows.

    1. Download the image of my first 3 partitions (450MB Recovery, 100 MB EFI partition, and 16MB unformatted primary)
      EFI_Boot-00-00.7z - Google Drive
    2. Run Macrium and restore the image from step 1, overwriting your existing 1st three partitions, leaving C alone.
    3. Delete the 490MB Recovery partition.
    4. From Macrium, run fix boot problems.
    5. Reboot. Open Admin command prompt then run Reagentc /info to make sure that it is enabled. If not, enable it.
      if failed to enable, reboot and try again.
    OPTION 2: Assuming you've already had Windows backup with Macrium.

    1. Wipe out the first 5 parttiions. (450MB, 100MB, 16MB, C Drive, 480MB)
    2. Fresh install Windows 10
    3. Restore C drive from backup image, run fix boot problems
    4. repeat step 5 from OPTION 1 above.
     
    topgundcp, Dec 24, 2019
    #4
Thema:

REagentC went mad

Loading...
  1. REagentC went mad - Similar Threads - REagentC went mad

  2. help me reagentc error

    in Windows 10 Gaming
    help me reagentc error: When I use the reagentc /enable reagentc /info command. This command can only be executed from an elevated command prompt.REAGENTC.EXE: Operation failed: 5REAGENTC.EXE: An error has occurred. it gives this error...
  3. help me reagentc error

    in Windows 10 Installation and Upgrade
    help me reagentc error: When I use the reagentc /enable reagentc /info command. This command can only be executed from an elevated command prompt.REAGENTC.EXE: Operation failed: 5REAGENTC.EXE: An error has occurred. it gives this error...
  4. help me reagentc error

    in Windows 10 Software and Apps
    help me reagentc error: When I use the reagentc /enable reagentc /info command. This command can only be executed from an elevated command prompt.REAGENTC.EXE: Operation failed: 5REAGENTC.EXE: An error has occurred. it gives this error...
  5. Autoplay Madness

    in Windows 10 Support
    Autoplay Madness: I turned off Autoplay in settings I turned off Autoplay in Group Policy (both system and user) I set the default autorun behaviour to "do not execute any autorun commands" (both system and user) and yet, I have a USB stick that when inserted brings up a Run window and types...
  6. ReAgentC will not ENable

    in Windows 10 Performance & Maintenance
    ReAgentC will not ENable: ISSUE: In Windows 10 Pro v1909 reagentc.exe cannot ENable from an elevated command prompt -- "The Windows RE image was not found." QUESTIONS: Does it even need to, per 18918 "Can't enable Windows Recovery Environment"? (or) Should I just follow the steps in 90923 "Enable...
  7. REagentC works badly

    in Windows 10 Installation and Upgrade
    REagentC works badly: I want to set up recovery image location for Windows to custom partion but REagentC went mad. 1. Query info C:\windows\system32>reagentc /info Windows Recovery Environment Windows RE and system reset configuration Information: Windows RE status: Disabled...
  8. Reagentc failed

    in Windows 10 Support
    Reagentc failed: Shawn or other friend; in using MBR2GPT this am on a fresh install for which I used Win usb media - all of which went well, the conversion went well, but the edit to Reagentc failed. I thought, per the suggestion in the MBR2GPT.exe helps, to disable /enable but it all fails....
  9. midtown madness 2

    in Windows 10 Gaming
    midtown madness 2: i played midown madness 2 a month ago but today its saying direct x 7 is required i have direct x 12 installed i also have the game running under as windows xp service pack 2 i have directplay on...
  10. IM GOING MAD!

    in Windows 10 BSOD Crashes and Debugging
    IM GOING MAD!: hey guys, i have a REAL PAIN IN THE BRAIN problem! i cant use (code Completion or what ever name it has) in anyyyyy WINDOWS, and Visual Studios 2015 and 2017 and Visual Studio Code, IntelliJ and Eclipse android Studio and OTHERSSS........... its about 2 month! im rly mad...

Users found this page by searching for:

  1. the file reagentc.exe could not be found in any standard locations

    ,
  2. REAGENTC.EXE: Operation failed: b7

    ,
  3. reagentc.exe unable to update boot configuration data