Others' (https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_january_9th_2024/kh32u6f/)That's interesting. My win10 has the same issue. I read the directions on how to fix and the first step is to shrink the OS by 250M so the recovery can be larger.
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with
"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in
64-bit W10 Pro. right now. I already rebooted once from other today's updates:
1. https://support.microsoft.com/en-us/topic/january-9-2024-kb5034275-cumulative-update-for-net-framework-3-5-4-8-and-4-8-1-for-windows-10-version-22h2-6c9a603c-f0a1-4b32-b7fa-a1c6337523f1
2. https://support.microsoft.com/en-us/topic/january-9-2024-kb5034122-os-builds-19044-3930-and-19045-3930-7656c6a4-0b06-4424-86a9-d0719f4ac252
I read 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
's known issue about small WinRE partition with a https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
link.
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
On 1/9/2024 1:47 PM, Ant wrote:Sometime later I'll probably image the whole system and try those commands.
Others'That's interesting. My win10 has the same issue. I read the directions on how to fix and the first step is to shrink the OS by 250M so the recovery can be larger.
(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_january_9th_2024/kh32u6f/)
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with
"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in
64-bit W10 Pro. right now. I already rebooted once from other today's updates:
1.
https://support.microsoft.com/en-us/topic/january-9-2024-kb5034275-cumulative-update-for-net-framework-3-5-4-8-and-4-8-1-for-windows-10-version-22h2-6c9a603c-f0a1-4b32-b7fa-a1c6337523f1
2. https://support.microsoft.com/en-us/topic/january-9-2024-kb5034122-os-builds-19044-3930-and-19045-3930-7656c6a4-0b06-4424-86a9-d0719f4ac252
I read
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
's known issue about small WinRE partition with a
https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
link.
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Cute idea but rather than all that command line stuff I just opened disk manager and tried to shrink it there... It won't let me, it says that it's not possible to shrink.
Normally with a spinning disk this meant that data was stored on those last few sectors it needs to shrink.
One would now just run some defrag program to pull the data away from the end of the disk and all is fine.
But I have an SSD and I have a feeling this tosses a wrinkle in the works.
So now I have no idea what to do. I'm somewhat hesitant to do those commands to shrink and reformat the new recovery. Looks simple but I'm a not adventurous.
On 1/9/2024 4:42 PM, Big Al wrote:
On 1/9/2024 1:47 PM, Ant wrote:
Others'That's interesting. My win10 has the same issue. I read the directions on how to fix and the first step is to shrink the OS by 250M so the recovery can be larger.
(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_january_9th_2024/kh32u6f/)
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with
"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in
64-bit W10 Pro. right now. I already rebooted once from other today's updates:
1.
https://support.microsoft.com/en-us/topic/january-9-2024-kb5034275-cumulative-update-for-net-framework-3-5-4-8-and-4-8-1-for-windows-10-version-22h2-6c9a603c-f0a1-4b32-b7fa-a1c6337523f1
2. https://support.microsoft.com/en-us/topic/january-9-2024-kb5034122-os-builds-19044-3930-and-19045-3930-7656c6a4-0b06-4424-86a9-d0719f4ac252
I read
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
's known issue about small WinRE partition with a
https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
link.
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Cute idea but rather than all that command line stuff I just opened disk manager and tried to shrink it there... It won't let me, it says that it's not possible to shrink.
Normally with a spinning disk this meant that data was stored on those last few sectors it needs to shrink.
One would now just run some defrag program to pull the data away from the end of the disk and all is fine.
But I have an SSD and I have a feeling this tosses a wrinkle in the works.
So now I have no idea what to do. I'm somewhat hesitant to do those commands to shrink and reformat the new recovery. Looks simple but I'm a not adventurous.Sometime later I'll probably image the whole system and try those commands.
On 1/9/2024 4:42 PM, Big Al wrote:
On 1/9/2024 1:47 PM, Ant wrote:
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
On 1/9/2024 4:45 PM, Big Al wrote:
On 1/9/2024 4:42 PM, Big Al wrote:
On 1/9/2024 1:47 PM, Ant wrote:
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Then Al finds this recipe, and the fools use shorthands for the commands. DONT DO THAT.
The users have enough trouble having to do this bloody shit by hand,
why make it twice as hard by crypt-o-fying the command sequence ?
Remember, the average inconvenienced customer, is doing this for the first time.
Not the fiftieth time.
https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
reagentc /info # shows recovery agent is enabled, and is using Partition 4
# The article should show what that looks like. A picture would help.
[Picture]
https://i.postimg.cc/sgXwB389/diskpart-disk-summary.gif
diskpart # Administrator Command Prompt, or Admin Powershell then type "cmd.exe" as a command
list disk
select disk 0
list partition
select partition 3 # will shrink C: now
shrink desired=250 minimum=250 # runtime 1 second
select partition 4
delete partition override # "delete partition" is the command we seek to cowboy at this point
# This solves the inability to change the origin of a partition.
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac # The ID is a partition type, our Recovery.
gpt attributes =0x8000000000000001 # <=== Protected status of partition. Partitions
# can be "marked" as "being special" [Attribute]
format quick fs=ntfs label="Windows RE tools" # Partition 4 is NTFS, and now it has no content. Empty file system.
# Partition is likely hidden by its ID value.
exit
I'm not sure the rest of the procedure is exactly valid.
I'm having trouble believing you can reagentc /enable
when the partition is empty. reagentc /info
will tell you how you
are doing.
The above is to demonstrate what it looks like, without shorthands being used.
I haven't tested this sequence. I'm getting tired.
Paul
On 1/9/2024 8:48 PM, Paul wrote:Your partition looks like it's 646M and mine is 641M, wonder why it's so small or why your update worked.
On 1/9/2024 4:45 PM, Big Al wrote:
On 1/9/2024 4:42 PM, Big Al wrote:
On 1/9/2024 1:47 PM, Ant wrote:
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Then Al finds this recipe, and the fools use shorthands for the commands. DONT DO THAT.
The users have enough trouble having to do this bloody shit by hand,
why make it twice as hard by crypt-o-fying the command sequence ?
Remember, the average inconvenienced customer, is doing this for the first time.
Not the fiftieth time.
https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
reagentc /info # shows recovery agent is enabled, and is using Partition 4
# The article should show what that looks like. A picture would help.
[Picture]
https://i.postimg.cc/sgXwB389/diskpart-disk-summary.gif
diskpart # Administrator Command Prompt, or Admin Powershell then type "cmd.exe" as a command
list disk
select disk 0
list partition
select partition 3 # will shrink C: now
shrink desired=250 minimum=250 # runtime 1 second
select partition 4
delete partition override # "delete partition" is the command we seek to cowboy at this point
# This solves the inability to change the origin of a partition.
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac # The ID is a partition type, our Recovery.
gpt attributes =0x8000000000000001 # <=== Protected status of partition. Partitions
# can be "marked" as "being special" [Attribute]
format quick fs=ntfs label="Windows RE tools" # Partition 4 is NTFS, and now it has no content. Empty file system.
# Partition is likely hidden by its ID value.
exit
I'm not sure the rest of the procedure is exactly valid.
I'm having trouble believing you can reagentc /enable
when the partition is empty. reagentc /info
will tell you how you
are doing.
The above is to demonstrate what it looks like, without shorthands being used.
I haven't tested this sequence. I'm getting tired.
Paul
My Patch Tuesday came in a couple hours ago.
I guess mine succeeded. But why are the dates
on the files so old. My guess is, I didn't get
new contents in my Partition 4.
[Picture]
https://i.postimg.cc/prMPTGLz/January2024-Patch-Tuesday.gif
Paul
Your partition looks like it's 646M and mine is 641M, wonder why it's so small or why your update worked.all?
Too many questions.
bottom line? do you think these instructions are going to work? It will leave an empty partition of course. I use Acronis, I could replace the files after formatting. I could also dd the files out using Linux. Or do they need to be replaced at
Paul <nospam@needed.invalid> wrote:
On 1/9/2024 4:45 PM, Big Al wrote:
On 1/9/2024 4:42 PM, Big Al wrote:
On 1/9/2024 1:47 PM, Ant wrote:
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Then Al finds this recipe, and the fools use shorthands for the commands. DONT DO THAT.
Seconded. Do not, repeat Do Not, repeat DO NOT try to shortcut
this process. There be dragons.
The users have enough trouble having to do this bloody shit by hand,
why make it twice as hard by crypt-o-fying the command sequence ?
Remember, the average inconvenienced customer, is doing this for the first time.
Not the fiftieth time.
I suspect that MS has a FixIt tool in the works. Since this is
night 1 of Patch Tuesday, this is probably the best we'll see for
a while.
[snip KB5028997 extract]
I'm not sure the rest of the procedure is exactly valid.
I'm having trouble believing you can reagentc /enable
If I've figured this correctly, the /enable parameter reloads the
stock WinRE environment, ready for patching via KB5034441.
The above is to demonstrate what it looks like, without shorthands being used.
And I repeat: Do not, repeat Do Not, repeat DO NOT try to
shortcut this process.
I haven't tested this sequence. I'm getting tired.
I did this earlier tonight (Life, what's that?). WinRE
partition: Old size 697 MB, new size 947 MB. After a reboot for
the changed partition size (old precautions), KB5034441 installs
without complaint.
Hope this helps.
Others' >(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_ >january_9th_2024/kh32u6f/) and my updated 64-bit W10 Pro. PC, I'm
getting "Status: Download error - 0x80070643" with "2024-01 Security
Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)"
in 64-bit W10 Pro. right now. I already rebooted once from other
today's updates:
Paul wrote on 1/10/24 2:44 AM:
Now, I can try the recipe and see what happens.
OK, recipe works. REcovery Partition (4) now 759MB.
p.s.
KB5034957: Updating the WinRE partition on deployed devices to address security vulnerabilities in CVE-2024-20666
<https://support.microsoft.com/en-us/topic/kb5034957-updating-the-winre-partition-on-deployed-devices-to-address-security-vulnerabilities-in-cve-2024-20666-0190331b-1ca3-42d8-8a55-7fc406910c10>
In message <jOycnT_9xr1ACQD4nZ2dnZfqn_SdnZ2d@earthlink.com>, Ant <ant@zimage.comANT> writesrebooted once from other today's updates:
Others'
(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_
january_9th_2024/kh32u6f/) and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with "2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in 64-bit W10 Pro. right now. I already
On my 32-bit Windows 10 machine, the patch seems to have downloaded OK, but fails to install, seemingly being stuck at 0%. After a while, it reports the failure and says that it will try again later. If I manually click the Retry button that it givesme to get it to try again immediately, the same thing happens.
I think I'll just wait for Microsoft to fix things rather than try anything fancy.
On 1/10/24 06:44 AM, ...w¡ñ§±¤ñ wrote:Okay, my VM win 10 had a small 511M recovery and it failed the update. Great. So I did the commands in the first link, the ones you have to hand type.
Paul wrote on 1/10/24 2:44 AM:So now I'm totally confused.
Now, I can try the recipe and see what happens.
OK, recipe works. REcovery Partition (4) now 759MB.
p.s.
KB5034957: Updating the WinRE partition on deployed devices to address security vulnerabilities in CVE-2024-20666
<https://support.microsoft.com/en-us/topic/kb5034957-updating-the-winre-partition-on-deployed-devices-to-address-security-vulnerabilities-in-cve-2024-20666-0190331b-1ca3-42d8-8a55-7fc406910c10>
I'm leaning towards John Hall's idea, wait for a while and see MS fixes this on their own.
So you're telling me that the above link that tells me to download the Safe OS Dynamic Update, and run a .ps1 power
shell script will take care of this all for me?  As well as what commands were suggested earlier (or maybe better than
those commands). ?
Paul wrote on 1/10/24 6:44 AM:rebooted once from other today's updates:
On 1/10/2024 5:54 AM, John Hall wrote:
In message <jOycnT_9xr1ACQD4nZ2dnZfqn_SdnZ2d@earthlink.com>, Ant <ant@zimage.comANT> writes
Others'
(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_ >>> january_9th_2024/kh32u6f/) and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with "2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in 64-bit W10 Pro. right now. I already
gives me to get it to try again immediately, the same thing happens.
On my 32-bit Windows 10 machine, the patch seems to have downloaded OK, but fails to install, seemingly being stuck at 0%. After a while, it reports the failure and says that it will try again later. If I manually click the Retry button that it
I think I'll just wait for Microsoft to fix things rather than try anything fancy.
Winstons link shows there is the potential for Bitlocker involvement.
So yes, anything fancy might not be a good idea, especially the
more protected the device is. (Surface, versus a home-built desktop)
Hell, it could have third-party protection for all we know.
Even if a person were to reinstall, the partition still
might not be big enough. "Bad schemes are bad"
One of the reasons some of the audience compromise their machines,
is in the name of maintenance :-) My setup is almost maintainable.
The recipe did not cause me grief. But my setup would not pass HIPPA.
Some people have no choice but to have "complex wrecks" for computers.
Paul
The manual method provided in MSFT's KB/Learn article is, well, just
plain nasty for the consumer(in some cases even the tech savvy consumer).
On my Win10 Pro 22H2 device the Jan. updates installed without issue and possibly(likely) WinRE had more than sufficient free space. My WinRE partition is 1 GB. Before the update is was using just shy of 630 MB of
the 1 GB total, after the update the Win RE is using 830 MB.
Note: Thus I did not have the need or opportunity to test the link I provided.
I mentioned my approach to Windows RE partition creation in the past when performing a clean install. Use the Windows provided installer's Advanced options to create the 4 GPT required partitions and when doing so create
the WinRE partition as 1 GB using a Disk Part script or manually using
the command line UI - a script is much easier<g>.
Likewise, on my Win11 Pro 23H2 device the Jan. update installed without issue(took about 4 minutes). The Win11 23H2 device was also previously
clean installed as Win10 Pro and upgraded to Win11 - the same process was used during that Win10 Pro clean install which used a DiskPart script to create the 4 GPT partitions with the WinRE as a 1GB partition.
If folks are going to reinstall, creating the WinRE as a 1 GB(or maybe
even 2 GB, the way things are growing with WinRE now included in
cumulative updates) might be a good idea or even the recommended norm.
...w¡ñ§±¤ñ <winstonmvp@gmail.com> wrote:rebooted once from other today's updates:
Paul wrote on 1/10/24 6:44 AM:
On 1/10/2024 5:54 AM, John Hall wrote:
In message <jOycnT_9xr1ACQD4nZ2dnZfqn_SdnZ2d@earthlink.com>, Ant <ant@zimage.comANT> writes
Others'
(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_ >>>>> january_9th_2024/kh32u6f/) and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with "2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in 64-bit W10 Pro. right now. I already
gives me to get it to try again immediately, the same thing happens.
On my 32-bit Windows 10 machine, the patch seems to have downloaded OK, but fails to install, seemingly being stuck at 0%. After a while, it reports the failure and says that it will try again later. If I manually click the Retry button that it
I think I'll just wait for Microsoft to fix things rather than try anything fancy.
Winstons link shows there is the potential for Bitlocker involvement.
So yes, anything fancy might not be a good idea, especially the
more protected the device is. (Surface, versus a home-built desktop)
Hell, it could have third-party protection for all we know.
Even if a person were to reinstall, the partition still
might not be big enough. "Bad schemes are bad"
One of the reasons some of the audience compromise their machines,
is in the name of maintenance :-) My setup is almost maintainable.
The recipe did not cause me grief. But my setup would not pass HIPPA.
Some people have no choice but to have "complex wrecks" for computers.
Paul
The manual method provided in MSFT's KB/Learn article is, well, just
plain nasty for the consumer(in some cases even the tech savvy consumer).
On my Win10 Pro 22H2 device the Jan. updates installed without issue and
possibly(likely) WinRE had more than sufficient free space. My WinRE
partition is 1 GB. Before the update is was using just shy of 630 MB of
the 1 GB total, after the update the Win RE is using 830 MB.
Note: Thus I did not have the need or opportunity to test the link I
provided.
I mentioned my approach to Windows RE partition creation in the past when
performing a clean install. Use the Windows provided installer's Advanced
options to create the 4 GPT required partitions and when doing so create
the WinRE partition as 1 GB using a Disk Part script or manually using
the command line UI - a script is much easier<g>.
Likewise, on my Win11 Pro 23H2 device the Jan. update installed without
issue(took about 4 minutes). The Win11 23H2 device was also previously
clean installed as Win10 Pro and upgraded to Win11 - the same process was
used during that Win10 Pro clean install which used a DiskPart script to
create the 4 GPT partitions with the WinRE as a 1GB partition.
If folks are going to reinstall, creating the WinRE as a 1 GB(or maybe
even 2 GB, the way things are growing with WinRE now included in
cumulative updates) might be a good idea or even the recommended norm.
Right, but how many people will do this? 1%? Most are using the defaults. :/
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall <john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings > Windows Update now tells me that I'm up to date. I wonder whether Christmas and New Year meant that this update received less testing than usual before it was released.
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall <john_nospam@jhall.co.uk> writesYou're right. I did the dirty work on my VM yesterday, and held off on my live system, and sure enough, it's not doing
<snip>
I think I'll just wait for Microsoft to fix things rather than try anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings > Windows Update now tells me that I'm up to date. I
wonder whether Christmas and New Year meant that this update received less testing than usual before it was released.
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall <john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings >
Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing than usual before it was released.
ant@zimage.comANT (Ant) wrote:
Others' >(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_january_9th_2024/kh32u6f/)
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with
"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in
64-bit W10 Pro. right now. I already rebooted once from other today's updates:
[snip]
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Good news, folks. MS has released a PowerShell script to
automate the process.
Details, courtesy BleepingComputer: https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-script-to-update-windows-10-winre-with-bitlocker-fixes/
(mind the wrap)
The script: Article KB5034957 https://support.microsoft.com/en-us/topic/kb5034957-updating-the-winre-partition-on-deployed-devices-to-address-security-vulnerabilities-in-cve-2024-20666-0190331b-1ca3-42d8-8a55-7fc406910c10
(mind he wrap)
On 1/11/2024 3:01 AM, John Hall wrote:
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall <john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings > Windows Update now tells me that I'm up to date. I wonder whether Christmas and New Year meant that this update received less testing than usual before it was released.
Still getting the same error here today. Not fixed for me.
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall <john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings >
Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing than usual before it was released.
John Hall <john_nospam@jhall.co.uk> wrote:
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings >
Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing than
usual before it was released.
Please check that it indeed has been fixed.
For example on my wife's Windows 10 system, Windows Update indeed says "You're up to date", but in 'Update history' ('Quality Updates' section)
it says that KB5034441 failed to install and gives the 0x80070643 error
code.
So: "You're up to date", but install failure and the update is not re-offered (nor has any other update been offered/installed).
And to answer Paul's question, yes this system has a 'special'
partition layout. *Two* recovery partitions (and the HP 'RECOVERY'
partition which probably still contains the HP-proprietary recovery for Windows 8):
From 'Disk Management':
[Partition type descriptions translated from Dutch:]
Partition 1: Recovery partition (400 MB)
Partition 2: EFI system partition (260 MB)
Partition : Windows (C:) partition (449.96 GB)
Partition 5: Recovery partition (605 MB)
Partition : RECOVERY (D:) partition ( 14.94 GB)
N.B. Partitions are listed in physical order (bottom pane). Disk Management does not list the partition numbers for C: and D: and I don't
see how Disk Management can show the partition numbers of these
partitions.
In the top pane, the order in the 'Volume' column is different than
the physical order: Partition 1, partition 2, partition 5,
RECOVERY (D:), Windows (C:).
But most importantly, the question to Winston, Paul et al:
How can we *check* that the recovery partition was indeed correctly 'fixed'/updated?
Some posters (like John Hall) report no errors, but does that mean
their system is OK/'fixed'/updated?
Others (like 'sticks' and me) report errors, but does that mean their system is *not* OK/'fixed'/updated?
John Hall <john_nospam@jhall.co.uk> wrote:<snip>
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings >
Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing than
usual before it was released.
Please check that it indeed has been fixed.
For example on my wife's Windows 10 system, Windows Update indeed says
"You're up to date", but in 'Update history' ('Quality Updates' section)
it says that KB5034441 failed to install and gives the 0x80070643 error
code.
So: "You're up to date", but install failure and the update is not
re-offered (nor has any other update been offered/installed).
Ant wrote on 1/11/24 7:51 PM:
George <george.ruch74@gmail.com> wrote:
ant@zimage.comANT (Ant) wrote:
Others'
(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_january_9th_2024/kh32u6f/)
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with
"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in
64-bit W10 Pro. right now. I already rebooted once from other today's updates:
[snip]
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Good news, folks. MS has released a PowerShell script to
automate the process.
Details, courtesy BleepingComputer:
https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-script-to-update-windows-10-winre-with-bitlocker-fixes/
(mind the wrap)
The script: Article KB5034957
https://support.microsoft.com/en-us/topic/kb5034957-updating-the-winre-partition-on-deployed-devices-to-address-security-vulnerabilities-in-cve-2024-20666-0190331b-1ca3-42d8-8a55-7fc406910c10
(mind he wrap)
Has anyone tried it yet? Is it safe or buggy? :)
Successful results from the Enterprise community(some of the Admins responsible for 100,000+ devices still using Win10)
Same identical link for the Powershell script(s)I posted yesterday Jan
10, 2024.
Also note, in both the consumer and Enterprise community reports(earlier today) have indicated that rerunning Windows Update to install the same update are now yielding successful results.
i.e. MSFT has updated the code for the Jan. 2024 cumulative update.
- in this case the general understanding is they reverted to or
modified existing code, that updated the Windoes RE envirorment(and its partition on disk) that was in use from June 2023 through Dec 2023(WinRE
has been included in Cumulative Updates since June 2023 without issues encountered by the Jan. 2024 update)
In both of the above successful cases, do realize that there are
hundreds, thousands or more of different devices and not all operating
under the same conditions as one's own device.
Good news, folks. MS has released a PowerShell script to
automate the process.
Details, courtesy BleepingComputer: https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-sc ript-to-update-windows-10-winre-with-bitlocker-fixes/ (mind the
wrap)
The script: Article KB5034957 https://support.microsoft.com/en-us/topic/kb5034957-updating-the-wi nre-partition-on-deployed-devices-to-address-security-vulnerabiliti es-in-cve-2024-20666-0190331b-1ca3-42d8-8a55-7fc406910c10 (mind he
wrap)
John Hall <john_nospam@jhall.co.uk> wrote:
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings >
Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing than
usual before it was released.
Please check that it indeed has been fixed.
For example on my wife's Windows 10 system, Windows Update indeed says "You're up to date", but in 'Update history' ('Quality Updates' section)
it says that KB5034441 failed to install and gives the 0x80070643 error
code.
So: "You're up to date", but install failure and the update is not re-offered (nor has any other update been offered/installed).
And to answer Paul's question, yes this system has a 'special'
partition layout. *Two* recovery partitions (and the HP 'RECOVERY'
partition which probably still contains the HP-proprietary recovery for Windows 8):
From 'Disk Management':
[Partition type descriptions translated from Dutch:]
Partition 1: Recovery partition (400 MB)
Partition 2: EFI system partition (260 MB)
Partition : Windows (C:) partition (449.96 GB)
Partition 5: Recovery partition (605 MB)
Partition : RECOVERY (D:) partition ( 14.94 GB)
N.B. Partitions are listed in physical order (bottom pane). Disk
Management does not list the partition numbers for C: and D: and I don't
see how Disk Management can show the partition numbers of these
partitions.
In the top pane, the order in the 'Volume' column is different than
the physical order: Partition 1, partition 2, partition 5,
RECOVERY (D:), Windows (C:).
But most importantly, the question to Winston, Paul et al:
How can we *check* that the recovery partition was indeed correctly 'fixed'/updated?
Some posters (like John Hall) report no errors, but does that mean
their system is OK/'fixed'/updated?
Others (like 'sticks' and me) report errors, but does that mean their system is *not* OK/'fixed'/updated?
Nil wrote on 1/12/24 4:07 PM:
The script: Article KB5034957
https://support.microsoft.com/en-us/topic/kb5034957-updating-the-winre-partition-on-deployed-devices-to-address-security-vulnerabilities-in-cve-2024-20666-0190331b-1ca3-42d8-8a55-7fc406910c10
(mind he wrap)
This confuses me. If I'm reading things right, the update failed
because the recovery partition is too small. The article says,
"the company now also provides a dedicated PowerShell script to
help you automate updating the WinRE partition (without having to
resize it first) and patching the CVE-2024-20666 BitLocker
vulnerability." It's not clear to me whether the script resizes
the partition or not My recovery partition on this desktop is 542
MB. If that was too small before, is the script going to fix the
basic problem?
The script in the referenced support article does not resize the
partition. - This script only performs the installation, and only
if you have downloaded the Safe OS update package. It doesn't
resize any partitions. It also requires that the packages are
actually available and have already been downloaded.
The script does check for Bitlocker and disable and reenable WinRE
if it's enabled.
Ideally, what size should the Recovery Partition be? I see on twoMultiple recovery partitions?
of my other computers, both of which took the update
successfully, have multiple (redundant?) recovery partitions,
totaling about 15 GB.
How many?
Please specify the sizes of each one.
While one could have multiple Recovery partitions for Windows, one
could also have one active Recovery partition, and/or an
inactive(useless) or OEM 'Recovery partition'. The OEM Recovery
partition are usually very large(GB) and is not the active
Recovery partition being addressed/updated with the January 2024 update/patch. - The OEM Recovery partition was placed on the
device, as-shipped, by the OEM to allow the end-user(purchaser) to
reset the device to as-shipped condition(i.e. it has no bearing on
the Jan. 2024 update or updating the active Windows Recovery
partition
On 1/12/2024 6:31 AM, Frank Slootweg wrote:I just tried my system last night and I have 566M in Recovery.
John Hall <john_nospam@jhall.co.uk> wrote:
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings >
Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing than >>> usual before it was released.
Please check that it indeed has been fixed.
For example on my wife's Windows 10 system, Windows Update indeed says
"You're up to date", but in 'Update history' ('Quality Updates' section)
it says that KB5034441 failed to install and gives the 0x80070643 error
code.
So: "You're up to date", but install failure and the update is not
re-offered (nor has any other update been offered/installed).
And to answer Paul's question, yes this system has a 'special'
partition layout. *Two* recovery partitions (and the HP 'RECOVERY'
partition which probably still contains the HP-proprietary recovery for
Windows 8):
From 'Disk Management':
[Partition type descriptions translated from Dutch:]
Partition 1: Recovery partition (400 MB)
Partition 2: EFI system partition (260 MB)
Partition : Windows (C:) partition (449.96 GB)
Partition 5: Recovery partition (605 MB)
Partition : RECOVERY (D:) partition ( 14.94 GB)
N.B. Partitions are listed in physical order (bottom pane). Disk
Management does not list the partition numbers for C: and D: and I don't
see how Disk Management can show the partition numbers of these
partitions.
In the top pane, the order in the 'Volume' column is different than
the physical order: Partition 1, partition 2, partition 5,
RECOVERY (D:), Windows (C:).
But most importantly, the question to Winston, Paul et al:
How can we *check* that the recovery partition was indeed correctly
'fixed'/updated?
Some posters (like John Hall) report no errors, but does that mean
their system is OK/'fixed'/updated?
Others (like 'sticks' and me) report errors, but does that mean their
system is *not* OK/'fixed'/updated?
This has certainly turned into a hobby :-)
[Picture]
https://i.postimg.cc/HnkmKP8X/4441-installed-OK-dates-filesize.gif
Paul
On 1/12/24 09:14 PM, Paul wrote:Just saw Winston's remarks that the powershell script only fixes the
On 1/12/2024 6:31 AM, Frank Slootweg wrote:I just tried my system last night and I have 566M in Recovery.
John Hall <john_nospam@jhall.co.uk> wrote:
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try
anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings >
Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing
than
usual before it was released.
  Please check that it indeed has been fixed.
  For example on my wife's Windows 10 system, Windows Update indeed
