On 3/17/2024 3:21 PM, Boris wrote:
> Paul <nospam@needed.invalid> wrote in news:ut769q$3k7ga$1@dont-email.me:
>
>> On 3/17/2024 12:07 PM, Boris wrote:
>>> =?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?= <winstonmvp@gmail.com> wrote in
>>> news:ut6b0c$3ef2l$1@dont-email.me:
>>>
>>>> Paul wrote on 3/16/24 12:31 PM:
>>>>> On 3/16/2024 2:16 PM, ...w¡ñ§±¤ñ wrote:
>>>>>> Paul wrote on 3/15/24 6:10 PM:
>>>>>>>   Directory of K:\Recovery\WindowsRE
>>>>>>>
>>>>>>> 01/14/2024  01:55 PM   
>>>>>>> <DIR>          . 01/14/2024  01:50
>>>>>>> PM    <DIR>          ..
>>>>>>> 12/07/2019  05:08 AM         3,170,304
>>>>>>> boot.sdi 01/14/2024  01:50
>>>>>>> PM             1,109
>>>>>>> ReAgent.xml 01/14/2024  01:55 PM      
>>>>>>> 517,679,270 winre.wim         <=== can't
>>>>>>> copy, but Testdisk 7.0 can get it
>>>>>>>                 3
>>>>>>> File(s)    520,850,683 bytes
>>>>>>>                 2
>>>>>>> Dir(s)     539,164,672 bytes free
>>>>>>>
>>>>>>> 493 MB (517,679,270 bytes)
>>>>>>>
>>>>>>> The size does not look like a challenge for the 1GB
>>>>>>> partition I gave it. They are likely leaving
>>>>>>> some amount of "safety room".
>>>>>>
>>>>>> Looks like winre.wim was updated.
>>>>>> Free space on that device only matters for the next update.
>>>>>>
>>>>>> I've covered this before...the free space requirement applies to
>>>>>> the installation process requiremenet, not the size of the
>>>>>> existing or updated files.
>>>>>
>>>>> I was referring to the difference between the OPs 829MB
>>>>> versus the 493MB demonstrated by my winre.wim . There
>>>>> is no reason for them to be exactly the same size, but
>>>>> neither do I expect an "elephant" to be hiding in there.
>>>>> There should be *lots* of elbow room for '4441
>>>>> to install, between 829 and 493 (336 space left over).
>>>>> The 829 tells me the OP had already taken heed of
>>>>> some advice to up-size that partition. I don't think 829
>>>>> is a canonical number for a vanilla installation.
>>>>>
>>>>> I would want to check the reagentc status again (in
>>>>> an admin terminal).
>>>>>
>>>>> reagentc /info
>>>>>
>>>>> It's hard to believe the installer doesn't have write
>>>>> permission in there. Or, maybe it is unable to create
>>>>> the temporary area it uses for preparing the winre.wim .
>>>>>
>>>>> Paul
>>>>>
>>>> Hi,Paul.
>>>> Just about every system I've seen reported or even my own have
>>>> different sizes for the WinRE partition sizes, free space before and
>>>> after installing KB5034441(and its safe o/s update).
>>>>
>>>> Was your 493 MB winre.wim with its Jan. 2024 date previously updated
>>>> with KB5034441. Also, comparing a system with an updated winre.wim
>>>> with another. Your WinRE partition, W10Pro(partition #6) is 1025
>>>> MB(your results) The OP's WinRe partition 856 MB(looks like you
>>>> referred to it as 829 MB?) - if your Win10 device was updated with
>>>> KB5034441 and the op's wasn't(it was reported as not being update)
>>>> it would be after(yours) vs. before(comparison).
>>>> =>Yes, the difference between 856 and 493 would be 364 MB, but
>>>> imo, the
>>>> comparison, in this case, is only your 1025 MB WinRE partition vs.
>>>> the op's 856 MB.
>>>>
>>>> It would be helpful, if the op(Boris in this thread) reported the
>>>> results of the WinRE partition size and free space.
>>>> Powershell admin mode
>>>> Get-Volume
>>>>
>>>> Other comments:
>>>> ---------------
>>>> 1. WinRE partition on my Win10 Pro device, updated with KB5034441
>>>> - WinRE partition total 1024 MB, free space 355 MB, winre.wim 661
>>>> MB => This device with the 661 MB winre.wim after updating with
>>>> 5034441,
>>>> without having to shrink C/resize WinRE - the 1024 MB partition was
>>>> created at an earlier time during a clean install replacing an HDD
>>>> with SSD
>>>>
>>>> 2. Win11 Pro, not the same o/s for comparison sake, and on another
>>>> device has:
>>>> WinRE partition total 1024 MB, free space 195 MB, winre.wim 810 MB
>>>> ...but it does indicate that winre.wim and the WinRE partition total
>>>> size, free space is not necessarily common(nor has it ever been)
>>>> across the same or later o/s and other devices(including yours and
>>>> probably many others too).
>>>> - ...I could add another of my Win 10 Pro devices with a different
>>>> WinRE partition(total, free space, and different winre.wim) size
>>>> e.g. my Surface 3 W10Pro 22H2, which updated with 5034441 without a
>>>> necessary shrink/resize but required advanced prep after initially
>>>> failing 5034441 - disabled System Restore points, Disk Cleanup in
>>>> admin mode(selecting everything), disabled WU, BITS, delete Software
>>>> Distribution and let Windows rebuild...but that would only add more
>>>> confirmation that WinRE partition size(and its files, free space)
>>>> varies quite a bit across devices...maybe even validating the MSFT
>>>> 250 MB shrink choice to increase WinRE partition size is a number
>>>> specifically for the installation requirements across hundreds of
>>>> million devices with only a small bit for winre.wim size
>>>> increase(which has been growing periodically for the last 8 yrs.)
>>>>
>>>>
>>>
>>> Below is a copy/paste of Get-Volume. Sorry it's wrapped, so here's a
>>> screenshot that may be easier to read:
>>>
>>> https://postimg.cc/5Q8gcM1L
>>>
>>> Windows PowerShell
>>> Copyright (C) Microsoft Corporation. All rights reserved.
>>>
>>> Try the new cross-platform PowerShell https://aka.ms/pscore6
>>>
>>> PS C:\WINDOWS\system32> Get-Volume
>>>
>>> DriveLetter FriendlyName FileSystemType DriveType HealthStatus OperationalStatus SizeRemaining Size
>>> ----------- ------------ -------------- --------- ------------ ----------------- ------------- ----
>>> D Unknown CD-ROM Healthy Unknown 0 B 0 B
>>> Image NTFS Fixed Healthy OK 620.39 MB 11.94 GB
>>> NTFS Fixed Healthy OK 426.64 MB 856 MB
>>> ESP FAT32 Fixed Healthy OK 462.12 MB 496 MB
>>> C OS NTFS Fixed Healthy OK 791.73 GB 918.12 GB
>>>
>>> PS C:\WINDOWS\system32>
>>>
>>> ------------------------------------
>>>
>>> Also, in C:\Recovery\OEM I found this file titled 'diskpart', dated
>>> March 3, 2016, about five months before I purchased this machine.
>>>
>>> convert gpt
>>> create partition efi size=200
>>> format quick fs=fat32 label="ESP"
>>> assign letter="S"
>>> create partition msr size=16
>>> create partition primary
>>> shrink minimum=12679
>>> format quick fs=ntfs label="OS"
>>> assign letter="W"
>>> create partition primary size=450
>>> id=de94bba4-06d1-4d40-a16a-bfd50179d6ac format quick fs=ntfs
>>> label="WINRETOOLS" assign letter="T"
>>> gpt attributes=0x8000000000000001
>>> create partition primary size=12229
>>> id=de94bba4-06d1-4d40-a16a-bfd50179d6ac format quick fs=ntfs
>>> label="Image" assign letter="R"
>>> gpt attributes=0x8000000000000001
>>> create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
>>> format quick fs=ntfs label="DELLSUPPORT"
>>> assign letter="Q"
>>> gpt attributes=0x8000000000000001
>>> list vol
>>> exit
>>>
>>> ----------------------------
>>>
>>> This directory contained:
>>>
>>> AfterImageApply_BDB0C1E8-6951-46C4-AB7F-C07B29F462FD.cmd, 3/13/2022
>>> bootmenu.xml, 6/12/2015
>>> DellEFI.wim, 3/23/2016
>>> diskpart.txt, 3/23/2016
>>> DK-EXC.exe, 7/15/2015
>>> EnableWinRE.log, 3/23/2016
>>> ResetConfig.xml, 3/13/2022
>>> ResetConfig_F62B90D4-A654-4CFE-B625-213D47A83416.xml, 3/23/2016
>>>
>>> I thought some of the above may be of interest/helpful.
>>>
>>> Thanks.
>>>
>> If you do
>>
>> admin terminal:
>>
>> reagentc /info # assuming it is actually enabled... we'll try some more things
>> reagentc /disable
>> reagentc /enable
>> reagentc /info
>>
>> does the status come back to the original value ?
>>
>> Do any of the steps fail ?
>>
>> Perhaps that might verify the plumbing on it.
>>
>> Paul
>>
>>
>
> Boot Configration Data changed:
>
> Microsoft Windows [Version 10.0.19045.4170]
> (c) Microsoft Corporation. All rights reserved.
>
> 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: 4e779847-a827-11e9-8e98-847beb199e33
> Recovery image location:
> Recovery image index: 0
> Custom image location:
> Custom image index: 0
>
> REAGENTC.EXE: Operation Successful.
>
>
> C:\WINDOWS\system32>reagentc /disable
> REAGENTC.EXE: Operation Successful.
>
>
> C:\WINDOWS\system32>reagentc /enable
> REAGENTC.EXE: Operation Successful.
>
>
> 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: 3fd1cfd0-e492-11ee-9040-2c6e8556f413
> Recovery image location:
> Recovery image index: 0
> Custom image location:
> Custom image index: 0
>
> REAGENTC.EXE: Operation Successful.

