KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 Win Update

itsme1 · 20 Jan 2024

einstein1969 said:

Greetings,

I'm still freaking out about this update.

I read the post from user "swegmike" two pages back KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 and it seems to contain help on re-downloading the update to "winRE".

I had left the PC with the update done and the WinRe (presumably not updated) in the recovery partition (enlarged to 1.6GB)

and the last command had given me back

Code:

"C:\WINDOWS\system32>reagentc /info
Configuration information for Windows Recovery Environment
and resetting the system:

     Windows Recovery Environment Status: Enabled
     Windows Recovery Environment path: \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE
     Boot Configuration Data Identifier (BCD): 3dad1203-af32-11ee-98e2-a8b13b70166d
     Recovery image path:
     Recovery image index: 0
     Custom Image Path:
     Custom image index: 0

today I took the situation back into my hands to redo the update.

but when I gave the command I received this:

Code:

C:\WINDOWS\system32>reagentc /info
Configuration information for Windows Recovery Environment
and resetting the system:

     Windows Recovery Environment Status: Disabled
     Windows Recovery Environment Path:
     Boot Configuration Data Identifier (BCD): 3dad1203-af32-11ee-98e2-a8b13b70166d
     Recovery image path:
     Recovery image index: 0
     Custom Image Path:
     Custom image index: 0

REAGENTC.EXE: Operation successful."

then I gave a

Code:

C:\WINDOWS\system32>reagentc /enable
REAGENTC.EXE: Success.

And

Code:

C:\WINDOWS\system32>reagentc /info
Configuration information for Windows Recovery Environment
and resetting the system:

     Windows Recovery Environment Status: Disabled
     Windows Recovery Environment Path:
     Boot Configuration Data Identifier (BCD): 3dad1203-af32-11ee-98e2-a8b13b70166d
     Recovery image path:
     Recovery image index: 0
     Custom Image Path:
     Custom image index: 0

REAGENTC.EXE: Success.

but it returns that it is disabled
what did I miss?

also partition explorer has a winre of 750MB, does it have to be that big?

Attachment 403924

a little help....

How many disks and how many Windows installations do you have?

Take a screenshot of the Windows Partition Manager.

Bree · 20 Jan 2024

I've just done a clean install of Windows 10. It created a 530MB recovery partition which of course promptly failed to update with KB5034441. Shrank C: a little and expanded the recovery drive to 800GB, installed successfully now.

Wannagofast · 20 Jan 2024

Bree said:

I've just done a clean install of Windows 10. It created a 530MB recovery partition which of course promptly failed to update with KB5034441. Shrank C: a little and expanded the recovery drive to 800GB, installed successfully now.

Was it Pro or Home Edition? Did you use the most recent version of the Media Creation tool to create your installer? I just did a clean install on Monday and it created a 546MB recovery partition which installed everything just fine. I wonder what criteria is used to calculate how big the installer makes the recovery partition during the install.

peace
wanna

NICK ADSL UK · 20 Jan 2024

Wannagofast said:

Was it Pro or Home Edition? Did you use the most recent version of the Media Creation tool to create your installer? I just did a clean install on Monday and it created a 546MB recovery partition which installed everything just fine. I wonder what criteria is used to calculate how big the installer makes the recovery partition during the install.

peace
wanna

Same here, My workaround was to reinstall windows, keeping my documents and settings. This procedure is simple to undertake, as it realigns the hard drive recovery partition in which the update fault lies. I did that as soon as I posted the monthly update at 6pm UK time, as I get the updates by 7pm on my computer in the UK. a bit of an overkill, but that's the way things are sometime
sooner or later well all get cut off with a bad update, it's bound to happen

sometimes it's best to just keep it simple and a simple overwrite of the files is that. Although I'm sure for some that would fail but that again is computers nothing's perfect. :)

Bree · 20 Jan 2024

Wannagofast said:

Was it Pro or Home Edition? Did you use the most recent version of the Media Creation tool to create your installer? I just did a clean install on Monday and it created a 546MB recovery partition which installed everything just fine. I wonder what criteria is used to calculate how big the installer makes the recovery partition during the install.

It was Pro. No, it wasn't the latest one, the MCT now makes 22H2 19045.3803. It was the previous one, that was 22H2 build 19045.2965.