says
"You're up to date", but in 'Update history' ('Quality Updates' section) >>> it says that KB5034441 failed to install and gives the 0x80070643 error
code.
  So: "You're up to date", but install failure and the update is not
re-offered (nor has any other update been offered/installed).
  And to answer Paul's question, yes this system has a 'special'
partition layout. *Two* recovery partitions (and the HP 'RECOVERY'
partition which probably still contains the HP-proprietary recovery for
Windows 8):
 From 'Disk Management':
[Partition type descriptions translated from Dutch:]
Partition 1: Recovery     partition (400 MB)
Partition 2: EFI system   partition (260 MB)
Partition : Windows (C:) partition (449.96 GB)
Partition 5: Recovery     partition (605 MB)
Partition : RECOVERY (D:) partition ( 14.94 GB)
  N.B. Partitions are listed in physical order (bottom pane). Disk
Management does not list the partition numbers for C: and D: and I don't >>> see how Disk Management can show the partition numbers of these
partitions.
  In the top pane, the order in the 'Volume' column is different than >>> the physical order: Partition 1, partition 2, partition 5,
RECOVERY (D:), Windows (C:).
  But most importantly, the question to Winston, Paul et al:
  How can we *check* that the recovery partition was indeed correctly >>> 'fixed'/updated?
  Some posters (like John Hall) report no errors, but does that mean
