On 2/16/2024 11:36 AM, ...w¡ñ§±¤ñ wrote:
> sticks wrote on 2/15/24 7:19 AM:

> Wtg!  Well done.
>  You're welcome.
>
> You can rerun that earlier mentioned commane to see your current WinRE
> Service Pack build and dates etc.

I had intended to do this and forgot before claiming it was all fixed.
Nice catch. When I checked, it was all the same build (2014) as before.
I had to go back and do the recreating of the partition, and renamed
the .wim file in the recovery directory, re-enabling it, and I think it
finally shows a current ReAgent!

<https://www.dropbox.com/scl/fi/qb1aa61bhgdo5099bvpws/ReAgentNew.jpg?rlkey=jnhiz15sutdqm2cwsnv61k1qr&dl=0>

> Sometimes the wipe path is the easier route, especially in this case
> when the WinRE partition build was showing and old o/s(unsupported long
> ago) build number.
>  There were other ways to replace that Win8 era WinRE...as I said messy
>  - one of which pulls/extracts the WinRE.wim file(using the DISM
> command) from an external(or mounted ISO) same o/s(as installed) media's
> install.wim file(not install.esd used in Media Creation tool media),
> copy  the winre.wim to the C:\..\Recovery folder allowing it be used
> when reaagentc is later enabled and moved to the newly created WinRE
> partition.

I think what I did wrong during the reinstall was that I just refreshed
the recovery partition instead of formatting it?
Anyway, giving it back to the MIL as a spare today. Kind of a waste
really. With a clean install now, instead of a Windows 8 upgrade
install of Windows 10, it probably works better than it ever did. Since
I already bought her the new system, this will just lay around and never
get used. But, it was certainly interesting doing all this stuff.

Thanks!

--
Stand With Israel!
NOTE: If you use Google Groups I don't see you,
unless you're whitelisted and that's doubtful.

sticks wrote on 2/17/24 9:34 AM:
> On 2/16/2024 11:36 AM, ...w¡ñ§±¤ñ wrote:
>> sticks wrote on 2/15/24 7:19 AM:
>
>> Wtg!  Well done.
>>   You're welcome.
>>
>> You can rerun that earlier mentioned commane to see your current WinRE
>> Service Pack build and dates etc.
>
> I had intended to do this and forgot before claiming it was all fixed.
> Nice catch.  When I checked, it was all the same build (2014) as before.
>  I had to go back and do the recreating of the partition, and renamed
> the .wim file in the recovery directory, re-enabling it, and I think it
> finally shows a current ReAgent!
>
> <https://www.dropbox.com/scl/fi/qb1aa61bhgdo5099bvpws/ReAgentNew.jpg?rlkey=jnhiz15sutdqm2cwsnv61k1qr&dl=0>
>

That looks right for Win10. Other Win10 devices Service Pack Build,
date created can look different, some of which being dependent upon the
version of or the point in time the Win10 media was created or downloaded.
- e.g. Win10 22H2 was released in fall or 2022 but the Media Creation
Tool and ISO have been updated with some new system files. Win11 WinRE
System Build likewise can show variation in the Service Pack Build(e.g.
3000 vs 3007 or higher)

>
>> Sometimes the wipe path is the easier route, especially in this case
>> when the WinRE partition build was showing and old o/s(unsupported long
>> ago) build number.
>>   There were other ways to replace that Win8 era WinRE...as I said messy
>>   - one of which pulls/extracts the WinRE.wim file(using the DISM
>> command) from an external(or mounted ISO) same o/s(as installed)
>> media's install.wim file(not install.esd used in Media Creation tool
>> media), copy  the winre.wim to the C:\..\Recovery folder allowing it be
>> used when reaagentc is later enabled and moved to the newly created
>> WinRE partition.
>
>
> I think what I did wrong during the reinstall was that I just refreshed
> the recovery partition instead of formatting it?

Yes, wiping the disk, then following all the steps to create all 4 GPT
partitions is the preferred approach.
When clean installing Windows by booting the media I use the Advanced
options mode allowing me command line control and access to Diskpart for
running a Diskpart script(*.txt file). The script(while in Diskpart)
isn't necessary since all commands can be entered/typed manually, but
using the script ensures no errors(typing), streamlines the process and
it's faster.
- Here's an example script of all the steps for a device with a single
256 GB SSD as Disk 0.
**************
rem DISKPART script
rem Disk 0 with a single 256 GB SSD
rem Creates GPT(EFI MSR Windows with 2 GB Recovery)
rem Disk 0 OpSy Windows10 Pro 22H2
rem Select Disk, wipe it empty, convert to GPT
select disk 0
clean
convert gpt
create partition efi size=100
format quick fs=fat32 label="System"
create partition msr size=16
create partition primary
shrink minimum=2048
format quick fs=ntfs label="Windows10Pro"
assign letter="W"
create partition primary size=2048
format quick fs=ntfs label="WinRE"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
rem Exit Diskpart
rem written by winston
exit
******************