I see no pattern in how MS decides the size of the recovery partition, but I was installing to a Legacy/MBR machine with a 120GB SSD.

I've just downloaded the latest MCT and rebuilt my install media to 19045.3803, then repeated exactly the same clean install. This time it created a 554MB recovery partition, 24MB larger than before. This time round KB5034441 did install.

KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9-image.png

Andy Roid · 21 Jan 2024

einstein1969 said:

reagent.xml on C:\Windows\System32\Recovery>

....

on recovery partition:

Well, there are two things to notice. Both resumeobject values in bcdedit output are set to:

{40c54273-2774-11ed-ad6a-a749d813d476}

while recoverysequence is set to:

{3dad1203-af32-11ee-98e2-a8b13b70166d}

Note that this is equal to the WinreBCD id in both ReAgent.xml files. In my case resumeobject and recoverysequence have the same value.
Second thing, the first xml file in the system directory has value:

<InstallState state="0"/>

which would suggest it is not installed/enabled. The other xml (the one on the recovery partition) has value "1" and that would suggest it should be running. In my case this value is also "1" on a laptop where RE Environment is running and hotfix is installed.
The next thing I would try is to set recovery image path with:

reagentc /setreimage /path X:\Recovery\WindowsRE /target C:\Windows

where X: is the letter where the image is mounted, to connect your recovery environment to the GPT boot record. You can assign letter with diskpart by selecting partition and executing assign letter=X. Note that I'm not sure if:

/target C:\Windows

is really needed as I've seen examples with and without it. I can't be of more help, unfortunately.

Celery · 21 Jan 2024

Andy Roid said:

Note that I'm not sure if:

/target C:\Windows

is really needed as I've seen examples with and without it.

reagentc /setreimage /?

Sets the location of the custom Windows Recovery Environment (Windows RE) image.

REAGENTC.EXE /setreimage /path <dir_name> [/target <dir_name>] [/logpath <file_path>]

/path <dir_name> - Specifies the directory that contains the custom Windows RE image (winre.wim).
/target <dir_name> - Specifies the Windows installation. If this argument is not specified, the running operating system is used.
/logpath <file_path> - Specifies the path of log file. If this argument is not specified, the default path is Windows\Logs\Reagent\Reagent.log.

Example:
REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE /logpath C:\Temp\Reagent.log
REAGENTC.EXE /setreimage /path r:\Recovery\WindowsRE /target C:\Windows

Andy Roid · 21 Jan 2024

Celery said:

/target <dir_name> - Specifies the Windows installation. If this argument is not specified, the running operating system is used.

OK, I have only one Windows installation and it is in C:\Windows.
If I omit the target, it will use my running Windows. But if I specify /target option, then it will use C:\Windows, which happens to be the same installation.
So for computers with only one installation (big majority), does it make any difference whether /target is specified or not?

Celery · 21 Jan 2024

Andy Roid said:

So for computers with only one installation (big majority), does it make any difference whether /target is specified or not?

Then it doesn't matter if /target is specified or not.

By the way, I never use the /setreimage option.

I just use the following commands.

reagentc /info ---> "Windows RE status: Enabled"
reagentc /info ---> "Windows RE status: Disabled"

reagentc /disable ---> "Operation Successful"
reagentc /disable ---> "Windows RE is already disabled"

reagentc /enable ---> "Operation Successful"
reagentc /enable ---> "The Windows RE image was not found" X)

X) You don't have Winre.wim and ReAgent.xml under: C:\Windows\System32\Recovery

More info in the post below.

Windows Recovery Environment

topgundcp said:

You need not to mount/assign any letter to the Recovery partition. If for some reason it's broken. Make sure you have WinRe.wim and Reagent.xml (containing all 0's) under: C:\Windows\System32\Recovery
then type: reagentc /enable

- - - Updated - - -

[X]Show hidden files, folders, and drives
[ ]Hide protected operating system files (Recommended)

KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9-reagentc-disable.png

KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9-reagentc-enable.png

reagentc /enable ---> "The Windows RE image was not found"

KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9-windows-re-image-not-found.png

recovery partition

topgundcp said:

Copy WinRE.wim and the uninitialized ReAgent.xml files from the installation Media to C:\Windows\System32\Recovery