their system is OK/'fixed'/updated?
  Others (like 'sticks' and me) report errors, but does that mean their >>> system is *not* OK/'fixed'/updated?
This has certainly turned into a hobby :-)
   [Picture]
    https://i.postimg.cc/HnkmKP8X/4441-installed-OK-dates-filesize.gif >>
  Paul
I did the manual way and when I did the shrink on the OS partition it failed. 96G, said it could not shrink, something about the new size
would be less than the minimum.
And I did verify that the Sel Part was 4 for OS and 5 for Recovery and I
was on the right partition.
Now I wonder if I should run the powershell script? Will it abort and
reset properly if this error pops up there?
You're right Paul. I've spent less time on hobbies.
Frank Slootweg wrote on 1/12/24 4:31 AM:
And to answer Paul's question, yes this system has a 'special'
partition layout. *Two* recovery partitions (and the HP 'RECOVERY' partition which probably still contains the HP-proprietary recovery for Windows 8):
From 'Disk Management':
[Partition type descriptions translated from Dutch:]
Partition 1: Recovery partition (400 MB)
Partition 2: EFI system partition (260 MB)
Partition : Windows (C:) partition (449.96 GB)
Partition 5: Recovery partition (605 MB)
Partition : RECOVERY (D:) partition ( 14.94 GB)
N.B. Partitions are listed in physical order (bottom pane). Disk Management does not list the partition numbers for C: and D: and I don't see how Disk Management can show the partition numbers of theseIt does not, it has a drive label.
partitions.
On your device
MSR(not shown) iw partition 3
C: is partition 4
D: is partition 6
In the top pane, the order in the 'Volume' column is different than
the physical order: Partition 1, partition 2, partition 5,
RECOVERY (D:), Windows (C:).
You've variety of built-in tools to view partitions in an admin mode. PowerShell's command Get-Volume
- shows about the same as Disk Management
Diskpart provides a little more depth
List Vol (all partitions/volumes with and without assigned drive labels)
Sel Disk (command to select the desired disk)
List Part (command to list and show the partitions and partition number
on the selected disk)
On 1/13/24 07:33 AM, Big Al wrote:
On 1/12/24 09:14 PM, Paul wrote:Just saw Winston's remarks that the powershell script only fixes the win.re not the partition size.
On 1/12/2024 6:31 AM, Frank Slootweg wrote:I just tried my system last night and I have 566M in Recovery.
John Hall <john_nospam@jhall.co.uk> wrote:
In message <r+dvniBRdnnlFwAy@jhall_nospamxx.co.uk>, John Hall
<john_nospam@jhall.co.uk> writes
<snip>
I think I'll just wait for Microsoft to fix things rather than try >>>>>> anything fancy.
I'm glad I waited, as Microsoft now seem to have fixed it. Settings > >>>>> Windows Update now tells me that I'm up to date. I wonder whether
Christmas and New Year meant that this update received less testing than >>>>> usual before it was released.
  Please check that it indeed has been fixed.
  For example on my wife's Windows 10 system, Windows Update indeed says
