Windows 10 KB5034441 Security Update Fails With 0x80070643 Errors

Ldee said:

No it's not black
Attachment 405872

I see 100 MB partition in NTFS format, typically in a UEFI boot system this contains the BCD boot information and is formatted in FAT 32. just an observation.

3Bit said:

Best advice a great teacher always said to me: "keep it simple stupid".

From my own research and experience the problem appears to be that the recovery partition is too small.
Typically around 500 something megabytes it causes that problem.
It appears, that once again someone at a certain company was once again asleep at the helm...

Simplest correction is to boot an OS from an USB (I.e. Win10 or Strelec or the like) and enlarge the recovery partition size on drive C.
In my case I used AOMEI in a PE environment.
I increased my original 550 MB recovery partition to 1GB.
Thereafter the problem was gone.

@3Bit can you please illustrate the process as I have never used AOMEI in a PE Environment, I have installed AOMEI Partition Assistant


I have created Win 10 installation ready to execute via the creation tool as suggested by Pentagon.

- - - Updated - - -

3Bit said:

I see 100 MB partition in NTFS format, typically in a UEFI boot system this contains the BCD boot information and is formatted in FAT 32. just an observation.

Ok, what am I supposed to do here in this scenario?

- - - Updated - - -

Pentagon said:

OK, from 3 bit solutions back to 64 bit
Your next steps:
The Program 7z will be needed
Download Media Creation Tool from MS and create an ISO
Mount the ISO and run 7z as administrator

See the path in the picture

Attachment 405898

Copy the WinRe.wim from the mounted ISO to
C:\Recovery\WindowsRE

Verify like yesterday:

Code:

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

Show hidden files and folders must be enabled first

I have Download Media Creation Tool from MS and created an ISO waiting for 3Bit to respond before I proceed to your steps.

Pentagon said:

Yes, in your case it's the install.esd

So do I use the same process as is file extension .esd and change file extension highlighted in this code below to .esd or just run code as is:?

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

- - - Updated - - -

Ldee said:

So do I use the same process as is file extension .esd and change file extension highlighted in this code below to .esd or just run code as is:?

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

it's here:
...install.esd\#\Windows\System32\Recovery
Just continue with 7z and doubleclick on install.esd
and run 7z as admin!

Pentagon said:

it's here:
...install.esd\#\Windows\System32\Recovery
Just continue with 7z and doubleclick on install.esd
and run 7z as admin!

I have chosen to open file with 7z inside C:\ and herewith the result.



Those files on 7z where do they extract to ?

No, just doubleclick on |2| and continue
when you are there click on Copy in the ribbon like my 7z screenshot

Pentagon said:

No, just doubleclick on |2| and continue
when you are there click on COPY in the ribbon like my 7z screenshot

Ok I get what you mean

Now copied over the file date changed from 2010 to 2023 meaning its copied ok.

Yes and then navigate to:
C:\Recovery\WindowsRE
when it's done:

Code:

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