Mount the Installation ISO. If already mounted, under Sources folder, use 7-zip to open either install.esd or install.wim then navigate to Windows\system32\Recovery then copy both files.

NOTE: the install.esd or install.wim might contain multiple editions of Windows, just use any index.

From Admin command, run reagentc /enable. This will move WinRe.wim to the Recovery partition and set the GUID and location in ReAgent.xml

KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9-7-zip.png

einstein1969 · 21 Jan 2024

itsme1 said:

How many disks and how many Windows installations do you have?

Take a screenshot of the Windows Partition Manager.

only one disk , os partition + data partition (10GB)

KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9-image1.png

- - - Updated - - -

Andy Roid said:

Well, there are two things to notice. Both resumeobject values in bcdedit output are set to:

{40c54273-2774-11ed-ad6a-a749d813d476}

while recoverysequence is set to:

{3dad1203-af32-11ee-98e2-a8b13b70166d}

Note that this is equal to the WinreBCD id in both ReAgent.xml files. In my case resumeobject and recoverysequence have the same value.
Second thing, the first xml file in the system directory has value:

<InstallState state="0"/>

which would suggest it is not installed/enabled. The other xml (the one on the recovery partition) has value "1" and that would suggest it should be running. In my case this value is also "1" on a laptop where RE Environment is running and hotfix is installed.
The next thing I would try is to set recovery image path with:

reagentc /setreimage /path X:\Recovery\WindowsRE /target C:\Windows

where X: is the letter where the image is mounted, to connect your recovery environment to the GPT boot record. You can assign letter with diskpart by selecting partition and executing assign letter=X. Note that I'm not sure if:

/target C:\Windows

is really needed as I've seen examples with and without it. I can't be of more help, unfortunately.

If you read in my thread or in my post you see that I had already given that command and everything had worked but a few days later I found the situation messed up.

However this is the outcome of the command:

Code:

C:\Windows\System32\Recovery>dir E:\Recovery\WindowsRE /a
 Il volume nell'unità E non ha etichetta.
 Numero di serie del volume: BED7-2BC8

 Directory di E:\Recovery\WindowsRE

21/01/2024  21:00    <DIR>          .
21/01/2024  21:00    <DIR>          ..
07/12/2019  10:08         3.170.304 boot.sdi
21/01/2024  21:00             1.141 ReAgent.xml
16/10/2023  12:36       750.043.858 winre.wim
               3 File    753.215.303 byte
               2 Directory     945.065.984 byte disponibili

C:\Windows\System32\Recovery>reagentc /setreimage /path E:\Recovery\WindowsRE /target C:\Windows
REAGENTC.EXE: Ambiente ripristino Windows è già abilitato.


C:\Windows\System32\Recovery>reagentc /info
Informazioni di configurazione per Ambiente ripristino Windows
e la reimpostazione del sistema:

    Stato Ambiente ripristino Windows:      Enabled
    Percorso Ambiente ripristino Windows:   \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE
    Identificatore dati di configurazione di avvio (BCD): 3dad1209-af32-11ee-98e2-a8b13b70166d
    Percorso immagine di ripristino:
    Indice immagine di ripristino:          0
    Percorso immagine personalizzata:
    Indice immagine personalizzata:         0

REAGENTC.EXE: operazione riuscita.


C:\Windows\System32\Recovery>dir /a
 Il volume nell'unità C non ha etichetta.
 Numero di serie del volume: F4E5-CA6C

 Directory di C:\Windows\System32\Recovery

17/01/2024  00:44    <DIR>          .
17/01/2024  00:44    <DIR>          ..
21/01/2024  21:00             1.141 ReAgent.xml
08/08/2022  13:04             1.110 ReAgent_Merged.xml1
               2 File          2.251 byte
               2 Directory  59.177.574.400 byte disponibili

C:\Windows\System32\Recovery>reagentc /disable
REAGENTC.EXE: operazione riuscita.


C:\Windows\System32\Recovery>reagentc /info
Informazioni di configurazione per Ambiente ripristino Windows
e la reimpostazione del sistema:

    Stato Ambiente ripristino Windows:      Disabled
    Percorso Ambiente ripristino Windows:
    Identificatore dati di configurazione di avvio (BCD): 00000000-0000-0000-0000-000000000000
    Percorso immagine di ripristino:
    Indice immagine di ripristino:          0
    Percorso immagine personalizzata:
    Indice immagine personalizzata:         0