"You're up to date", but in 'Update history' ('Quality Updates' section) >>>> it says that KB5034441 failed to install and gives the 0x80070643 error >>>> code.
  So: "You're up to date", but install failure and the update is not >>>> re-offered (nor has any other update been offered/installed).
  And to answer Paul's question, yes this system has a 'special'
partition layout. *Two* recovery partitions (and the HP 'RECOVERY'
partition which probably still contains the HP-proprietary recovery for >>>> Windows 8):
 From 'Disk Management':
[Partition type descriptions translated from Dutch:]
Partition 1: Recovery     partition (400 MB)
Partition 2: EFI system   partition (260 MB)
Partition : Windows (C:) partition (449.96 GB)
Partition 5: Recovery     partition (605 MB)
Partition : RECOVERY (D:) partition ( 14.94 GB)
  N.B. Partitions are listed in physical order (bottom pane). Disk
Management does not list the partition numbers for C: and D: and I don't >>>> see how Disk Management can show the partition numbers of these
partitions.
  In the top pane, the order in the 'Volume' column is different than >>>> the physical order: Partition 1, partition 2, partition 5,
RECOVERY (D:), Windows (C:).
  But most importantly, the question to Winston, Paul et al:
  How can we *check* that the recovery partition was indeed correctly >>>> 'fixed'/updated?
  Some posters (like John Hall) report no errors, but does that mean >>>> their system is OK/'fixed'/updated?
  Others (like 'sticks' and me) report errors, but does that mean their >>>> system is *not* OK/'fixed'/updated?
This has certainly turned into a hobby :-)
   [Picture]
    https://i.postimg.cc/HnkmKP8X/4441-installed-OK-dates-filesize.gif >>>
  Paul
I did the manual way and when I did the shrink on the OS partition it failed. 96G, said it could not shrink, something about the new size would be less than the minimum.
And I did verify that the Sel Part was 4 for OS and 5 for Recovery and I was on the right partition.
Now I wonder if I should run the powershell script? Will it abort and reset properly if this error pops up there?
You're right Paul. I've spent less time on hobbies.
Just saw Winston's remarks that the powershell script only fixes
the win.re not the partition size.
On 13 Jan 2024, Big Al <alan@invalid.com> wrote in
alt.comp.os.windows-10:
Just saw Winston's remarks that the powershell script only fixes
the win.re not the partition size.
So, this implies to me that the script will get us through the current
error condition, but if there's a similar update in the future we may
run into it again, due to low free space in the recovery partition.
Would you agree?
On 1/13/24 01:41 PM, Nil wrote:I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
On 13 Jan 2024, Big Al <alan@invalid.com> wrote inI would agree. I've tried to do the manual resize and it fails. It worked on a VM but not my live system. I dual boot Linux.
alt.comp.os.windows-10:
Just saw Winston's remarks that the powershell script only fixes
the win.re not the partition size.
So, this implies to me that the script will get us through the current
error condition, but if there's a similar update in the future we may
run into it again, due to low free space in the recovery partition.
Would you agree?
I'm looking into doing defrag or jkdefrag as Paul has noted to get some space at the end. That might be why it won't shrink.
This is (now) a low priority item.Using jkdefrag I found that restore points were shoved at the end of the drive.
I deleted all of them then went back and ran those manual commands and I
was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably
should have shoved it 500M, but... It's at 881M now.
Paul wrote on 1/12/24 7:14 PM:
And will be as long as WinRE continues to grow(apparently like yours has, since it would be unlikely to have ever been initially created as a 759 MB partition)
This has certainly turned into a hobby :-)
   [Picture]
    https://i.postimg.cc/HnkmKP8X/4441-installed-OK-dates-filesize.gif >>
  Paul
Lol...also unlikely for anyone's WinRE partition to be the same size as another's WinRE partition.
You may recall, I've previously been a proponent of creating the WinRe partition for clean installs at 1 GB.
 - with my Win11 23H2(updated with Jan. 2024 updates) WinRE partition at 827 MB its winre.wim at 811 MB...2 GB could easily become my new recommendation for the WinRE partition.
