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:

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? :/
--
"Since the day we heard about you, we have not stopped praying for you and asking God to fill you with the knowledge of his will through all spiritual wisdom and understanding." --Colossians 1:9. So cold.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

On 1/9/2024 1:47 PM, 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:
>
> 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? :/
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.
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'
>> (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? :/
> 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.
> 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.

Big Al <BigAl@invalid.com> wrote:
> On 1/9/2024 4:42 PM, Big Al wrote:
> > On 1/9/2024 1:47 PM, 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:
> >>
> >> 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? :/
> > 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.
> > 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.

MS needs to do a better job with this update. It looks like pretty everyone is having this problematic update today. :(
--
"Since the day we heard about you, we have not stopped praying for you and asking God to fill you with the knowledge of his will through all spiritual wisdom and understanding." --Colossians 1:9. So cold.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

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:
> 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

On 1/9/24 09:02 PM, Paul wrote:
> On 1/9/2024 8:48 PM, Paul 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.
>>
>> 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.
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 all?
--
Linux Mint 21.2 Cinnamon
Al

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.

Big Al wrote on 1/9/24 8:41 PM:

> Your partition looks like it's 646M and mine is 641M, wonder why it's so
> small or why your update worked.
> Too many questions.

The size shown in Disk Management for the WinRE partiton is the full size
of the partition, it is not the partition's amount of used or free space.

On this device, the total size of the WinRE partition is 1 GB(1024 MB) as
shown in Disk Management. It has 824.63 MB used and 199.37 MB of free space.

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

On 1/9/2024 10:41 PM, Big Al wrote:

> Your partition looks like it's 646M and mine is 641M, wonder why it's so small or why your update worked.
> 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 all?

OK, I'm on the other computer now, and fresh carrot cake (Disk 33 Win10 x64 21H2) has been added.
This is an "intentionally behind" installation.

Because the machine was intentionally behind, I'm showing

KB5001716 2023-05 Update for Windows 10 Version 21H2 Download error - 0x80070643

So even an old update is showing that way. This means I'm slightly
unimpressed with how things are going, and what we know.

Whereas:

Feature update to Windows 10, version 22H2 is showing Downloading - 56%

It is going forward.

OK, 22H2 is in, and '4441 is showing the error 0x80070643

C:\$WinREAgent\Scratch\update.wim Originally showing 514MB, now shows 496,222,165 bytes (473MB)

DISM and friends, have been grinding out a new WinRE.wim .

And that I guess, won't fit in the partition 4.

C:\Windows\Logs\WinREAgent\setupact.log

2024-01-10 Info WinRE partition total space [533721088], free space [36130816], winre size [477367903], target WinRE size [496222165]
2024-01-10 Info Free space requirement: [54525952]

The partition just might be big enough, but it's
violating a "free space" requirement, if some cruft
needs to be stored near the WinRE.wim .

Now, I can try the recipe and see what happens.

OK, recipe works. REcovery Partition (4) now 759MB.

*******

winreUpdateInstaller.exe is running

The WinRE.wim fits and all seems OK. reagentc /info is normal and functional.
And the history of reagentc, you'd be surprised how many users have
a non-functional or busted setup. That's why they can't "make a recovery stick".

[Picture]

https://i.postimg.cc/Z5zxB0YN/Patch-Tuesday-works-after-resize-partition4.gif

Paul

On 1/10/2024 2:26 AM, George wrote:
> 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.
>

+1

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 rebooted once from other
>today's updates:

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 gives me 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.
--
John Hall
"Acting is merely the art of keeping a large group of people
from coughing."
Sir Ralph Richardson (1902-83)

Paul wrote on 1/10/24 2:44 AM:
>
> KB5001716 2023-05 Update for Windows 10 Version 2 > Download error - 0x80070643

Fyi....for clarity, Microsoft already knows the UI error classification
is incorrect(and misleading)
Not Download, but Installation error

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

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>

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

On 1/10/24 06:44 AM, ...w¡ñ§±¤ñ wrote:
> 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>
>
>
So now I'm totally confused.
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). ?
--
Linux Mint 21.2 Cinnamon
Al

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 rebooted once from other today's updates:
>
> 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 gives me 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.

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

On 1/10/24 08:21 AM, Big Al wrote:
> On 1/10/24 06:44 AM, ...w¡ñ§±¤ñ wrote:
>> 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>
>>
>>
> So now I'm totally confused.
> 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). ?
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.
Worked fine, after I opened my eyes and noted that I had an MBR and not GPT, couldn't figure out why the commands to
create the recovery partition didn't work. Duh!.
Update installed just fine after the new partition was created. I'll try my live system later.
--
Linux Mint 21.2 Cinnamon
Al

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 rebooted once from other today's updates:
>>
>> 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 gives me 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.
>
> 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¡ñ§±¤ñ

....w¡ñ§±¤ñ <winstonmvp@gmail.com> wrote:
> 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 rebooted once from other today's updates:
> >>
> >> 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 gives me 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.
> >
> > 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. :/
--
"My son, if sinners entice you, do not give in to them." --Proverbs 1:10. Dang brokeness, cold, life, etc.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org.
/ /\ /\ \ Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

On 1/10/2024 8:00 PM, Ant wrote:
> ...w¡ñ§±¤ñ <winstonmvp@gmail.com> wrote:
>> 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 rebooted once from other today's updates:
>>>>
>>>> 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 gives me 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.
>>>
>>> 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 have messed with all the partitions, at one time or another, and
some are easy, and some... are damn hard to access.

