Was trying to figure out the logistics of WinRe due to a windows update failure.
I first in diskpart assigned drive letter T to Recovery Partition 5
So I then exited diskpart back to cmd shell
I was experimenting with watching the winre.wim move back to
C:\Windows\System32\Recovery\ when I disabled reagentc
Long story short, along the way something foobarred,
T:\Recovery\WindowsRE>reagentc /enable
REAGENTC.EXE: Operation failed: b7
REAGENTC.EXE: An error has occurred.
(I might of had diskpart running on one cmd shell and another cmd shell
running dir cmds at same time, anyhow I foobarred something)
So I try reagentc /info and it says none found.
I looked to the Recovery Partition on drive letter T and found windows had moved all the files that used to be in \Recovery\WindowsRE
to \Recovery\Temporary
--Anyhow it created a Temporary folder to hold the 3 files boot.sdi, ReAgent.xml, winre.wim.
And winre.wim was also not in C:\Windows\System32\Recovery
So I did this, dir /a /s c:\winre.wim
and it found one in,
C:\$WinREAgent\Backup\
So in a file manager I copied it to the
C:\Windows\System32\Recovery\
Then did this,
So tried to set the path back,
T:\Recovery\WindowsRE>reagentc /setreimage /path T:\Recovery\WindowsRE
REAGENTC.EXE: No valid image found in the specified path (obviously since it's been moved into the temporary folder).
T:\Recovery\WindowsRE>reagentc /enable
REAGENTC.EXE: Operation Successful.
--Everything still looks good except all the files are in a sub folder named Temporary and /setreimage /path T:\Recovery\WindowsRE
gets-> REAGENTC.EXE: No valid image found in the specified path.
It's getting late and I'm beat, but I'm guessing I need to edit a new
ReAgent.xml in the C:\Windows\System32\Recovery
I can get into the T:\Recovery\Temporary in a cmd shell only,
--But I can't robocopy or xcopy anything in or out of there.
Robocopy /S /E T:\Recovery C:\My Scans
Robocopy said it copied them but they're not there. I tried attrib etc.
If anyone read this far and knows a direction to head me in would be much appreciated.
I was able to open the ReAgentOld.xml sitting in T:\Recovery
and it looks obliterated with zero guids. I could post up it's contents tomorrow. Short of that I guess I could delete the foobarred recovery partition and create a new one in it's place and try to get it going from scratch.
The C:\$WinREAgent\Backup\ folder has the 3 files boot.sdi, ReAgent.xml, winre.wim. But the ReAgent.xml contents doesn't look promising.
The irony is this Win11 device I just foobarred the recovery partition on was only an experiment so I could learn to fix my wife's device that has a recovery partition Win10 update issue. Experimenting on my Win11 device so I could apply my notes to her Win10 device. Yea whatever.
Hope I didn't typo anything too bad. Logging out for tonight.
I first in diskpart assigned drive letter T to Recovery Partition 5
So I then exited diskpart back to cmd shell
I was experimenting with watching the winre.wim move back to
C:\Windows\System32\Recovery\ when I disabled reagentc
Long story short, along the way something foobarred,
T:\Recovery\WindowsRE>reagentc /enable
REAGENTC.EXE: Operation failed: b7
REAGENTC.EXE: An error has occurred.
(I might of had diskpart running on one cmd shell and another cmd shell
running dir cmds at same time, anyhow I foobarred something)
So I try reagentc /info and it says none found.
I looked to the Recovery Partition on drive letter T and found windows had moved all the files that used to be in \Recovery\WindowsRE
to \Recovery\Temporary
Code:
T:\Recovery\Temporary>dir /a
Volume in drive T has no label.
Volume Serial Number is 44F1-0F2C
Directory of T:\Recovery\Temporary
05/08/2024 05:47 PM <DIR> .
05/08/2024 05:47 PM <DIR> ..
05/07/2022 01:19 AM 3,170,304 boot.sdi
01/13/2024 05:38 PM 703,297,296 Winre.wim
2 File(s) 706,467,600 bytes
2 Dir(s) 82,210,816 bytes free
T:\Recovery\WindowsRE>dir /a
Volume in drive T has no label.
Volume Serial Number is 44F1-0F2C
Directory of T:\Recovery\WindowsRE
05/08/2024 05:35 PM <DIR> .
05/08/2024 05:47 PM <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 82,210,816 bytes free
And winre.wim was also not in C:\Windows\System32\Recovery
So I did this, dir /a /s c:\winre.wim
and it found one in,
C:\$WinREAgent\Backup\
So in a file manager I copied it to the
C:\Windows\System32\Recovery\
Then did this,
Code:
T:\Recovery\WindowsRE>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
So tried to set the path back,
T:\Recovery\WindowsRE>reagentc /setreimage /path T:\Recovery\WindowsRE
REAGENTC.EXE: No valid image found in the specified path (obviously since it's been moved into the temporary folder).
T:\Recovery\WindowsRE>reagentc /enable
REAGENTC.EXE: Operation Successful.
Code:
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\partition3\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 828f9305-b225-11ee-a3db-adda79cfde9f
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
So it's now running on C drive partition.
So looked at foobarred Recovery partition 5,
DISKPART> list part
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 100 MB 1024 KB
Partition 2 Reserved 16 MB 101 MB
Partition 3 Primary 750 GB 117 MB
Partition 4 Primary 202 GB 750 GB
* Partition 5 Recovery 768 MB 953 GB
DISKPART> det part
Partition 5
Type : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Hidden : Yes
Required: Yes
Attrib : 0X8000000000000001
Offset in Bytes: 1023402835968
Volume # Ltr Label Fs Type Size Status Info
------- --- ------ ----- ---------- ------ ------- --------
*Volume 3 T NTFS Partition 768 MB Healthy Hidden
gets-> REAGENTC.EXE: No valid image found in the specified path.
It's getting late and I'm beat, but I'm guessing I need to edit a new
ReAgent.xml in the C:\Windows\System32\Recovery
I can get into the T:\Recovery\Temporary in a cmd shell only,
Code:
T:\Recovery\Temporary>dir /a
Volume in drive T has no label.
Volume Serial Number is 44F1-0F2C
Directory of T:\Recovery\Temporary
05/08/2024 05:47 PM <DIR> .
05/08/2024 05:47 PM <DIR> ..
05/07/2022 01:19 AM 3,170,304 boot.sdi
01/13/2024 05:38 PM 703,297,296 Winre.wim
2 File(s) 706,467,600 bytes
2 Dir(s) 82,210,816 bytes free
Robocopy /S /E T:\Recovery C:\My Scans
Robocopy said it copied them but they're not there. I tried attrib etc.
If anyone read this far and knows a direction to head me in would be much appreciated.
I was able to open the ReAgentOld.xml sitting in T:\Recovery
and it looks obliterated with zero guids. I could post up it's contents tomorrow. Short of that I guess I could delete the foobarred recovery partition and create a new one in it's place and try to get it going from scratch.
The C:\$WinREAgent\Backup\ folder has the 3 files boot.sdi, ReAgent.xml, winre.wim. But the ReAgent.xml contents doesn't look promising.
The irony is this Win11 device I just foobarred the recovery partition on was only an experiment so I could learn to fix my wife's device that has a recovery partition Win10 update issue. Experimenting on my Win11 device so I could apply my notes to her Win10 device. Yea whatever.
Hope I didn't typo anything too bad. Logging out for tonight.
My Computer
System One
-
- OS
- Windows 10 & Windows 11
- Computer type
- Laptop
- Manufacturer/Model
- HP 17" Laptop, Acer Aspire 5