REAGENTC.EXE: operazione riuscita.


C:\Windows\System32\Recovery>dir /a
 Il volume nell'unità C non ha etichetta.
 Numero di serie del volume: F4E5-CA6C

 Directory di C:\Windows\System32\Recovery

17/01/2024  00:44    <DIR>          .
17/01/2024  00:44    <DIR>          ..
21/01/2024  21:02             1.110 ReAgent.xml
08/08/2022  13:04             1.110 ReAgent_Merged.xml1
               2 File          2.220 byte
               2 Directory  58.942.685.184 byte disponibili

C:\Windows\System32\Recovery>dir E:\Recovery\WindowsRE /a
 Il volume nell'unità E non ha etichetta.
 Numero di serie del volume: BED7-2BC8

 Directory di E:\Recovery\WindowsRE

21/01/2024  21:02    <DIR>          .
21/01/2024  21:02    <DIR>          ..
16/10/2023  12:36       750.043.858 winre.wim
               1 File    750.043.858 byte
               2 Directory     948.240.384 byte disponibili

C:\Windows\System32\Recovery>reagentc /enable
REAGENTC.EXE: operazione riuscita.


C:\Windows\System32\Recovery>reagentc /info
Informazioni di configurazione per Ambiente ripristino Windows
e la reimpostazione del sistema:

    Stato Ambiente ripristino Windows:      Enabled
    Percorso Ambiente ripristino Windows:   \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE
    Identificatore dati di configurazione di avvio (BCD): 3dad120b-af32-11ee-98e2-a8b13b70166d
    Percorso immagine di ripristino:
    Indice immagine di ripristino:          0
    Percorso immagine personalizzata:
    Indice immagine personalizzata:         0

REAGENTC.EXE: operazione riuscita.


C:\Windows\System32\Recovery>dir /a
 Il volume nell'unità C non ha etichetta.
 Numero di serie del volume: F4E5-CA6C

 Directory di C:\Windows\System32\Recovery

17/01/2024  00:44    <DIR>          .
17/01/2024  00:44    <DIR>          ..
21/01/2024  21:03             1.141 ReAgent.xml
08/08/2022  13:04             1.110 ReAgent_Merged.xml1
               2 File          2.251 byte
               2 Directory  58.911.604.736 byte disponibili

C:\Windows\System32\Recovery>dir E:\Recovery\WindowsRE /a
 Il volume nell'unità E non ha etichetta.
 Numero di serie del volume: BED7-2BC8

 Directory di E:\Recovery\WindowsRE

21/01/2024  21:03    <DIR>          .
21/01/2024  21:03    <DIR>          ..
07/12/2019  10:08         3.170.304 boot.sdi
21/01/2024  21:03             1.141 ReAgent.xml
16/10/2023  12:36       750.043.858 winre.wim
               3 File    753.215.303 byte
               2 Directory     945.065.984 byte disponibili

C:\Windows\System32\Recovery>

For scruple, I also tried to disable and rehabilitate. It seems to me that there is something wrong ...

- - - Updated - - -

Since the "Winre.wim" is a backup I must definitely update it.

While I wait for someone to give me the subsequent operations to do I have tried to see if it is updated but I need your advice to understand if the information is back.

Code:

C:\>ver

Microsoft Windows [Versione 10.0.19045.3930]

C:\>Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\winre.wim /index:1

Strumento Gestione e manutenzione immagini distribuzione
Versione: 10.0.19041.3636

Dettagli per l'immagine: \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\winre.wim

Indice: 1
Nome: Microsoft Windows Recovery Environment (x64)
Descrizione: Microsoft Windows Recovery Environment (x64)
Dimensioni: 3.056.489.637 byte
WIM avviabile: No
Architettura: x64
HAL: <non definite>
Versione: 10.0.19041
Build Service Pack: 3562
Livello Service Pack: 0
Edizione: WindowsPE
Installazione: WindowsPE
Tipo prodotto: WinNT
Famiglia di prodotti:
Radice sistema: WINDOWS
Directory: 3776
File: 17438
Data creazione: 07/12/2019 - 14:58:12
Data modifica: 16/10/2023 - 12:36:43
Lingue:
        it-IT (valore predefinito)
Operazione completata.

C:\>