I'm sure those programmers who have returned from their Christmas
vacation, are raring to go on fixing the broken stuff.

"Oh, yeah. That hole we made, before Christmas. And you
say some of the customers fell into the hole ? I'm on it !!!
I will make a bigger hole, capable of holding more customers !!!"

One of the reason I make fun of those programmers, is they managed
to make *three* Recovery partitions next to my C: . The software
was making them after every Upgrade. It would look like this.

--------------+-----------------+---------------+-------------+
C: | Recovery #3 | Recovery #2 | Recovery #1 |
--------------+-----------------+---------------+-------------+

And then, what exactly is the user supposed to do ?

Each upgrade, would shrink a chunk off the end of C: and
create another Recovery. (Only one of them has the current
valid WinRE.wim in it.)

This is one of the benefits of GPT partitioning, you can just
keep doing that until the cows come home. GPT can have up
to 128 partitions.

One of the functions of "cleanmgr.exe" should be to remove the excess ones.
Once Windows.old is gone, then only one of those can be valid.

Paul

Paul wrote on 1/10/24 6:42 PM:
> On 1/10/2024 8:00 PM, Ant wrote:
>> ...w¡ñ§±¤ñ <winstonmvp@gmail.com> wrote:
>>> 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 rebooted once from other today's updates:
>>>>>
>>>>> 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 gives me 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.
>>>>
>>>> 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 have messed with all the partitions, at one time or another, and
> some are easy, and some... are damn hard to access.
>
> I'm sure those programmers who have returned from their Christmas
> vacation, are raring to go on fixing the broken stuff.
>
> "Oh, yeah. That hole we made, before Christmas. And you
> say some of the customers fell into the hole ? I'm on it !!!
> I will make a bigger hole, capable of holding more customers !!!"
>
> One of the reason I make fun of those programmers, is they managed
> to make *three* Recovery partitions next to my C: . The software
> was making them after every Upgrade. It would look like this.
>
> --------------+-----------------+---------------+-------------+
> C: | Recovery #3 | Recovery #2 | Recovery #1 |
> --------------+-----------------+---------------+-------------+
>
> And then, what exactly is the user supposed to do ?
>
> Each upgrade, would shrink a chunk off the end of C: and
> create another Recovery. (Only one of them has the current
> valid WinRE.wim in it.)
>
> This is one of the benefits of GPT partitioning, you can just
> keep doing that until the cows come home. GPT can have up
> to 128 partitions.
>
> One of the functions of "cleanmgr.exe" should be to remove the excess ones.
> Once Windows.old is gone, then only one of those can be valid.
>
> Paul
>
That's been around for some time - self induced, the OEM, and earlier by
MSFT(MCT installer download) where the Recovery partition was not placed
immediately after the Windows partition.

I agree, and why I mentioned the manual method is a 'nasty' approach to
resolution. It's a pita including those encountering the issue for those
in the SMB and Enterprise community. Enterprise doesn't like the idea or
having to tamper with hundreds, thousand of machines even when the
resolution may be to reimage devices during offline hours.

Just thinking out loud...have not ventured down this path...but maybe you
could comment.
Note: Not suggesting folks do it either :)

Could one just jump to diskpart in an admin console(Command or
Powershell), and using a diskpart script, select the disk, select the o/s
partition, shrink it so that it will free up enough space for a 1 GB
recovery partition, then create Windows RE as 1 GB etc.

Obviously one should inspect in advance and ensure they know the
operating system disk and its partition - for most its disk 0 but for
some devices with more than one disk, it could also be '1'. In an normal
GPT partitioned drive, the o/s is partition #3, Windows RE partition #4

One would need to verify the Windows RE partition status as enabled in an
elevated command prompt
reagentc /info

To make changes, after verifying Windows RE is enabled, one would then
disable it
reagentc /disable

As an example...For GPT using design intent partitioning order and with
the os on disk 0 as partition 3 and WinRE as partition #4 with an
existing size of 512 MB a script might look like this.

Note: IMPORTANT - The following is ***not intended for use***, it is only
for discussion sake!!!

rem---
rem Select os disk
sel disk 0
rem Select os partition
sel part 3
rem shrink os partition
shrink desired=512 minimum=512
rem Select Windows Recovery partition
sel part 4
rem Delete Windows Recovery partition
delete partition override
rem Create new Windows Recovery Partition
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes =0x8000000000000001
format quick fs=ntfs label="WinRE"
rem Exit Diskpart
exit

Once done, verify the WinRE partition is created and present by returning
to Diskpart

List vol
If created then exit diskpart using the 'exit' command

Re-enable WinRE
reagentc /enable
Verify the WinRE status and location
reagentc /info

Go back and install January 2024 latest update.

One final comment on the above script
One item may need additional parameters when used in a script, that are
not required when manually entering a command string via keyboard

The line(shown above)
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
- when using a script may need to include the ""
create partition primary id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"

or optionally(in the script)
the entire line could be two lines
create partition primary
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"

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

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
"Acting is merely the art of keeping a large group of people
from coughing."
Sir Ralph Richardson (1902-83)

On 1/11/2024 4: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.

That's also going to impact some backup programs.

If you were perhaps running Incremental Forever,
and the partition size changes.

Paul

On 1/11/24 04: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.
You'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
that update today.

WooHoo. Thanks for the notice. One less headache.
--
Linux Mint 21.2 Cinnamon
Al

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.

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