Once done(diskpart exited), all that remains is to continue clean
installing Win10 22H2 to the Windows partition.

> Thanks!
>
You're welcome

--
....w¡ñ§±¤ñ

On 2/17/2024 2:11 PM, ...w¡ñ§±¤ñ wrote:
> sticks wrote on 2/17/24 9:34 AM:
>> On 2/16/2024 11:36 AM, ...w¡ñ§±¤ñ wrote:
>>> sticks wrote on 2/15/24 7:19 AM:
>>
>>> Wtg!  Well done.
>>>   You're welcome.
>>>
>>> You can rerun that earlier mentioned commane to see your current
>>> WinRE Service Pack build and dates etc.
>>
>> I had intended to do this and forgot before claiming it was all fixed.
>> Nice catch.  When I checked, it was all the same build (2014) as
>> before.   I had to go back and do the recreating of the partition, and
>> renamed the .wim file in the recovery directory, re-enabling it, and I
>> think it finally shows a current ReAgent!
>>
>> <https://www.dropbox.com/scl/fi/qb1aa61bhgdo5099bvpws/ReAgentNew.jpg?rlkey=jnhiz15sutdqm2cwsnv61k1qr&dl=0>
>
>  That looks right for Win10.  Other Win10 devices Service Pack Build,
> date created can look different, some of which being dependent upon the
> version of or the point in time the Win10 media was created or downloaded.
>  - e.g. Win10 22H2 was released in fall or 2022 but the Media Creation
> Tool and ISO have been updated with some new system files. Win11 WinRE
> System Build likewise can show variation in the Service Pack Build(e.g.
> 3000 vs 3007 or higher)
>
>>
>>> Sometimes the wipe path is the easier route, especially in this case
>>> when the WinRE partition build was showing and old o/s(unsupported
>>> long ago) build number.
>>>   There were other ways to replace that Win8 era WinRE...as I said messy
>>>   - one of which pulls/extracts the WinRE.wim file(using the DISM
>>> command) from an external(or mounted ISO) same o/s(as installed)
>>> media's install.wim file(not install.esd used in Media Creation tool
>>> media), copy  the winre.wim to the C:\..\Recovery folder allowing it
>>> be used when reaagentc is later enabled and moved to the newly
>>> created WinRE partition.
>>
>>
>> I think what I did wrong during the reinstall was that I just
>> refreshed the recovery partition instead of formatting it?
>
> Yes, wiping the disk, then following all the steps to create all 4 GPT
> partitions is the preferred approach.
> When clean installing Windows by booting the media I use the Advanced
> options mode allowing me command line control and access to Diskpart for
> running a Diskpart script(*.txt file). The script(while in Diskpart)
> isn't necessary since all commands can be entered/typed manually, but
> using the script ensures no errors(typing), streamlines the process and
> it's faster.
> - Here's an example script of all the steps for a device with a single
> 256 GB SSD as Disk 0.
> **************
> rem DISKPART script
> rem Disk 0 with a single 256 GB SSD
> rem Creates GPT(EFI MSR Windows with 2 GB Recovery)
> rem Disk 0 OpSy Windows10 Pro 22H2
> rem Select Disk, wipe it empty, convert to GPT
> select disk 0
> clean
> convert gpt
> create partition efi size=100
> format quick fs=fat32 label="System"
> create partition msr size=16
> create partition primary
> shrink minimum=2048
> format quick fs=ntfs label="Windows10Pro"
> assign letter="W"
> create partition primary size=2048
> format quick fs=ntfs label="WinRE"
> set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
> rem Exit Diskpart
> rem written by winston
> exit
> ******************
>
> Once done(diskpart exited), all that remains is to continue clean
> installing Win10 22H2 to the Windows partition.
>
>
>> Thanks!
>>
>  You're welcome
>

Nice. I have archived this locally for the future just in case.

Wife's laptop could really use this I think. The one I just finished
runs so much better than it ever did, I suggested doing hers since she
get occasional lockups. She passed on the offer, and I shrugged as I
walked away.

--
Stand With Israel!
NOTE: If you use Google Groups I don't see you,
unless you're whitelisted and that's doubtful.