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

You have to download a new Windows Version. Media Creation Tool from MS or an ISO
The old one creates the same problems!
I thought that is clear.
Good luck!
Don't worry it works!

Ivan Petrov said:

Have no idea. Perhaps you want to try a clean install...
Attachment 406387Attachment 406388Attachment 406389

nooooooooooo are you kidding? 😊 just for that? Takes days to customise windows and stuff. PC runs very well overall and i am happy with it.

thanks for sharing tips anyway!

Mike100 said:

The first thing I did was run reagentc /disable. But I do not see the WinRE.wim file.
I did run "delete partition override" because everything says to do that. I did not delete the first partition per se because it's still there.

I did make an image of the C: drive which has Windows 10. I used AOMEI and can view the image & it does show the Recovery partition. I presume I can restore any partition. If not I can restore the whole C: drive.

Here's some screen shots. Please advise what to do.
Thanks

Attachment 406381

Attachment 406379

Attachment 406380

I don't see it necessary that you reinstall Windows. You can recover winre.wim from a Windows installing media, the more modern the better (newer version of winre.wim), with the free program 7zip, and put it and ReAgent.xml manually in C:\Windows\System32\Recovery. This will have the effect of a well done ReagentC /disable. I'd leave your ancient 528 MB partition unallocated or as data partition (for the latter option you need to give it some id that Idk as I don't have experience with GPT, although I've seen it somewhere, and possibly set it with attributes that Idk either; if in doubt, leave it unallocated), and create a new Recovery partition in the unallocated space that you've got to do at the end (with its id and attributes so that it's recognized as the Recovery partition and set it as hidden). I've seen suggested to reboot after this to let Windows "enterily" know where does it have the Recovery partition, it wouldn't hurt. I suggest hiding KB5034441 and doing a drive image backup at this exact point in case something goes wrong (if such thing did ocurred, you'd restore the full drive). Afterwards, do ReAgentC /enable, what will move winre.wim and an adapted version of ReAgent.xml from C:\Windows\System32\Recovery to the new 1 GB Recovery partition, and enable WinRE. Likely it won't be the latter version and KB5034441 would be attempted if you unhide it. This time it will have a 1 GB Recovery partition at its disposal, although it doesn't guarantee a successful update. But in the worst case, you'll have saved your Windows install.

-----------------------------------------------------------

As you've been said, your first screen here shows the error that deleted winre.wim. This is a deeper explain.

You entered "reagentc /disable" inside diskpart. The net result of this is that "reagentc /disable" was never run. When you enter an incorrect command in Diskpart, it doesn't always show an error message, sometimes a list of available Diskpart commands is shown instead.

"cmd.exe" is the so called "command prompt", where you enter commands as lines of text. Commands can be "internal" or "external". Examples of internal ones are DIR, CD and others that are caught and run by cmd.exe itself. Examples of external ones are XCOPY and EDIT, these are actual executable files (with extension .COM or .EXE) included in the OS for being run at the command prompt. Besides, there will be the executable and not executable files of your installed programs and of Windows.

30-35 years ago Microsoft OSs (MS-DOS) did only have command prompt so, despite being only text, it was highly developed, and was kept inside the new MS OSs, introduced in middle 90's, meant to be graphical. Diskpart, included first in Windows 2000, is the successor of the previous utility Fdisk.

"cmd.exe" works by the principle of "being in" a given folder (also called directory) at any time. The current folder/directory is shown in the prompt. In modern versions of Windows, it's frequently C:\Windows\System32 but it can be changed with the command CD (change directory). For instance:

C:\Windows\System32>cd \
C:\>cd windows
C:\Windows>cd sYstEm32
C:\Windows\System32>cd ..
C:\Windows>_

The command prompt keeps current folders for every drive with letter, and also a current drive that can be changed entering <letter>: . For instance:

C:\Windows>D:
D:\>cd "problem KB5034441"
D:\problem KB5034441>I really have this folder!
'I' is not recognized as an internal or external command,
operable program or batch file.

D:\problem KB5034441>C:
C:\Windows>D:
D:\problem KB5034441>_

If there had been a file called I.EXE I.COM or I.BAT in D:\problem KB5034441 (that needs the quotes when cd'ing to it b/c its name has several words), it would have been run when I entered that. The command prompt can run programs that are in the current drive letter and directory, or in one of a list of directories specified in a complicated manner, so that the command prompt can run the programs in those directories from any folder. DISKPART.EXE is one of those programs. Be wary that a program run from the command prompt can take control of the command prompt and change its rules. This is a typical first programming practice followed by a further one (the student has done the executables HW.EXE and SUMS.EXE):

D:\>HW
Hello world!

D:\>SUMS
Enter first summand:5
Enter second summand:7
The sum is:12

D:\>_

If the user, instead of numbers like 5 or 7, had entered a command like reagentc /disable, some kind of error or misunderstanding would have ocurred, but for sure the command reagentc /disable wouldn't have run.

DISKPART.EXE is a cmd.exe command like the above SUMS.EXE but, instead of treating with numbers, it treats with commands for disks and partitions and, instead of being run once and exitting by itself, it runs multiple commands in the same session, until the user exits from Diskpart to cmd.exe with the Diskpart command EXIT.

The fix for me is not to move anything, not to change anything and hide the update with Wushowhide
https://download.microsoft.com/downl...owhide.diagcab

And here is why
Windows 10 22H2 KB5034441 install error How to hide it using tool and why some install some do not - YouTube

camelia said:

The fix for me is not to move anything, not to change anything and hide the update with Wushowhide
https://download.microsoft.com/downl...owhide.diagcab

And here is why
Windows 10 22H2 KB5034441 install error How to hide it using tool and why some install some do not - YouTube

cheers, not bothered by now. One user was able to install it by disabling his bitlocker - he didn't say if he re-enabled it though. If that works that way, is a super easy "fix". I do use bitlocker and have it enabled.

gabgab said:

cheers, not bothered by now. One user was able to install it by disabling his bitlocker - he didn't say if he re-enabled it though. If that works that way, is a super easy "fix". I do use bitlocker and have it enabled.

Maybe you're interested in this KB5034441 Security Update for Windows 10 (21H2 and 22H2) - Jan. 9 , although you'd still have to have KB5034441 hidden, because the Dynamic Updates version of KB5034441, so called KB5034232, doesn't introduce any new entry in the WU list. It just injects the new winre.wim .

According to the MS link (I repeat it here https://support.microsoft.com/en-us/...5-7fc406910c10 ):

With the device started up into the running version of Windows installed on the device, the script will perform the following steps:

Mount the existing WinRE image (WINRE.WIM).

Update the WinRE image with the specified Safe OS Dynamic Update (Compatibility Update) package available from the Windows Update Catalog. We recommend that you use the latest Safe OS Dynamic Update available for the version of Windows installed on the device.

Unmount the WinRE image.

If the BitLocker TPM protector is present, reconfigures WinRE for BitLocker service.

Important This step is not present in most third-party scripts for applying updates to the WinRE image.

I'm not too knowledgeable in the PowerShell language, although its grammar is close to C or Java, and it has a function (2nd one defined) that seems to do different things depending on the different Bitlocker-TPM enabling states in which a device can be.

Hi Rooscoota

I agree that KB5034441 does not install without considerable effort which I do not recommend. But KB5001716 did install on your system as you can see from the History, but failed to install a second time. Now, just hide both updates, KB5034441 and the 2nd KB5001716, and you're "good to go"

Yoy can download the app to hide updates here.

Download wushowhide - MajorGeeks