Thank you MS.
Security Update KB5034441 for Windows 10 Ver. 22H2 will not install.
Thank you so much Microsoft as you have started the New Year off with bang with this update failure below on the first patch Tuesday of the year:
Installation Failure: Windows failed to install the following update with error 0x8024200B: 2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441).
Tried multiple times to install this brick but no luck on my OMEN desktop and my wife's Envy laptop. So now what Microsoft?
Don
Windows for home | Windows 10 | Windows update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
170 answers
Sort by: Most helpful
-
Anonymous
2024-02-02T12:06:45+00:00 -
Anonymous
2024-02-02T09:12:22+00:00 Nope. Troubleshooter was a waste of time in this case. As to the 0x search suggestion, that process is far too complex (and tedious) for a now unskilled tech user like me. I shall wait until MS can repair the update so that its replacement makes the fixes they want me to make.
Far out folks the family has 3 PCs, the Windows 11 updates were broken for December and January - in place reinstall was necessary. Yuk.
Then this security update was broken on the two Windows 10 machines. Money I can't afford goes into my licences, and I do expect (against reality, often), my padding the revenue to issue in benefits to me!
-
Anonymous
2024-02-01T14:52:27+00:00 not instaled
-
Anonymous
2024-01-28T21:30:50+00:00 Another option for extending the RE partition is to use a 3rd party disk utility that allows you to "rearrange"/resize"/"create"/"delete" partitions, such as EaseUS Partition Manager.
It should be possible to see the RE partition, delete it, move the Windows installation partition to the start of the disk--careful not to overwrite the protected partitions--like the boot and the manufacturer's "clean install" to purchased state (if it exists)--and then create a partition that can then be configured as the RE partition.
Though I'd probably use the creation steps that Microsoft has outlined in KB5028997 now that the placement will put it at the end of the occupied section(s) of the drive. This placement still isn't the best scenario, because, if you find you have the room at the end of the drive and need to expand the Windows partition later you have to go through all of these steps again.
As of this point I've done three physical systems and one VM using the steps in KB5028997 successfully--but also very carefully/deliberately--and then successfully completed this **** update.
Don't know if ANY of this helps anyone, but I thought I'd "throw" it out there as a possible solution for moving/re-arranging/extending the RE partition.
IMHO, instead of making this something the end user has to be responsible for, Microsoft should be putting this into the update as a test and as necessary warning that the RE partition needs to be resized, ask the end user if they are okay with the change and if okayed doing the repartition, the restart and then the installation of the update. Don't leave the end user having to determine their mess and have to correct it.
-
Anonymous
2024-01-28T21:02:19+00:00 I ran diskpart and shrunk the the c: partition, followed the instructions for creating the new recovery partition. It worked fine for me, but I've been a Windows user for over 30 years with training in dos and older Windows versions on IBM and other major brand pcs and laptops. The field of pc makers and models is too diverse these days for the average home user to attempt this without having some idea of how partitions are setup on their system.