On 1/13/2024 4:17 PM, Big Al wrote:
I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance you could post
the message ID of the one that had the instructions you followed to get yours working?Â
It would be much appreciated!
...If using Win10 or Win11 and using System Restore to revisit SystemTo resize my partition, I did step 'b' first to get space.
Restore in Windows, then it might be of benefit(after successfully
installing the Jan 2024 update)to:
a. Verify SR is still enabled
b. Delete all SR restore points
d. Enable SR and create a new SR restore point
e. Restart the device
f. Re-image the disk(System, MSR, Windows, and WinRE partitions)
On 1/13/2024 4:17 PM, Big Al wrote:
I deleted all of them then went back and ran those manual commands and
I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and
it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably
should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance
you could post the message ID of the one that had the instructions you followed to get yours working? It would be much appreciated!
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands
and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and
it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably
should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any
chance you could post the message ID of the one that had the
instructions you followed to get yours working? It would be much
appreciated!
Frank Slootweg wrote on 1/13/24 7:44 AM:[...]
[...]In the meantime, I have found that Macrium Reflect (Free) gives some more information, including partition numbers:
- Partition 1 seems to be the real - in use - recovery partition,
because MR says:
1 - WINRE (None)
Primary - NTFS
291.4 MB
400.0 MB
- Partition 5 seems to be some kind of left-over recovery partition,
because it is listed without a label (no 'WINRE'):
5 - (None)
Primary - NTFS
523.4 MB
605.0 MB
- Partition 3 is indeed the MSR (Microsoft Reserved Partition):
3 - (None)
Primary - Unformatted
120.0 MB
120.0 MB
Hi, Frank
In an admin command prompt(Powershell or Command.com) enter
reagentc /info
The result will show WinRE's
- the status (Recovery - Enabled or Disabled)
- location of the active WinRE partition.
It's unlikely that Partition 1 is the real in-use(active) WinRE partition.
More likely, that the OEM or a post device first use and much earlier
Windows installation version placed a WinRE before the o/s partition.
- Up until Windows 10 version 2004, a clean install(including OEM's who
did not follow GPT partitioning Guidelines) placed the Recovery partition
at the beginning of the disk. Any upgrade that required a larger recovery partition then placed the new one after the Windows partition(carving
space out of the Windows partition)
=> MSFT fixed this in Windows 10 2004 version releasing an updated
Media Creation Tool for creating installation media(usb or iso) and also
ISO builds available in Visual Studio subscriptionsA(fka MSDN and TechNet)
=> Devices that initially had WinRE as the first partition and as the active WinRE partition were fine up until that Recovery partition became
too small to handle an increase in size of the WinRE partitions files(primarily winre.wim). Windows by design and consistent with GPT partitioning guidelines created a new and active WinRE partition after
the Windows partition.
i.e. Partition 5 would be your device's 'active, enabled, WinRE partition)...and also by design, it does not have a label.
On 1/13/2024 6:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:
I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance you could post
the message ID of the one that had the instructions you followed to get yours working?
It would be much appreciated!
We have not reduced the answer to this question to a "recipe".
You could have Bitlocker encryption on the disk drive. While Bitlocker
is not "supported" on Home, and is supported on Pro, the manage-bde
utility may be present anyway, to give some information. Some people to
this day, are blissfully unaware their disk is encrypted. Surprise!
manage-bde -status
Early in the thread, we were treated to the support.microsoft.com article.
I tried to provide a picture of my disk drive, and show
the commands I would use to fix my specific case. I generally
do not use crypto, if I can possibly avoid it. (Only my VMWare
virtual machine with the Win11 in it, is encrypted, as VMWare
did not offer any options in the matter. Users even told VMWare how
to do this. Crickets.)
A typical user might have a UEFI installation on a modern computer, with
a GPT partitioned disk. The worked example assumes these characteristics.
I had to "avoid" using my legacy MBR Win10 installation, as it would mislead people a bit. More people could be here on OEM setups, in which case
the possible disk layouts, crypto situations, just explodes. Thus,
this example is a very narrow and "best-guess" at what you might find.
OEM systems will be GPT. A lot of users in the group, might well have selected GPT for the flexibility it offers.
A couple posters have already recommended waiting until Microsoft fixes this. If you're a multi-booter with *lots* of experience, I think you can handle this,
but then, you'd be finished by now.
The standard advice (which I use religiously when standing on a shaky platform),
is to do a full disk backup before attempting anything like this.
https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
# Administrator Command Prompt, or Admin Powershell then type "cmd.exe" as a command
reagentc /info # shows recovery agent is enabled, and is using Partition 4
# The article should show what that looks like. A picture would help.
# If your reagentc is blank or messed up, *stop now*. See example further down,
# for what one looks like.
[Picture] This picture shows my disk setup, and makes a reference to the invisible non-partition known as MSR (reserved/junk area)
Partition 2 can be seen from Linux gparted /dev/sda , if you really want to see the disk layout.
The disktype.exe utility also shows it, but it's only available via a Cygwin installation.
I do not really want to lard up this answer with a lot more utility photos. I guess even List Partition
shows it, come to think of it.
https://i.postimg.cc/sgXwB389/diskpart-disk-summary.gif
reagentc /disable # Disable recovery environment agent before making changes
diskpart.exe # Now, we're doing shrink of C: and regeneration (empty) Recovery partition 4
list disk
select disk 0
list partition
select partition 3 # will shrink C: now. This could fail, if the $USN journal is right at the end of C: .
shrink desired=250 minimum=250 # runtime 1 second (*normally* the end of the disk doesn't have a blocker up there)
select partition 4
delete partition override # "delete partition" is the command we seek to cowboy at this point
# This solves the inability to change the origin of a partition in DiskMgmt. Deleting Partition 4
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac # The ID is a partition type, it's our Recovery partition.
gpt attributes =0x8000000000000001 # <=== Protected status of partition. Partitions
# can be "marked" as "being special" [Attribute]
# Yes, there are fourteen zeros in that constant.
format quick fs=ntfs label="Windows RE tools" # Partition 4 is NTFS, and now it has no content. Empty file system.
# Partition is likely hidden by its ID value. The Windows Update will fill it up.
exit
reagentc /enable # Even though Partition 4 is empty, we can still pretend all is well.
reagentc /info # A sample output is provided, after this line.
Windows Recovery Environment (Windows RE) and system reset configuration Information:
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE <=== partition pointer remains as before
Boot Configuration Data (BCD) identifier: 964e2ef1-3a60-11ed-81d3-5cf3707d2fda <=== likely inside ESP Partition 1
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
Anyway, that was enough operations for me to fix mine. YMMV, OK?
... Time passes. Somehow, we encourage '4441 to install. We think
a new WinRE.wim was installed. How to prove it ?
To prove '4441 has installed my new WinRE, I used TestDisk version 7.
Using this is actually too complicated to explain. Which speaks well of the interface.
Not a problem. We have an alternative.
[Picture]
https://i.postimg.cc/HnkmKP8X/4441-installed-OK-dates-filesize.gif
The alternative, is more Diskpart. Administrator window of some sort,
or otherwise, diskpart will elevate itself.
diskpart.exe
list disk
select disk 0
list partition
select partition 4 # We're pointed to the 0x27 style hidden Recovery partition now.
assign letter=K # Temporarily assigning a drive letter, to make partition visibie.
# Permissions can *still* prevent us from doing stuff. File Manager
# pointing to K: , is not very helpful right now.
exit
In the same administrator window, to prove '4441 is present, now we have access to the partition via the letter K. (The letter K will be removed
on a reboot. If you want it per-session, you have to do the procedure per-session.) You should see three files with Jan 2024 datestamps or so.
The slash a h is asking to display all files with a Hidden attribute set.
dir /ah K:\Recovery\WindowsRE
So that's about it... for me.
Paul
On 1/14/2024 7:25 AM, Big Al wrote:
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands
and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and
it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably
should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any
chance you could post the message ID of the one that had the
instructions you followed to get yours working? It would be much
appreciated!
Thanks AL!
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands
and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update
and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably
should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any
chance you could post the message ID of the one that had the
instructions you followed to get yours working? It would be much
appreciated!
Thanks AL!
shrink fails, then just exit and reagentc /enable.
No harm done. That was my issue. The os would not shrink, no room at
the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at the end stopping the shrink. They were the files I could move / delete etc.
Then I could restart the process.
On 1/14/2024 2:34 PM, Big Al wrote:
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands >>>>>> and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update
and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably >>>>>> should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any
chance you could post the message ID of the one that had the
instructions you followed to get yours working? It would be much
appreciated!
Thanks AL!
shrink fails, then just exit and reagentc /enable.
No harm done. That was my issue. The os would not shrink, no room at
the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at the
end stopping the shrink. They were the files I could move / delete etc.
Then I could restart the process.
Fortunately, I had lots of space on that drive and partition and did not
have this problem.
I did solve the update problem on this system using Paul's explanation
of basically the same link Al provided. One of the commands was not
quite the right syntax, but help provided the full correct one, and it worked. Don't know why that was.
I shrank the C: partition by 1000mb and built a new WinRE partition by
the same 1000 mb. Now the total of my RE partition is 1527MB or 1.49
GB. After completing everything on the MS link, I ran updates again and
it installed immediately. I then did another macrium image and deleted
the old one. As far as I'm concerned that should be the end of it for now! Checked the wife's laptop and it has a 15G RE partition (don't know why
it's that big) and had successfully installed the update.
Checked my newest system that is about 2 years old and has an SSD drive,
and it hadn't been offered it yet. Upon checking it downloaded it and
it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB free. So, after sending this, it's down
to that computer to do it all on that one too. At least I'm not so intimidated now. Now I am not a total newbie on computers, but
certainly not a guru of any sorts, but I still can't think of any of the people I know who could do this. They wouldn't even try. This all
doesn't seem acceptable to me.
Much thanks to everyone, especially Big Al, Paul and Winston!
On 1/14/24 05:17 PM, sticks wrote:did another macrium image and deleted the old one. As far as I'm concerned that should be the end of it for now!
On 1/14/2024 2:34 PM, Big Al wrote:
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the shrink fails, then just exit and reagentc /enable.
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance you could post the message ID of the one that had the instructions you followed to get yours working? It would be much appreciated!
Thanks AL!
No harm done. That was my issue. The os would not shrink, no room at the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at the end stopping the shrink. They were the files I could move / delete etc.
Then I could restart the process.
Fortunately, I had lots of space on that drive and partition and did not have this problem.
I did solve the update problem on this system using Paul's explanation of basically the same link Al provided. One of the commands was not quite the right syntax, but help provided the full correct one, and it worked. Don't know why that was.
I shrank the C: partition by 1000mb and built a new WinRE partition by the same 1000 mb. Now the total of my RE partition is 1527MB or 1.49 GB. After completing everything on the MS link, I ran updates again and it installed immediately. I then
free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now. Now I am not a total newbie on computers, but certainly not a guru of any sorts, but I still can't think of any of theChecked the wife's laptop and it has a 15G RE partition (don't know why it's that big) and had successfully installed the update.
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
I kinda wish I had added 1G to mine rather than 250. I may go back one day and up it.  Now that I know how.
Much thanks to everyone, especially Big Al, Paul and Winston!
Checked my newest system that is about 2 years old and has an SSD drive,
and it hadn't been offered it yet. Upon checking it downloaded it and
it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB free. So, after sending this, it's down
to that computer to do it all on that one too. At least I'm not so intimidated now.
On 1/14/2024 6:11 PM, Big Al wrote:did another macrium image and deleted the old one. As far as I'm concerned that should be the end of it for now!
On 1/14/24 05:17 PM, sticks wrote:
On 1/14/2024 2:34 PM, Big Al wrote:
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the shrink fails, then just exit and reagentc /enable.
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance you could post the message ID of the one that had the instructions you followed to get yours working? It would be much appreciated!
Thanks AL!
No harm done. That was my issue. The os would not shrink, no room at the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at the end stopping the shrink. They were the files I could move / delete etc.
Then I could restart the process.
Fortunately, I had lots of space on that drive and partition and did not have this problem.
I did solve the update problem on this system using Paul's explanation of basically the same link Al provided. One of the commands was not quite the right syntax, but help provided the full correct one, and it worked. Don't know why that was.
I shrank the C: partition by 1000mb and built a new WinRE partition by the same 1000 mb. Now the total of my RE partition is 1527MB or 1.49 GB. After completing everything on the MS link, I ran updates again and it installed immediately. I then
free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now. Now I am not a total newbie on computers, but certainly not a guru of any sorts, but I still can't think of any of theChecked the wife's laptop and it has a 15G RE partition (don't know why it's that big) and had successfully installed the update.
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
I kinda wish I had added 1G to mine rather than 250. I may go back one day and up it.  Now that I know how.
Much thanks to everyone, especially Big Al, Paul and Winston!
Since I had one more Patch Tuesday to do, I decided to try using partition tools, rather than diskpart.
I tried Paragon PM14 Free, and it was leaving little gaps between
partitions. I fired up Linux gparted, and I was able to shrink C:
by whatever I wanted, then use gparted to move the Reserved partition
to the left. Then, resized the Reserved partition (which is a hidden type), and it all went fine. This means, I did not actually delete Reserved
and make a new one. It's the same partition it was before, just resized.
I did a reagentc /disable, did my partition stuff, then reagentc /enable afterwards. '4441 installed (because at that point, I'd plugged
the Ethernet cable back in). The contents of Reserved look the same as
the other Windows 10 ones.
This is not a major savings by any means, and no simpler. But when it
comes to shrinking and moving, since Windows is at rest while Linux
runs, there is hardly any resistance to what you are doing. Maybe
I didn't really need to disable reagentc, and I could have left it alone.
This means, when '4441 installs, it would have to remove the old WinRE.wim before installing the new bigger one.
Paul
On 1/14/2024 4:17 PM, sticks wrote:free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now.
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
Well that didn't go as easily as I had hoped!Can't remember the exact wording, but it couldn't find the WinRE.wim file. I did find a copy of the file on the disk, and tried copying it into C:\windows\system32\recovery but that alone did not work. After a little researching, one suggestion was
Once again I followed the directions on the link Big Al gave. The only difference was this system is GPT and not MBR. No problem, directions were easy enough. All went fine until the last 2 steps, step 8, re-enable WinRE. It couldn't do it.Â
reagentc /info still said it was disabled and had no location
So, I then tried reagentc /enable and it worked.
Says it is enabled and it created a new xml file.
Went to windows update and the damn 5034441 is finally installed on all the computers here.
Wow, I sure hope grandma can do this!
On 1/14/24 07:04 PM, Paul wrote:then did another macrium image and deleted the old one. As far as I'm concerned that should be the end of it for now!
On 1/14/2024 6:11 PM, Big Al wrote:
On 1/14/24 05:17 PM, sticks wrote:
On 1/14/2024 2:34 PM, Big Al wrote:
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the shrink fails, then just exit and reagentc /enable.
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance you could post the message ID of the one that had the instructions you followed to get yours working? It would be much appreciated!
Thanks AL!
No harm done. That was my issue. The os would not shrink, no room at the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at the end stopping the shrink. They were the files I could move / delete etc.
Then I could restart the process.
Fortunately, I had lots of space on that drive and partition and did not have this problem.
I did solve the update problem on this system using Paul's explanation of basically the same link Al provided. One of the commands was not quite the right syntax, but help provided the full correct one, and it worked. Don't know why that was.
I shrank the C: partition by 1000mb and built a new WinRE partition by the same 1000 mb. Now the total of my RE partition is 1527MB or 1.49 GB. After completing everything on the MS link, I ran updates again and it installed immediately. I
free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now. Now I am not a total newbie on computers, but certainly not a guru of any sorts, but I still can't think of any of theChecked the wife's laptop and it has a 15G RE partition (don't know why it's that big) and had successfully installed the update.
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
What "stuff" did you do? If you resized the partition with gparted, I would think the job was done.I kinda wish I had added 1G to mine rather than 250. I may go back one day and up it.  Now that I know how.
Much thanks to everyone, especially Big Al, Paul and Winston!
Since I had one more Patch Tuesday to do, I decided to try using partition >> tools, rather than diskpart.
I tried Paragon PM14 Free, and it was leaving little gaps between
partitions. I fired up Linux gparted, and I was able to shrink C:
by whatever I wanted, then use gparted to move the Reserved partition
to the left. Then, resized the Reserved partition (which is a hidden type), >> and it all went fine. This means, I did not actually delete Reserved
and make a new one. It's the same partition it was before, just resized.
I did a reagentc /disable, did my partition stuff, then reagentc /enable
afterwards. '4441 installed (because at that point, I'd plugged
the Ethernet cable back in). The contents of Reserved look the same as
the other Windows 10 ones.
On 1/14/2024 10:10 PM, Big Al wrote:then did another macrium image and deleted the old one. As far as I'm concerned that should be the end of it for now!
On 1/14/24 07:04 PM, Paul wrote:
On 1/14/2024 6:11 PM, Big Al wrote:
On 1/14/24 05:17 PM, sticks wrote:
On 1/14/2024 2:34 PM, Big Al wrote:
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the shrink fails, then just exit and reagentc /enable.
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance you could post the message ID of the one that had the instructions you followed to get yours working? It would be much appreciated!
Thanks AL!
No harm done. That was my issue. The os would not shrink, no room at the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at the end stopping the shrink. They were the files I could move / delete etc.
Then I could restart the process.
Fortunately, I had lots of space on that drive and partition and did not have this problem.
I did solve the update problem on this system using Paul's explanation of basically the same link Al provided. One of the commands was not quite the right syntax, but help provided the full correct one, and it worked. Don't know why that was.
I shrank the C: partition by 1000mb and built a new WinRE partition by the same 1000 mb. Now the total of my RE partition is 1527MB or 1.49 GB. After completing everything on the MS link, I ran updates again and it installed immediately. I
80MB free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now. Now I am not a total newbie on computers, but certainly not a guru of any sorts, but I still can't think of any of theChecked the wife's laptop and it has a 15G RE partition (don't know why it's that big) and had successfully installed the update.
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than
What "stuff" did you do? If you resized the partition with gparted, I would think the job was done.I kinda wish I had added 1G to mine rather than 250. I may go back one day and up it.  Now that I know how.
Much thanks to everyone, especially Big Al, Paul and Winston!
Since I had one more Patch Tuesday to do, I decided to try using partition >>> tools, rather than diskpart.
I tried Paragon PM14 Free, and it was leaving little gaps between
partitions. I fired up Linux gparted, and I was able to shrink C:
by whatever I wanted, then use gparted to move the Reserved partition
to the left. Then, resized the Reserved partition (which is a hidden type), >>> and it all went fine. This means, I did not actually delete Reserved
and make a new one. It's the same partition it was before, just resized. >>>
I did a reagentc /disable, did my partition stuff, then reagentc /enable >>> afterwards. '4441 installed (because at that point, I'd plugged
the Ethernet cable back in). The contents of Reserved look the same as
the other Windows 10 ones.
I initially started work with PM14 on Windows, because I wanted to
see if PM14 could manage to do the whole thing. Cleaning up the
cosmetic issues on Linux was a bit easier, and I finished the process
by doing the Reserved origin shift and resize there. I think Paragon
did not want to resize the Reserved partition, but it allowed the
origin to move.
Of the two, the Linux gparted seemed to be the most capable, but
that's a hard sell for the audience. I was mainly curious to see
if I could do it, without have to erase the partition, create
a new one, format it, and so on.
I would have preferred that Paragon PM14 Free, be a bit more
cooperative. I believe there is a later free version than 2014. They offer Move/Resize as the only functional thing on their Free version,
which is better than the vanilla Resize in Disk Management. Some
OPs on Paragon, require a reboot. It's not "Apple Magical" at all.
When it is time to reboot, you will be thinking about your
old Ghost days. But that's the price to pay, for asking it
to work on data that is "not at rest".
Paul
On 1/14/2024 9:44 PM, sticks wrote:free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now.
On 1/14/2024 4:17 PM, sticks wrote:
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
Can't remember the exact wording, but it couldn't find the WinRE.wim file. I did find a copy of the file on the disk, and tried copying it into C:\windows\system32\recovery but that alone did not work. After a little researching, one suggestion was
Well that didn't go as easily as I had hoped!
Once again I followed the directions on the link Big Al gave. The only difference was this system is GPT and not MBR. No problem, directions were easy enough. All went fine until the last 2 steps, step 8, re-enable WinRE. It couldn't do it.Â
There's a link to a powershell script, .ps1, that is supposed to fix
reagentc /info still said it was disabled and had no location
So, I then tried reagentc /enable and it worked.
Says it is enabled and it created a new xml file.
Went to windows update and the damn 5034441 is finally installed on all the computers here.
Wow, I sure hope grandma can do this!
That Linux Grandma, she gets around. She can bake a
cake while installing '4441. Fixing Windows Update is
no harder than making a batch of shortbread cookies.
One of the steps is to delete the Reserved partition (with Override, to make it possible).
Creating a new partition and formatting it NTFS, of course that will erase the
previous WinRE.wim . And that was one of the concerns I expressed in my first reading of the procedure, is that "reagentc /enable" after all is said and done, the partition is empty, and a routine like that should be sniffing
for details.
The real question, is why this was working in the first place. Why
did "reagentc /enable" work for me ? I don't know the answer to that.
Paul
sticks wrote on 1/14/24 3:17 PM:did another macrium image and deleted the old one. As far as I'm concerned that should be the end of it for now!
On 1/14/2024 2:34 PM, Big Al wrote:
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the shrink fails, then just exit and reagentc /enable.
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual commands and I was able now to expand the partition by that 250M.
The rest of the commands succeeded and then I ran Windows Update and it succeeded also.
So I'm happy that my system has a larger Recovery now. I probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any chance you could post the message ID of the one that had the instructions you followed to get yours working? It would be much appreciated!
Thanks AL!
No harm done. That was my issue. The os would not shrink, no room at the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at the end stopping the shrink. They were the files I could move / delete etc.
Then I could restart the process.
Fortunately, I had lots of space on that drive and partition and did not have this problem.
I did solve the update problem on this system using Paul's explanation of basically the same link Al provided. One of the commands was not quite the right syntax, but help provided the full correct one, and it worked. Don't know why that was.
I shrank the C: partition by 1000mb and built a new WinRE partition by the same 1000 mb. Now the total of my RE partition is 1527MB or 1.49 GB. After completing everything on the MS link, I ran updates again and it installed immediately. I then
free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now. Now I am not a total newbie on computers, but certainly not a guru of any sorts, but I still can't think of any of theChecked the wife's laptop and it has a 15G RE partition (don't know why it's that big) and had successfully installed the update.
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
The 15 GB RE partition is unlikely the 'Active' WinRE partition.
Much thanks to everyone, especially Big Al, Paul and Winston!
OEM' place a recovery partition normally at the end of the disk which is used to restore the device to as-shipped factory condition.
 - the successful update didn't use or touch that 15 GB partition.