Mine seems to do the same thing, when I test it.
Having the identifier change seems to be normal.
It should also be updated in "bcdedit" output.

PS C:\WINDOWS\system32> bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {2e6dc2f3-fa1b-11ed-991f-2cf05dd9f734}
displayorder {current}
{default}
toolsdisplayorder {memdiag}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {5a252332-b305-11ee-9947-e8ea6a0992ff} <===
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {2e6dc2f3-fa1b-11ed-991f-2cf05dd9f734}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
usefirmwarepcisettings No

Windows Boot Loader
-------------------
identifier {default}
device partition=D:
path \WINDOWS\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {964e2ef1-3a60-11ed-81d3-5cf3707d2fda}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=D:
systemroot \WINDOWS
resumeobject {964e2eee-3a60-11ed-81d3-5cf3707d2fda}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
usefirmwarepcisettings No

PS 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\partition6\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 5a252332-b305-11ee-9947-e8ea6a0992ff <===
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

PS C:\WINDOWS\system32> reagentc /disable
REAGENTC.EXE: Operation Successful.

PS C:\WINDOWS\system32> reagentc /enable
REAGENTC.EXE: Operation Successful.

PS 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\partition6\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: 32ae1bf5-e4be-11ee-995f-e8ea6a0992ff <=== changed
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0

