* * Mod note on 1/12/24. * * Please see: https://www.yourwindowsguide.com/2024/01/fix-error-0x80070643-for-windows-10-kb5034441-update.html The latest update downloads and then fails to install. OS Build # 19045.3930. Update Troubleshoot tool repair but it does not help. MS Windows Update Catalog does not have the update. Other updates all went through without any trouble. This is a brand new update. Is this a known issue? Is there a resolution specific to this update? (Please do not copy and paste standard procedure)

No se actualiza la KB5034441, por error (0x80070643). Ayuda por favor.

Yeah - this tripped me up too. Turns out that when you follow their instructions, the quick format re-assigns the partition ID. Since I'm using MBR, the quick format changed it from 27 (recovery partition) to 07 (ntfs partition). Because of this, reagentc couldn't find it - and I couldn't point it at the new partition either. I had to use DISKPART to set the ID back to 27 after I quick formatted it. I imagine you'd have to do something similar if your drive is GPT, but I can't test it. After that, reagentc worked properly, the update installed correctly, and my system has been fine.

I didn't had to. I didn't resize it even, it was 2GB+ by default. C:\WINDOWS\system32>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk2\partition1\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: 6cd92040-3fa9-11ea-a053-ce4b053997f7 Recovery image location: Recovery image index: 0 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. Details for image : \?\GLOBALROOT\device\harddisk2\partition1\Recovery\WindowsRE\winre.wim Index : 1 Name : Microsoft Windows Recovery Environment (x64) Description : Microsoft Windows Recovery Environment (x64) Size : 2,347,976,762 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 : 3614 Files : 17575 Created : 07-Dec-19 - 9:11:48 Modified : 12-Aug-20 - 3:21:21 Languages : en-US (Default)

At least this method actually works and the update was successful afterwards. But come on MS, do people really should use diskpart for just an update...

Windows 10 22h2 security update [KB5034441] fails to install with code: 0x80070643

Anonymous

* * Mod note on 1/12/24. * *

Please see: https://www.yourwindowsguide.com/2024/01/fix-error-0x80070643-for-windows-10-kb5034441-update.html

The latest update downloads and then fails to install.

OS Build # 19045.3930.
Update Troubleshoot tool repair but it does not help.
MS Windows Update Catalog does not have the update.
Other updates all went through without any trouble.

This is a brand new update. Is this a known issue? Is there a resolution specific to this update? (Please do not copy and paste standard procedure)

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.

0 comments

194 answers

Anonymous

2024-01-11T12:56:04+00:00

No se actualiza la KB5034441, por error (0x80070643). Ayuda por favor.
Was this answer helpful?

0 comments No comments
Anonymous

2024-01-11T12:48:22+00:00

Yeah - this tripped me up too. Turns out that when you follow their instructions, the quick format re-assigns the partition ID. Since I'm using MBR, the quick format changed it from 27 (recovery partition) to 07 (ntfs partition). Because of this, reagentc couldn't find it - and I couldn't point it at the new partition either.

I had to use DISKPART to set the ID back to 27 after I quick formatted it. I imagine you'd have to do something similar if your drive is GPT, but I can't test it. After that, reagentc worked properly, the update installed correctly, and my system has been fine.
Was this answer helpful?

0 comments No comments
Anonymous

2024-01-11T12:46:35+00:00
I didn't had to.
I didn't resize it even, it was 2GB+ by default.

C:\WINDOWS\system32>reagentc /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:
```
Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk2\partition1\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: 6cd92040-3fa9-11ea-a053-ce4b053997f7 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0 
```
REAGENTC.EXE: Operation Successful.

Details for image : \?\GLOBALROOT\device\harddisk2\partition1\Recovery\WindowsRE\winre.wim

Index : 1

Name : Microsoft Windows Recovery Environment (x64)

Description : Microsoft Windows Recovery Environment (x64)

Size : 2,347,976,762 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 : 3614

Files : 17575

Created : 07-Dec-19 - 9:11:48

Modified : 12-Aug-20 - 3:21:21

Languages :

en-US (Default)
Was this answer helpful?

0 comments No comments
Anonymous

2024-01-11T12:46:01+00:00

At least this method actually works and the update was successful afterwards. But come on MS, do people really should use diskpart for just an update...
Was this answer helpful?

0 comments No comments
Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more