Open a Command prompt with admin privileges
At the prompt, enter the following then press the return key.
 reagentc /info
The result will show the real active WinRe partition # and the disk # on which it resides.
 ...w
.\disktype /dev/sda <=== being Cygwin, it uses foreign nomenclature, not a problem. This is disk 0.
On 1/14/2024 9:44 PM, sticks wrote:free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now.
On 1/14/2024 4:17 PM, sticks wrote:
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
Can't remember the exact wording, but it couldn't find the WinRE.wim file. I did find a copy of the file on the disk, and tried copying it into C:\windows\system32\recovery but that alone did not work. After a little researching, one suggestion was
Well that didn't go as easily as I had hoped!
Once again I followed the directions on the link Big Al gave. The only difference was this system is GPT and not MBR. No problem, directions were easy enough. All went fine until the last 2 steps, step 8, re-enable WinRE. It couldn't do it.Â
Having followed up on the KB5034441 not installing, I did the steps to
reagentc /info still said it was disabled and had no location
So, I then tried reagentc /enable and it worked.
Says it is enabled and it created a new xml file.
Went to windows update and the damn 5034441 is finally installed on all the computers here.
Wow, I sure hope grandma can do this!
That Linux Grandma, she gets around. She can bake a
cake while installing '4441. Fixing Windows Update is
no harder than making a batch of shortbread cookies.
One of the steps is to delete the Reserved partition (with Override, to make it possible).
Creating a new partition and formatting it NTFS, of course that will erase the
previous WinRE.wim . And that was one of the concerns I expressed in my first reading of the procedure, is that "reagentc /enable" after all is said and done, the partition is empty, and a routine like that should be sniffing
for details.
The real question, is why this was working in the first place. Why
did "reagentc /enable" work for me ? I don't know the answer to that.
Paul
On 1/15/24 07:56 AM, Paul wrote:free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now.
On 1/14/2024 9:44 PM, sticks wrote:
On 1/14/2024 4:17 PM, sticks wrote:
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
Can't remember the exact wording, but it couldn't find the WinRE.wim file. I did find a copy of the file on the disk, and tried copying it into C:\windows\system32\recovery but that alone did not work. After a little researching, one suggestion was
Well that didn't go as easily as I had hoped!
Once again I followed the directions on the link Big Al gave. The only difference was this system is GPT and not MBR. No problem, directions were easy enough. All went fine until the last 2 steps, step 8, re-enable WinRE. It couldn't do it.Â
There's a link to a powershell script, .ps1, that is supposed to fix this issue by building the winre.wim outside and then moving it to Recovery. I haven't looked at my partition since I fixed it, wonder if it's empty.... hmm another day.
reagentc /info still said it was disabled and had no location
So, I then tried reagentc /enable and it worked.
Says it is enabled and it created a new xml file.
Went to windows update and the damn 5034441 is finally installed on all the computers here.
Wow, I sure hope grandma can do this!
That Linux Grandma, she gets around. She can bake a
cake while installing '4441. Fixing Windows Update is
no harder than making a batch of shortbread cookies.
One of the steps is to delete the Reserved partition (with Override, to make it possible).
Creating a new partition and formatting it NTFS, of course that will erase the
previous WinRE.wim . And that was one of the concerns I expressed in my first
reading of the procedure, is that "reagentc /enable" after all is said and >> done, the partition is empty, and a routine like that should be sniffing
for details.
The real question, is why this was working in the first place. Why
did "reagentc /enable" work for me ? I don't know the answer to that.
   Paul
