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

NICK ADSL UK said:

i am seeing on my travels far and wide that the update in question has been pulled. Hopefully, someone here in this forum may be able to confirm that

I don't think it has been pulled. It's still being offered on my work computer every morning when an update check takes place, including this morning. There is a record of a failed attempt in my update history for every day I've worked since it was released. I've hidden it on my own machines, but unfortunately don't have the privileges required to do so on my work desktop. I've alerted our IT dept. Their prob, not mine. :)

I was playing with it again on the Lenovo laptop showing a person what to expect and somehow it worked this time. Why it worked this time and not before is beyond me. When I retried it on the two HP Mini desktops, it still failed. The only difference in the Recovery partition size between the Lenovo and HPs is that the Lenovo laptop has a 1GB Recovery partition while the HPs have a 980mb partition size. So possibly 1GB is the magic number for the size of the Recovery partition. I will bone up on how to extend the Recovery partition on the HPs to 1.5GB (just to play safe) and see what happens. When I listed the info on the Lenovo Recovery partition using MiniTool Partition Wizard, it only shows that the "marker" was updated. Not sure if that is correct.

JohnD

@johnpd
The screenshot doesn't show or prove anything at all.
In posts #282 and #286 I listed the commands to verify the update
There is no magic number for the partition size!

Pentagon said:

@johnpd
The screenshot doesn't show or prove anything at all.
In posts #282 and #286 I listed the commands to verify the update
There is no magic number for the partition size!

Pentagon said:

@johnpd
...
In the registry
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
you should find: "WinREVersion"="10.0.19041.3920"
it's the last entry on the right side.
If this is ok, you can replace/exchange the WinRE.wim in all other machines by this one.
...

For some reason, I have no value WinREVersion in the mentioned registry key, or anywhere else in the registry. However, "reagentc /info" says it's enabled and gives me the location of RE partition - the screen that has been posted here so many times.

Andy Roid said:

For some reason, I have no value WinREVersion in the mentioned registry key, or anywhere else in the registry. However, "reagentc /info" says it's enabled and gives me the location of RE partition - the screen that has been posted here so many times.

see my screenshot in post #234

command prompt (admin)
Dism /Get-ImageInfo /ImageFile:\\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim /index:1
(it is one command! if it is partition4 otherwise change the number)
Service Pack-Build: 3920

Powershell
PS C:\WINDOWS\system32> Get-Hotfix

Do you really run: Windows 10 Professional x64 Version 21H2
You should have Build: 19045.3930

Pentagon said:

Do you really run: Windows 10 Professional x64 Version 21H2
You should have Build: 19045.3930

I'm running 22H2 (OS Build 19045.3930). But what I get from the command is completely strange:

Code:

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

Deployment Image Servicing and Management tool
Version: 10.0.19041.3636

Details for image : \\?\GLOBALROOT\device\harddisk1\partition5\Recovery\WindowsRE\winre.wim

Index : 1
Name : Microsoft Windows Recovery Environment (x64)
Description : Microsoft Windows Recovery Environment (x64)
Size : 2,331,248,849 bytes
WIM Bootable : No
Architecture : x64
Hal : <undefined>
Version : 10.0.19041
ServicePack Build : 1
ServicePack Level : 0
Edition : WindowsPE
Installation : WindowsPE
ProductType : WinNT
ProductSuite :
System Root : WINDOWS
Directories : 3604
Files : 17530
Created : 12/7/2019 - 8:11:48 AM
Modified : 4/21/2021 - 3:23:11 PM
Languages :
        en-US (Default)
The operation completed successfully.

C:\WINDOWS\system32>

This is really very strange.