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

Pentagon said:

@tecknot
1. assign drive letter
cmd (admin)
diskpart
sel disk 1
sel par 5
assign letter=R
exit
2. check directory cmd
dir R:\Recovery\WindowsRE /a /s
is there any file?

Here's what I got:

Pentagon said:

Run cmd bcdedit
and find your active bootpartition

I don't know what to look for or where to look:

PS C:\Windows\System32> bcdedit

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume7
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {36f35d2a-b97e-11ed-8c6f-ab7fe7c1dc20}
displayorder {current}
{36f35d2b-b97e-11ed-8c6f-ab7fe7c1dc20}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 11
locale en-US
inherit {bootloadersettings}
recoverysequence {36f35d34-b97e-11ed-8c6f-ab7fe7c1dc20}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {36f35d32-b97e-11ed-8c6f-ab7fe7c1dc20}
nx OptIn
bootmenupolicy Standard
hypervisorlaunchtype Auto

Windows Boot Loader
-------------------
identifier {36f35d2b-b97e-11ed-8c6f-ab7fe7c1dc20}
device partition=B:
path \WINDOWS\system32\winload.efi
description Windows 10
locale en-US
inherit {bootloadersettings}
recoverysequence {36f35d2c-b97e-11ed-8c6f-ab7fe7c1dc20}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=B:
systemroot \WINDOWS
resumeobject {36f35d2a-b97e-11ed-8c6f-ab7fe7c1dc20}
nx OptIn
bootmenupolicy Standard
PS C:\Windows\System32> reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
FirmwareBootDevice REG_SZ multi(0)disk(0)rdisk(1)partition(1)

Pentagon said:

If you lost your WinRE.wim you need an ISO. From there you can easily copy it to R:\... using 7z in admin mode

Can do. Thanks!

Kind regards,

tecknot

- - - Updated - - -

Looks like my response was posted before yours. Strange.

Kind regards,

tecknot

Ivan Petrov said:

@itsme1 or @Pentagon , can you please tell me why do I have an old service pack build - 3562 ??? Clean installed Windows 10 from MCT, KB5034441 also installed, even wanting to reinstall everyday so far and on 546 MB Recovery partition. How, eventually to update winre.wim from Windows installation created on USB stick? /the same which I used to install Windows few days ago/. Please step by step... Thank you guys.

I do not know, sorry.

I have already updated the recovery partition in the past, and I had gone to the Microsoft site to get this dism command where Microsoft explains in 2 3 lines of example how to know if the recovery partition has been updated. Well I never understood anything in the Microsoft example. It's still the same example currently I went there yesterday I still don't understand anything.

Ivan Petrov said:

Thanks! I also don't understand much of their language

You can try updating the recovery partition with the script and Safe OS Dynamic Update and see what the dism command produces.

Here it talks about the script and safe os, you need to find the tutorial: Microsoft working on a fix for Windows 10 0x80070643 errors

Pentagon said:

@tecknot
1. assign drive letter
cmd (admin)
diskpart
sel disk 1
sel par 5
assign letter=R
exit
2. check directory cmd
dir R:\Recovery\WindowsRE /a /s
is there any file?

Run cmd bcdedit
and find your active bootpartition
or run cmd
reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice

If you lost your WinRE.wim you need an ISO. From there you can easily copy it to R:\... using 7z in admin mode

I am hitting another low. I tried to copy the WinRE.wim from a fresh ISO, but there was no file to be found in the extracted ISO.
I redid the other commands in a elevated command prompt, but I got, "R:\Recovery\WindowsRE' is not recognized as an internal or external command,
operable program or batch file."

I found the boot partition, but I don't know if it is active:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume7
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {36f35d2a-b97e-11ed-8c6f-ab7fe7c1dc20}
displayorder {default}
{current}
toolsdisplayorder {memdiag}
timeout 30

Running reg query HKLM\SYSTEM\CurrentControlSet\Control /v FirmwareBootDevice gave me:
FirmwareBootDevice REG_SZ multi(0)disk(0)rdisk(1)partition(1)

I feel I'm at the end of my rope. I guess I will just wait until MS provides a fix.

Thanks for all your help Pentagon. I really appreciate it.

Kind regards,

tecknot

- - - Updated - - -

Pentagon said:

@tecknot
USE CMD (!) and not PowerShell
OK your boot partition is on disk 1 partition 1

So I suggest to delete the EFI Partition 6 and extend partition 5

Type cmd
diskpart
sel disk 1
sel par 6
set id="ebd0a0a2-b9e5-4433-87c0-68b6b72699c7"
delete partition override
sel par 5
extend
exit
This adds the 532 MB to your Recovery Partition.

I strongly recommend not to use drive letter B for WIN11

Win 10 ==> C
WIN 11 ==> D
Data ==> E
B: only for ESP-MOUNTING (The day will come when you are happy about that!)
Change your timeout from 30 to 3 or 5

I will give this a try and redo your previous commands.

Kind regards,

tecknot

Pentagon said:

@tecknot
"... but I got, "R:\Recovery\WindowsRE' is not recognized as an internal or external command,"

dir R:\Recovery\WindowsRE /a /s
use the right command!!!
Copy&paste is very easy!

Ok, got it. Sorry, but I was using copy and paste. Nonetheless, I got:

Pentagon said:

\sources\install.wim\#\Windows\System32\Recovery
copy Reagent.xml as well

EVERYTHING IS SO EASY!

Okay, I successfully found and copied "Reagent.xml," and "Wimre.wim" files. I pasted them into R:\Recovery\WindowsRE. I hope that is the correct destination.

Do I start from the beginning (post 174)?

Kind regards,

tecknot

Pentagon said:

@tecknot
Just check again
dir R:\Recovery\WindowsRE /a /s
The boot.sdi is already there

Edit:
Do I start from the beginning (post 174)? NO!
When ready boot into WIN10

Yes, both ReAgent.xml and Winre.wim files are there:


Rebooting into Windows 10.

Kind regards,

tecknot