Having followed up on the KB5034441 not installing, I did the steps to
delete and re-add a larger partition and made it ntfs, etc. Now, the KB >installed successfully, but the (in my case partition 4 ) is empty! I
thought the KB would refill it during installation. Suggestions?
Others' (https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_january_9th_2024/kh32u6f/)
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download
error - 0x80070643" with "2024-01 Security Update for Windows 10
Version 22H2 for x64-based Systems (KB5034441)" in 64-bit W10 Pro.
right now. I already rebooted once from other today's updates:
On 1/15/2024 7:56 AM, Paul wrote:free. So, after sending this, it's down to that computer to do it all on that one too. At least I'm not so intimidated now.
On 1/14/2024 9:44 PM, sticks wrote:
On 1/14/2024 4:17 PM, sticks wrote:
Checked my newest system that is about 2 years old and has an SSD drive, and it hadn't been offered it yet. Upon checking it downloaded it and it too failed. Checked the size of the MR partition and it too is only about 600MB with less than 80MB
Can't remember the exact wording, but it couldn't find the WinRE.wim file. I did find a copy of the file on the disk, and tried copying it into C:\windows\system32\recovery but that alone did not work. After a little researching, one suggestion was
Well that didn't go as easily as I had hoped!
Once again I followed the directions on the link Big Al gave. The only difference was this system is GPT and not MBR. No problem, directions were easy enough. All went fine until the last 2 steps, step 8, re-enable WinRE. It couldn't do it.Â
installation. Suggestions?Having followed up on the KB5034441 not installing, I did the steps to delete and re-add a larger partition and made it ntfs, etc. Now, the KB installed successfully, but the (in my case partition 4 ) is empty! I thought the KB would refill it during
reagentc /info still said it was disabled and had no location
So, I then tried reagentc /enable and it worked.
Says it is enabled and it created a new xml file.
Went to windows update and the damn 5034441 is finally installed on all the computers here.
Wow, I sure hope grandma can do this!
That Linux Grandma, she gets around. She can bake a
cake while installing '4441. Fixing Windows Update is
no harder than making a batch of shortbread cookies.
One of the steps is to delete the Reserved partition (with Override, to make it possible).
Creating a new partition and formatting it NTFS, of course that will erase the
previous WinRE.wim . And that was one of the concerns I expressed in my first
reading of the procedure, is that "reagentc /enable" after all is said and >> done, the partition is empty, and a routine like that should be sniffing
for details.
The real question, is why this was working in the first place. Why
did "reagentc /enable" work for me ? I don't know the answer to that.
   Paul
Did you ever try mintool partition wizard? https://www.partitionwizard.com/free-partition-manager.html
Ant wrote:
Others'
(https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_january_9th_2024/kh32u6f/)
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download
error - 0x80070643" with "2024-01 Security Update for Windows 10
Version 22H2 for x64-based Systems (KB5034441)" in 64-bit W10 Pro.
right now. I already rebooted once from other today's updates:
I am at version 10.0.19045.3930 on all my computers. Is that where I should be?
On 1/15/2024 8:44 AM, Big Al wrote:
Did you ever try mintool partition wizard?
https://www.partitionwizard.com/free-partition-manager.html
No, like backup tools, these things require a lot of careful
test, before you trust them.
Others' (https://www.reddit.com/r/Windows10/comments/192l9kj/cumulative_updates_januar
y_9th_2024/kh32u6f/)
and my updated 64-bit W10 Pro. PC, I'm getting "Status: Download error - 0x80070643" with
"2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441)" in
64-bit W10 Pro. right now. I already rebooted once from other today's updates:
1. https://support.microsoft.com/en-us/topic/january-9-2024-kb5034275-cumulati
ve-update-for-net-framework-3-5-4-8-and-4-8-1-for-windows-10-version-22h2-6c9a
603c-f0a1-4b32-b7fa-a1c6337523f1
2. https://support.microsoft.com/en-us/topic/january-9-2024-kb5034122-os-build
s-19044-3930-and-19045-3930-7656c6a4-0b06-4424-86a9-d0719f4ac252
I read https://support.microsoft.com/en-us/topic/kb5034441-windows-recovery-environme
nt-update-for-windows-10-version-21h2-and-22h2-january-9-2024-62c04204-aaa5-4f
ee-a02a-2fdea17075a8
's known issue about small WinRE partition with a https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-r
esize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c82
29763bf
link.
Couldn't MS do this to its users automatically without having to do it manually for
non-technical users? :/
Paul wrote on 1/14/24 5:04 PM:
This means, when '4441 installs, it would have to remove the old WinRE.wim >> before installing the new bigger one.
   Paul
Windows keeps a log file when the 'reagentc /disable' command is done.
 The logfile's location and name
 C:\Windows\Logs\ReAgent
  ReAgent.log
If the system is operating under design-intent, when the above command is executed, the winre.wim file is moved from the active recovery partition to the C:\WINDOWS\system32\Recovery\ folder
[ReAgentc.exe] -----Executing command line: reagentc /disable----- [ReAgentc.exe] ------------------------------------------------------ [ReAgentc.exe] Update enhanced config info is enabled.
[ReAgentc.exe] WinRE is installed
[ReAgentc.exe] winreCopyWIMBack moved WIM file from \\?\GLOBALROOT\device\harddisk1\partition4\Recovery\WindowsRE\ to C:\WINDOWS\system32\Recovery\Winre.wim successfully!
This move ensures that the fix which disables, deletes the Recovery partition, shrinks the o/s to create more space for a larger Recovery partition has the ability when reagentc /enable is executed to move the winre.wim from C: back to the Recoverypartition.
 - i.e. if not moved, then the winre.wim file would need to be recovered from media or an ISO.
The same logfile when reagentc /enable is run after resizing(enlarging) the Recovery partition will show the moving of winre.wim back from ...\system32\Recovery to the Recovery partition.
On Mon, 15 Jan 2024 13:16:46 -0500, Paul <nospam@needed.invalid> wrote:
On 1/15/2024 8:44 AM, Big Al wrote:
Did you ever try mintool partition wizard?
https://www.partitionwizard.com/free-partition-manager.html
No, like backup tools, these things require a lot of careful
test, before you trust them.
I would have agreed with you on that point until about 1994. Not so much these
days. The last 30 years have shown us that partitions (and partition managers)
aren't the magical mysterious things that they used to be.
On 1/15/2024 2:36 PM, Char Jackson wrote:
On Mon, 15 Jan 2024 13:16:46 -0500, Paul <nospam@needed.invalid> wrote:
On 1/15/2024 8:44 AM, Big Al wrote:
Did you ever try mintool partition wizard?
https://www.partitionwizard.com/free-partition-manager.html
No, like backup tools, these things require a lot of careful
test, before you trust them.
I would have agreed with you on that point until about 1994. Not so much these
days. The last 30 years have shown us that partitions (and partition managers)
aren't the magical mysterious things that they used to be.
Lets see. Acronis Partition Manager. Few of the routines are
particularly unique. I spot the "cluster size changer" module
in my new purchase. Now, knowing that a function like this is
"very risky", I'm armed with a backup. I push the button.
The churning stops. OK, it says it is done. I start looking
around. I'm in System32, and I see "gee, I never knew Microsoft
put zero sized files in System32". A bit more checking, a number
of files have zero size. If it was a pinball machine, we would
be making the "tilt" sound effect about now.
On Mon, 15 Jan 2024 19:58:53 -0500, Paul <nospam@needed.invalid> wrote:
On 1/15/2024 2:36 PM, Char Jackson wrote:
On Mon, 15 Jan 2024 13:16:46 -0500, Paul <nospam@needed.invalid> wrote:
On 1/15/2024 8:44 AM, Big Al wrote:
Did you ever try mintool partition wizard?
https://www.partitionwizard.com/free-partition-manager.html
No, like backup tools, these things require a lot of careful
test, before you trust them.
I would have agreed with you on that point until about 1994. Not so much these
days. The last 30 years have shown us that partitions (and partition managers)
aren't the magical mysterious things that they used to be.
Lets see. Acronis Partition Manager. Few of the routines are
particularly unique. I spot the "cluster size changer" module
in my new purchase. Now, knowing that a function like this is
"very risky", I'm armed with a backup. I push the button.
The churning stops. OK, it says it is done. I start looking
around. I'm in System32, and I see "gee, I never knew Microsoft
put zero sized files in System32". A bit more checking, a number
of files have zero size. If it was a pinball machine, we would
be making the "tilt" sound effect about now.
I used to be paranoid about working with partitions too, but 30 years and at least several hundred operations without any issues that I can remember have changed that.
sticks wrote on 1/14/24 3:17 PM:
On 1/14/2024 2:34 PM, Big Al wrote:The 15 GB RE partition is unlikely the 'Active' WinRE partition.
On 1/14/24 09:12 AM, sticks wrote:
On 1/14/2024 7:25 AM, Big Al wrote:Note:Â When you get to the part of shrinking the OS by 250M, and the
On 1/13/24 06:25 PM, sticks wrote:
On 1/13/2024 4:17 PM, Big Al wrote:https://support.microsoft.com/en-us/topic/kb5028997-instructions-to-manually-resize-your-partition-to-install-the-winre-update-400faa27-9343-461c-ada9-24c8229763bf
I deleted all of them then went back and ran those manual
commands and I was able now to expand the partition by that 250M. >>>>>>> The rest of the commands succeeded and then I ran Windows Update >>>>>>> and it succeeded also.
So I'm happy that my system has a larger Recovery now. I
probably should have shoved it 500M, but... It's at 881M now.
I have to admit, I'm thoroughly confused now.
I have a bunch of messages in this thread saved, but is there any
chance you could post the message ID of the one that had the
instructions you followed to get yours working? It would be much >>>>>> appreciated!
Thanks AL!
shrink fails, then just exit and reagentc /enable.
No harm done. That was my issue. The os would not shrink, no room
at the end. I ran Paul's jkdefrag, Mydefrag, and saw the files at
the end stopping the shrink. They were the files I could move /
delete etc.
Then I could restart the process.
Fortunately, I had lots of space on that drive and partition and did
not have this problem.
I did solve the update problem on this system using Paul's explanation
of basically the same link Al provided. One of the commands was not
quite the right syntax, but help provided the full correct one, and it
worked. Don't know why that was.
I shrank the C: partition by 1000mb and built a new WinRE partition by
the same 1000 mb. Now the total of my RE partition is 1527MB or 1.49
GB. After completing everything on the MS link, I ran updates again
and it installed immediately. I then did another macrium image and
deleted the old one. As far as I'm concerned that should be the end
of it for now!
Checked the wife's laptop and it has a 15G RE partition (don't know
why it's that big) and had successfully installed the update.
Checked my newest system that is about 2 years old and has an SSD
drive, and it hadn't been offered it yet. Upon checking it downloaded
it and it too failed. Checked the size of the MR partition and it too
is only about 600MB with less than 80MB free. So, after sending this,
it's down to that computer to do it all on that one too. At least I'm
not so intimidated now. Now I am not a total newbie on computers, but
certainly not a guru of any sorts, but I still can't think of any of
the people I know who could do this. They wouldn't even try. This
all doesn't seem acceptable to me.
Much thanks to everyone, especially Big Al, Paul and Winston!
OEM' place a recovery partition normally at the end of the disk which is
used to restore the device to as-shipped factory condition.
 - the successful update didn't use or touch that 15 GB partition.
