Absolutely "risking destroying the OS"
Couldn't agree more!
No way am I going to play "maybe" with production servers...
2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441) error (0x80070643) a known issue?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
I keep trying install this update yet it keeps failing. I already ran troubleshooter said it resolved the issue but the error persists. I also disabled my antivirus and tried again still did not work And I keep getting error (0x80070643) Is this a known issue? All the other updates installed fine without issue.
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.
163 answers
Sort by: Oldest
-
Anonymous
2024-01-10T13:45:42+00:00 -
Anonymous
2024-01-10T13:52:01+00:00 I thought I'm the only one having this kind of problem. This is my first time encountering this kind of issue with this gaming rig. Anyways, I hope Microsoft will come up with a solution.
-
Anonymous
2024-01-10T13:52:11+00:00 I genuinely hope a fix is pushed out soon because I am usually the type to get updates installed as quick as I can but this is the first time I had a issue like this and it's so annoying.
Microsoft needs to step in ASAP otherwise a large amount of their userbase is gonna remain effected and annoyed at them.
Depending on when this latest update issue (2024-01 Security Update for Windows 10 Version 22H2 for x64-based Systems (KB5034441) DOES get'resolved, I'm hoping that it will NOT effect future updates in January if it ISN'T resolved.
-
Anonymous
2024-01-10T14:18:07+00:00 This MS-BS occurs because probably you've chosen to decline micro-soft offer to use their cloud for backup your private stuff. In response they require a huge recovery partition so one will be persuaded to give up his private data to big bro. You know what? I'm used to XP and 7 when I've been resolving stuff through the back door and ignoring all their BS including "recommended" updates to protect me from bogey man. Obviously who the bogey man is ... If someone is eager to mess up his system partition and loose three hours to back up his machine I wish him luck and condoleances. I am returning to roots here. Old bad habits. Cheers.
-
Anonymous
2024-01-10T14:34:19+00:00 Hi Elise!
Your link is right one but that advise there is wrong. On my notebook (win10) with c: d: was 1 "winre" efter 2 patch try I got 3 st "win re" part , they had size about 400M, it's to little. So I used diskpart (if you need shrink do it with at least 2G), delete 3 old "win re" and create 1 win re = 2G size. and after that , patch update did work. Some people said that 1G is OK but I dont want to do the same work in the future.
The same work i did on my win2022 server ... with the size of 2G (win re) everything was OK after that job.
/Best Vlad