ReAgentC: Operation failed: 3

Hello,

I am running Windows 8.1 with Update 1 on a laptop with BIOS. 

ReAgentC was working fine on my laptop until about 4 days ago. I know it was working fine because I used it to prepare the recovery partition of a Hyper-V VHD on this laptop. However, from the next day or so whenever I run ReAgentC I get "Operation failed: 3". 

C:\Windows\System32>reagentc /info
REAGENTC.EXE: Operation failed: 3

REAGENTC.EXE: An error has occurred.

Both SFC and DISM report no errors on my system:

C:\Users\rakhesh\Desktop>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

Any suggestions on what the problem could be? I am guessing I must have corrupted some setting when using ReAgentC for the VHD but I checked the ReAgent.XML file, the System partition, BCD ... and all seem to be fine. Am happy to post output of these if that helps.

Thanks,

Rakhesh

 

Question Info


Last updated September 15, 2019 Views 3,674 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hello RakheshSasidharan,

Have you tried to Restore your computer to an earlier point of time? if you didn't then you can always give it a try!

On Windows 7:

Go to : Control Panel\All Control Panel Items\Recovery And then click on: "Open System Restore"

And Follow the instructions given after that!

On Windows 8:

Check that link out: http://blogs.msdn.com/b/zxue/archive/2012/03/09/windows-8-how-to-29-restore-system-to-a-previous-state-using-restore-point.aspx

Also there is a bigger chance that one of the files were corrupted and Windows Didn't detect it!

Good Luck,,,,,

Eth.

"Try not to become a man of success, but rather try to become a man of value." Albert Einstein

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello Eth,

Thanks for replying! Nope, I didn't try system restore. I read about it but was leaving it as a last resort. :)

You mention there's a chance some files were corrupted but Windows didn't detect it. Interesting! I thought SFC and DISM /Cleanup-Image were able to detect such corruptions so that came as a surprise. Got any link I can read about this just for my info? 

Also, is there any place where I can find out what "Operation failed: 3" stands for? Does it mean there are corruptions?

Thanks,

Rakhesh

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello again,

I did a System Restore finally, to a point in last week when I know ReAgentC was working. But it still does not work, I'm getting the same error. 

Any suggestions on what I can do now?

Thanks,

Rakhesh

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello RakheshSasidharan, Have you tried to check out system file checker and see if it fixed your problem? if you already scanned and it didn't fix it then do the following:

1. Go to cmd prompt and run it as an admin and type in :

DISM.exe /Online /Cleanup-image /Scanhealth

DISM.exe /Online /Cleanup-image /Restorehealth

type each command after the other not both of them at the same time

2. check ReAgentC to see if you still have that problem

And to know what is those commands above then read:

 technet.microsoft.com/en-us/library/hh824869.aspx

If you still have it then check that link:

http://windows.microsoft.com/en-us/windows-8/restore-refresh-reset-pc

I hope it get fixed,,

Good luck,,,,,,,

Eth

"Try not to become a man of success, but rather try to become a man of value." Albert Einstein

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello Eth,

Yes, I tried SFC - it reported no errors. Tried cleaning up and repairing via the two commands above - again no issues. 