Open a Command prompt with admin privileges
At the prompt, enter the following then press the return key.
 reagentc /info
The result will show the real active WinRe partition # and the disk # on which it resides.
reset-to-factory-condition Recovery partition(which also includes the
WinRE partition) at the beginning of the disk.
- This device could also be a pre-Win10 device(originally built with Win
7, or 8x). Many of those pre-Win10 devices were built like this by the
OEM's.
MBR guidelines for partitioning are shown in this MSFT article <https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-biosmbr-based-hard-drive-partitions?>
On 1/17/24 10:48 PM, ...w¡ñ§±¤ñ wrote:
<snip>
reset-to-factory-condition Recovery partition(which also includes the WinRE partition) at the beginning of the disk.Interesting that the article says the system will grow the WinRE partition as needed and take from the Windows partition.  Contrary to the 4441 update that won't grow the partition.  Seems one hand isn't following the other at Microsoft.
- This device could also be a pre-Win10 device(originally built with Win 7, or 8x). Many of those pre-Win10 devices were built like this by the OEM's.
MBR guidelines for partitioning are shown in this MSFT article
<https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-biosmbr-based-hard-drive-partitions?>
On 1/18/2024 8:03 AM, Big Al wrote:Yes, I don't like doing 6 operations at once.
On 1/17/24 10:48 PM, ...w¡ñ§±¤ñ wrote:
<snip>
reset-to-factory-condition Recovery partition(which also includes the WinRE partition) at the beginning of the disk.Interesting that the article says the system will grow the WinRE partition as needed and take from the Windows partition.  Contrary to the 4441 update that won't grow the partition.  Seems one hand isn't following the other at Microsoft.
- This device could also be a pre-Win10 device(originally built with Win 7, or 8x). Many of those pre-Win10 devices were built like this by the OEM's.
MBR guidelines for partitioning are shown in this MSFT article
<https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/configure-biosmbr-based-hard-drive-partitions?>
There's a subtle distinction there. The previously seen mechanism, works like this.
I don't really think of this as "growing a partition", rather "creating
a new partition which is a bit bigger".
+-----+----------------------------------+----------+
| MBR | Win10 C: | Recovery | +-----+----------------------------------+----------+
+-----+-----------------------+ - - - - -+----------+
| MBR | Win10 C: (shrink) | | Recovery | +-----+-----------------------+ - - - - -+----------+
+-----+-----------------------+----------+----------+
| MBR | Win10 C: (shrink) | Recovery | Recovery | +-----+-----------------------+----------+----------+
^ ^ ^ ^ No longer
WinRE.wim needed
Microsoft doesn't know how to do the following. They refuse to
"dd" the partition to change the origin. Then expand it.
It should be quite safe, since the partition has no
drive letter typically and is not being accessed except
by their own code. You could move the partition by
block transfer, then do an expand to make it the desired
1GB or whatever. (shrink C: , move Recovery left, expand Recovery)
+-----+-------------------------------+-------------+
| MBR | Win10 C: | Recovery1GB | +-----+-------------------------------+-------------+
When I did that from Linux, gparted chose to move that
partition using "dd" (to the left), rather than another method.
After it was moved to the left, I did a resize in gparted,
to finish the operation. I did not select move/resize and
do both in the same operation. But I could have done it
that way.
Paul
 - In this latest case, patching for security and updating Win10
including its WinRE partitoin, there is insuffficient space to
start/finish the process(install the update, shrink Winodws(C:), update
WinRE partition files. Additionally, the part of the process that
shrinks the Windows partition may fall because, system files(e.g. System Restore Points or other Windows protected files) reside on the end of
the Windows partition) prevent the shrinking.
I still see this and no fix with today's automatic monthly updates. It
still has the manual technical script instructions to fix it.
On 2/13/2024 2:00 PM, Ant wrote:
I still see this and no fix with today's automatic monthly updates. It still has the manual technical script instructions to fix it.
I've seen you post on this several times. At this point, it's probably
not going to fix it unless YOU try something. Have you tried following
the instructions, making your windows partition smaller, and increasing
the sizer of your ReAgent partition bigger?
Winston, Paul, and others have been very helpful in assisting me fix
this issue on several systems. In the message below, Winston details
removing restore points because of the location they get put on the
disk. Perhaps that might help you.
Message ID: news://news.eternal-september.org:119/uq1o6i$1ra1s$1@dont-email.me
sticks <wolverine01@charter.net> wrote:
On 2/13/2024 2:00 PM, Ant wrote:
I still see this and no fix with today's automatic monthly updates. It
still has the manual technical script instructions to fix it.
I've seen you post on this several times. At this point, it's probably
not going to fix it unless YOU try something. Have you tried following
the instructions, making your windows partition smaller, and increasing
the sizer of your ReAgent partition bigger?
Winston, Paul, and others have been very helpful in assisting me fix
this issue on several systems. In the message below, Winston details
removing restore points because of the location they get put on the
disk. Perhaps that might help you.
Message ID:
news://news.eternal-september.org:119/uq1o6i$1ra1s$1@dont-email.me
Try telling non-technical users like elders. :P
sticks <wolverine01@charter.net> wrote:
On 2/13/2024 2:00 PM, Ant wrote:
I still see this and no fix with today's automatic monthly updates. It
still has the manual technical script instructions to fix it.
I've seen you post on this several times. At this point, it's probably
not going to fix it unless YOU try something. Have you tried following
the instructions, making your windows partition smaller, and increasing
the sizer of your ReAgent partition bigger?
Winston, Paul, and others have been very helpful in assisting me fix
this issue on several systems. In the message below, Winston details
removing restore points because of the location they get put on the
disk. Perhaps that might help you.
Message ID:
news://news.eternal-september.org:119/uq1o6i$1ra1s$1@dont-email.me
Try telling non-technical users like elders. :P
I still see this and no fix with today's automatic monthly updates. It
still has the manual technical script instructions to fix it. :(
I still see this and no fix with today's automatic monthly updates. It
still has the manual technical script instructions to fix it. :(
On Wed, 14 Feb 2024 02:05:56 -0500, Paul <nospam@needed.invalid> wrote:
If a partition won't shrink, yes, you can defeat it. I used
a Macrium CD, a backup and restore of C:, to squeeze it down.
I would just spend a minute or two and use a partition manager. ;-)
I know, I know, you've got a toolbox full of tools and they get offended if you
don't take them out and exercise them from time to time.
If a partition won't shrink, yes, you can defeat it. I used
a Macrium CD, a backup and restore of C:, to squeeze it down.
*From:* Philip Herlihy <PhillipHerlihy@SlashDevNull.invalid>
*Date:* Wed, 14 Feb 2024 13:03:58 -0000
In article <QWidneGTaZz0V1b4nZ2dnZfqnPudnZ2d@earthlink.com>, Ant
wrote...
I still see this and no fix with today's automatic monthly
updates. It still has the manual technical script instructions to
fix it. :(
The "Accepted Answer" here did work for me. It's easy enough - but
it would also be quite easy to do some real damage if you don't
follow the instructions really carefully.
https://learn.microsoft.com/en-us/answers/questions/1495451/windows- update-issue-(failed-to-install)-0x8007064
On 2/14/2024 11:35 AM, Char Jackson wrote:
On Wed, 14 Feb 2024 02:05:56 -0500, Paul <nospam@needed.invalid> wrote:
If a partition won't shrink, yes, you can defeat it. I used
a Macrium CD, a backup and restore of C:, to squeeze it down.
I would just spend a minute or two and use a partition manager. ;-)
I know, I know, you've got a toolbox full of tools and they get offended if you
don't take them out and exercise them from time to time.
Realistically though, do you have a Partition Manager For All Occasions ?
In article <QWidneGTaZz0V1b4nZ2dnZfqnPudnZ2d@earthlink.com>, Ant wrote...
I still see this and no fix with today's automatic monthly updates. It still has the manual technical script instructions to fix it. :(
The "Accepted Answer" here did work for me. It's easy enough - but it would also be quite easy to do some real damage if you don't follow the instructions
really carefully.
https://learn.microsoft.com/en-us/answers/questions/1495451/windows-update- issue-(failed-to-install)-0x8007064
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 297 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 06:50:15 |
| Calls: | 6,666 |
| Files: | 12,213 |
| Messages: | 5,336,029 |
