Running Windows 10 Home, 22H2, build 19045.4170
KB5034441 keeps failing to install on my Windows 10 Home, 22H2, build 19045.4170
https://support.microsoft.com/en-us/topic/kb5034441-windows-recovery- environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024- 62c04204-aaa5-4fee-a02a-2fdea17075a8
This update "addresses a security vulnerability that could allow
attackers to bypass BitLocker encryption by using WinRE."
I wondered why my Windows 10 Home was getting this update downloaded to
my machine because what I've read says that BitLocker doesn't come with Windows 10 Home. I thought that might explain the install failure.
Based on this, I decided that this update didn't apply to my OS and used Windows Update Show/Hide to hide the update.
Afterwards, I decided to search for the term "BitLocker". Everything
found 150 objects. Huh? But I'm running Windows 10 Home. What's up?
OK, let's say that BitLocker is on my Windows 10 Home machine.
Requirements for this update state, "This update requires 250 MB of free space in the recovery partition to install successfully. If the recovery partition does not have sufficient free space, this update will fail."
reagentc /info tells me that Windows RE status is Enabled
Disk Management shows I have two recovery partitions, 856 MB and 11.94
GB. Diskpart shows the same.
https://postimg.cc/gallery/VSSKNkY
Perhaps the update is looking to install itself on the 856 MB partition, where there's not enough room?
I'm not trying to get this update installed. I suspect I'd have to
resize the 856 MB partition. I'm just wondering why Everyting shows 150 BitLocker objects. (Maybe it's there in case the user upgraded to
Windows 10 Pro?}
diskpart
k:Microsoft Windows [Version 10.0.22631.3296]
cmd
dir /ahVolume in drive K has no label.
cd Recovery
Running Windows 10 Home, 22H2, build 19045.4170
KB5034441 keeps failing to install on my Windows 10 Home, 22H2, build 19045.4170
https://support.microsoft.com/en-us/topic/kb5034441-windows-recovery- environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024- 62c04204-aaa5-4fee-a02a-2fdea17075a8
This update "addresses a security vulnerability that could allow
attackers to bypass BitLocker encryption by using WinRE."
I wondered why my Windows 10 Home was getting this update downloaded to
my machine because what I've read says that BitLocker doesn't come with Windows 10 Home. I thought that might explain the install failure.
Based on this, I decided that this update didn't apply to my OS and used Windows Update Show/Hide to hide the update.
Afterwards, I decided to search for the term "BitLocker". Everything
found 150 objects. Huh? But I'm running Windows 10 Home. What's up?
OK, let's say that BitLocker is on my Windows 10 Home machine.
Requirements for this update state, "This update requires 250 MB of free space in the recovery partition to install successfully. If the recovery partition does not have sufficient free space, this update will fail."
reagentc /info tells me that Windows RE status is Enabled
Disk Management shows I have two recovery partitions, 856 MB and 11.94
GB. Diskpart shows the same.
https://postimg.cc/gallery/VSSKNkY
Perhaps the update is looking to install itself on the 856 MB partition, where there's not enough room?
I'm not trying to get this update installed. I suspect I'd have to
resize the 856 MB partition. I'm just wondering why Everyting shows 150 BitLocker objects. (Maybe it's there in case the user upgraded to
Windows 10 Pro?}
On 15/03/2024 22:12, Boris wrote:
Running Windows 10 Home, 22H2, build 19045.4170
KB5034441 keeps failing to install on my Windows 10 Home, 22H2, build
19045.4170
https://support.microsoft.com/en-us/topic/kb5034441-windows-recovery-
environment-update-for-windows-10-version-21h2-and-22h2-january-9-2024-
62c04204-aaa5-4fee-a02a-2fdea17075a8
This update "addresses a security vulnerability that could allow
attackers to bypass BitLocker encryption by using WinRE."
I wondered why my Windows 10 Home was getting this update downloaded to
my machine because what I've read says that BitLocker doesn't come with
Windows 10 Home. I thought that might explain the install failure.
Based on this, I decided that this update didn't apply to my OS and used
Windows Update Show/Hide to hide the update.
Afterwards, I decided to search for the term "BitLocker". Everything
found 150 objects. Huh? But I'm running Windows 10 Home. What's up?
OK, let's say that BitLocker is on my Windows 10 Home machine.
Requirements for this update state, "This update requires 250 MB of free
space in the recovery partition to install successfully. If the recovery
partition does not have sufficient free space, this update will fail."
reagentc /info tells me that Windows RE status is Enabled
Disk Management shows I have two recovery partitions, 856 MB and 11.94
GB. Diskpart shows the same.
https://postimg.cc/gallery/VSSKNkY
Perhaps the update is looking to install itself on the 856 MB partition,
where there's not enough room?
I'm not trying to get this update installed. I suspect I'd have to
resize the 856 MB partition. I'm just wondering why Everyting shows 150
BitLocker objects. (Maybe it's there in case the user upgraded to
Windows 10 Pro?}
Was Windows 10 upgraded from an older version of Windows?
I have an old Toshiba laptop that came with Win 8 Home and I remember
needing to turn BitLocker off.
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.
Paul wrote on 3/16/24 12:31 PM:
On 3/16/2024 2:16 PM, ...w¡ñ§±¤ñ wrote:Hi,Paul.
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
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.)
=?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:Hi,Paul.
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
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.
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:Hi,Paul.
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
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
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 inIf you do
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:Hi,Paul.
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
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.
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.
Boris wrote on 3/17/24 9:07 AM:
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
It's common for OEM's to include a *.txt file with the as-shipped
factory partitioning commands. During a factory reset, the *.txt file extension is the requirement for diskpart to run the file as a script.
The above file indicates the OEM created 6 partitions
System 200MB
MSR 16 MB
Windows (GB in size less the following 3 partitions)
Recovery(Win RE Tools 450 MB)- the active WinRE partition
Image (11.9 GB) - the factory image of Windows and all pre-installed
software and apps
Dell Support(~1 GB) - Dell utilities probably used when running an app
Dell included in Windows to do or support the returning/resetting the
device to the as-shipped factory condition.
Boris wrote on 3/19/24 8:51 AM:It was difficult for me to line up the partitons as shown by the OEM partitioning file, Disk Management, and Diskpart. Partitions numbers
=?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?= <winstonmvp@gmail.com> wrote inYou're welcome.
news:ut9uop$9vgm$1@dont-email.me:
Boris wrote on 3/17/24 9:07 AM:
It's common for OEM's to include a *.txt file with the as-shipped
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
factory partitioning commands. During a factory reset, the *.txt
file extension is the requirement for diskpart to run the file as a
script.
The above file indicates the OEM created 6 partitions
System 200MB
MSR 16 MB
Windows (GB in size less the following 3 partitions)
Recovery(Win RE Tools 450 MB)- the active WinRE partition
Image (11.9 GB) - the factory image of Windows and all pre-installed
software and apps
Dell Support(~1 GB) - Dell utilities probably used when running an
app Dell included in Windows to do or support the
returning/resetting the device to the as-shipped factory condition.
Thanks.
Fyi...if you compare the OEM factor partitioning with the
partitioning
you reported.
- System(ESP aka EFI) partition is different 200 MB vs. 496 MB(500
MB
in Disk Management
- WinRE partition(Win RE Tools) is different 450 MB vs. 856 MB
The OEM partitioning files shows 6 partitions created(#6 as
DellSupport) yet your pics only indicate 5 partitions(counting the
hidden 16 MB MSR), which probably indicates that the DELLSUPPORT
partition shown in the OEM partitioning file is also hidden or no
longer present.
You might be able to see the presence of the supposed DELLSUPPORT via
a Powershell or Command.com admin window(session) using Diskpart
In Diskpart
List disk
Sel disk # (the #-number that list disk shows for the o/s (probably 0)
List part
You should at least see partition 1 to 4 -vSystem, Reserved(the MSR), Primary(Windows), Recovery, #5 Image...and if present, #6 DELLSUPPORT
=?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?= <winstonmvp@gmail.com> wrote in news:utcq36$10m09$1@dont-email.me:
Boris wrote on 3/19/24 8:51 AM:It was difficult for me to line up the partitons as shown by the OEM partitioning file, Disk Management, and Diskpart. Partitions numbers
=?UTF-8?B?Li4ud8Khw7HCp8KxwqTDsSA=?= <winstonmvp@gmail.com> wrote inYou're welcome.
news:ut9uop$9vgm$1@dont-email.me:
Boris wrote on 3/17/24 9:07 AM:
It's common for OEM's to include a *.txt file with the as-shipped
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
factory partitioning commands. During a factory reset, the *.txt
file extension is the requirement for diskpart to run the file as a
script.
The above file indicates the OEM created 6 partitions
System 200MB
MSR 16 MB
Windows (GB in size less the following 3 partitions)
Recovery(Win RE Tools 450 MB)- the active WinRE partition
Image (11.9 GB) - the factory image of Windows and all pre-installed
software and apps
Dell Support(~1 GB) - Dell utilities probably used when running an
app Dell included in Windows to do or support the
returning/resetting the device to the as-shipped factory condition.
Thanks.
Fyi...if you compare the OEM factor partitioning with the
partitioning
you reported.
- System(ESP aka EFI) partition is different 200 MB vs. 496 MB(500
MB
in Disk Management
- WinRE partition(Win RE Tools) is different 450 MB vs. 856 MB
The OEM partitioning files shows 6 partitions created(#6 as
DellSupport) yet your pics only indicate 5 partitions(counting the
hidden 16 MB MSR), which probably indicates that the DELLSUPPORT
partition shown in the OEM partitioning file is also hidden or no
longer present.
and sizes were different. I thought it was odd that Disk Management
showed Free Space 100% for all but the boot disk, OS (C:)
You might be able to see the presence of the supposed DELLSUPPORT via
a Powershell or Command.com admin window(session) using Diskpart
In Diskpart
List disk
Sel disk # (the #-number that list disk shows for the o/s (probably 0)
List part
You should at least see partition 1 to 4 -vSystem, Reserved(the MSR),
Primary(Windows), Recovery, #5 Image...and if present, #6 DELLSUPPORT
DISKPART> List disk
Disk ### Status Size Free Dyn Gpt
-------- ------------- ------- ------- --- ---
Disk 0 Online 931 GB 0 B *
DISKPART> Sel disk 0
Disk 0 is now the selected disk.
DISKPART> List part
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 System 500 MB 1024 KB
Partition 2 Reserved 128 MB 501 MB
Partition 3 Primary 918 GB 629 MB
Partition 4 Recovery 856 MB 918 GB
Partition 5 Recovery 11 GB 919 GB
DISKPART>
It does appear that the DELLSUPPORT partition #6 is either missing or
hidden.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 04:34:02 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,335,881 |