REAGENTC.EXE: Operation Successful.

PS C:\WINDOWS\system32> bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {2e6dc2f3-fa1b-11ed-991f-2cf05dd9f734}
displayorder {current}
{default}
toolsdisplayorder {memdiag}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {32ae1bf5-e4be-11ee-995f-e8ea6a0992ff} <=== Was updated with new identifier
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {2e6dc2f3-fa1b-11ed-991f-2cf05dd9f734}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
usefirmwarepcisettings No

Windows Boot Loader
-------------------
identifier {default}
device partition=D:
path \WINDOWS\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {964e2ef1-3a60-11ed-81d3-5cf3707d2fda}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=D:
systemroot \WINDOWS
resumeobject {964e2eee-3a60-11ed-81d3-5cf3707d2fda}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto
usefirmwarepcisettings No
PS C:\WINDOWS\system32>

**************************************************************

I don't know what they're using for slack space calculation, but there's
an "invisible lump" of something not in evidence. The thing seems
to be asking for almost 400MB of slack.

https://superuser.com/questions/1534341/reagentc-unable-to-update-winre-boot-configuration-data

... [ReAgentc] MeetPartitionRequirements

Info Partition details: {Offset: 1048576, Free space: 541589504, Total space: 575664128}
Info WinRE WIM size: 443717121
Info Required free space: 831690241
Warning Not enough free space req = 831690241 avail = 541589504 offset = 1048576

which means, who knows, yours really does need to be bigger :-/

You can check C:\$WinREAgent for evidence of the "waiting" update,
but don't expect the sizes to necessarily match anything. The "update.wim"
could be the cooked item to be copied, but I can't really be
sure of that. My Win11 has an update.wim of 570,403,392 bytes.
Which would fit in a shoe box.

Paul