I don't really want to restore/ refresh my PC as that would mean re-installing everything. I double checked WinRE yesterday and that works well, so everything seems to be working well just that I can't use ReAgentC. Weird! :(

Do you know what the error code 3 is supposed to indicate? 

Thanks,

Rakhesh

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello RakheshSasidharan

I am so sad that you didn't fix it yet ,,,

The Error code 3 meaning can be found on that link:

http://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

so It means The system cannot find the path specified.

Are you sure that you configured everything up ? 

Have you tried ReAgentC on an other laptop?

Good Luck,,,,,

Eth.

"Try not to become a man of success, but rather try to become a man of value." Albert Einstein

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Cool! Thanks Eth for the link to the erro code. (You have links for everything! That's nice). :)

Yes ReAgentC works on other laptops. It used to work on this laptop too till about 5 days ago. I was building some VMs and I used ReAgentC to setup the recovery partition of a VM I was building offline. But from the next day it stopped working. So when I did a System Restore I went to a point before I built the VM hoping ReAgentC will work then but it does not. 

I'll try and find what path it's searching for and not finding. Will post here if I have any success. 

Thanks again!

Regards,

Rakhesh

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

RakheshSasidharan , You Are Welcome! I have this website that tells you everything about REAgentC Command line options! here it is:

http://technet.microsoft.com/en-us/library/hh825204.aspx

And also I think that the system restore didn't restore the REAgentC options

And Lastly do you mind showing me your REAgent.xml if it's possible? :)

Good Luck,,,

Eth

"Try not to become a man of success, but rather try to become a man of value." Albert Einstein

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi Eth,

Yes, I too think the System Restore didn't restore the REAgentC options. Or maybe the corruption is in the recovery partition or someplace System Restore didn't touch. 

Here's my REAgent.XML file - 

<?xml version='1.0' encoding='utf-8'?>

<WindowsRE version="2.0">
  <WinreBCD id="{91d1f9bf-5c91-11e3-8c88-8f43aa31e915}"/>
  <WinreLocation path="\Recovery\WindowsRE" id="3609485342" offset="1048576" guid="{00000000-0000-0000-0000-000000000000}"/>
  <ImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <PBRImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
  <PBRCustomImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
  <InstallState state="1"/>
  <OsInstallAvailable state="0"/>
  <CustomImageAvailable state="0"/>
  <IsAutoRepairOn state="1"/>
  <WinREStaged state="0"/>
  <OperationParam path=""/>
  <OsBuildVersion path="9600.16384.amd64fre.winblue_rtm.130821-1623"/>
  <OemTool state="0"/>
  <IsServer state="0"/>
  <DownlevelWinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <ScheduledOperation state="5"/>
</WindowsRE>

Here's the same from my recovery partition - 

<?xml version='1.0' encoding='utf-8'?>

<WindowsRE version="2.0">
  <WinreBCD id="{91d1f9bf-5c91-11e3-8c88-8f43aa31e915}"/>
  <WinreLocation path="\Recovery\WindowsRE" id="3609485342" offset="1048576" guid="{00000000-0000-0000-0000-000000000000}"/>
  <ImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <PBRImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
  <PBRCustomImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
  <InstallState state="1"/>
  <OsInstallAvailable state="0"/>
  <CustomImageAvailable state="0"/>
  <IsAutoRepairOn state="1"/>
  <WinREStaged state="0"/>
  <OperationParam path=""/>
  <OsBuildVersion path="9600.16384.amd64fre.winblue_rtm.130821-1623"/>
  <OemTool state="0"/>
  <IsServer state="0"/>
  <DownlevelWinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
  <ScheduledOperation state="5"/>
</WindowsRE>

Lastly, BCDEdit output just in case - 

bcdedit.exe /enum osloader

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.exe
description             Windows 8.1
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {91d1f9bf-5c91-11e3-8c88-8f43aa31e915}
integrityservices       Enable
recoveryenabled         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {603c0be5-5c91-11e3-8c88-8f43aa31e915}
nx                      OptIn
bootmenupolicy          Standard
hypervisorlaunchtype    Auto

Windows Boot Loader
-------------------
identifier              {91d1f9bf-5c91-11e3-8c88-8f43aa31e915}
device                  ramdisk=[T:]\Recovery\WindowsRE\Winre.wim,{91d1f9c0-5c91-11e3-8c88-8f43aa31e915}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
locale                  en-US
inherit                 {bootloadersettings}
displaymessage          Recovery
osdevice                ramdisk=[T:]\Recovery\WindowsRE\Winre.wim,{91d1f9c0-5c91-11e3-8c88-8f43aa31e915}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

I mounted the Recovery partition as T: drive to get ReAgent.XML off that. That's why BCDEdit shows that drive as T:. 

Diskpart output - 

DISKPART> list partition


  Partition ###  Type              Size     Offset
  -------------  ----------------  -------  -------
  Partition 1    Recovery           350 MB  1024 KB
  Partition 2    Primary            111 GB   351 MB

All of these looked alright to me but maybe you can spot something incorrect? 

Thanks,

Rakhesh


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hi again!

And now REAgentC is working! I didn't do anything except try the command again after send the previous info. And I haven't done anything additional to the laptop either except leave it powered off for two days as I was busy with other things. 

Odd! 

PS T:\Recovery\WindowsRE> reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:

    Windows RE status:         Enabled
    Windows RE location:       \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: 91d1f9bf-5c91-11e3-8c88-8f43aa31e915
    Recovery image location:
    Recovery image index:      0
    Custom image location:
    Custom image index:        0

REAGENTC.EXE: Operation Successful.

Glad that it works, but surprised why it is working! :) Maybe it needed an additional reboot after system restore. Or maybe when I booted into WinRE and got back some setting was cleared. 

Thanks,

Rakhesh

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.