Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Author Topic: Jan 2014 updates failing  (Read 2830 times)

jelv

  • Helpful
  • Kitizen
  • *
  • Posts: 2054
Jan 2014 updates failing
« on: January 10, 2024, 07:00:30 PM »

Many users are seeing KB5034441: Windows Recovery Environment update for Windows 10, version 21H2 and 22H2: January 9, 2024  fail with error 0x80070643.

https://www.bleepingcomputer.com/news/microsoft/windows-10-kb5034441-security-update-fails-with-0x80070643-errors/ has an explanation:

Quote
WinRE partition too small

When installing the KB5034441 security update, Microsoft is installing a new version of the Windows Recovery Environment (WinRE) that fixes the BitLocker vulnerability.

Unfortunately, Windows 10 creates a recovery partition, usually around 500 MB, which is not large enough to support the new Windows RE image (winre.wim) file, causing the 0x80070643 error when attempting to install the update.

The procedure given in that page worked for me.

Logged
Broadband and Line rental: Zen Unlimited Fibre 2, Mobile: Vodaphone
Router: Fritz!Box 7530

banger

  • Kitizen
  • ****
  • Posts: 1186
  • TTB 80/20
Re: Jan 2014 updates failing
« Reply #1 on: January 10, 2024, 10:24:47 PM »

Think I will wait.  :cool:
Logged
Tim
talktalkbusiness.net & freenetname
Asus RT-AC68U and ZyXEL VMG1312-B10A Bridge on 80 Meg TTB Fibre

https://www.thinkbroadband.com/speedtest/1502566996147131655

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7388
  • VM Gig1 - AAISP L2TP
Re: Jan 2014 updates failing
« Reply #2 on: January 11, 2024, 03:08:20 PM »

I got a feeling this update will get pulled, pretty crazy they expecting their user base to manually configure boot partitions.

If it doesnt get pulled before my 10 day delay detects the update, I will probably hide it, not worth the hassle as I am not using bitlocker.
Logged

jelv

  • Helpful
  • Kitizen
  • *
  • Posts: 2054
Re: Jan 2014 updates failing
« Reply #3 on: January 21, 2024, 12:21:15 PM »

Although it was a patch to bit locker that caused a failure in this case, isn't it likely that patches to other components are going to run in to the same issue in the future?
Logged
Broadband and Line rental: Zen Unlimited Fibre 2, Mobile: Vodaphone
Router: Fritz!Box 7530

Alex Atkin UK

  • Addicted Kitizen
  • *****
  • Posts: 5272
    • Thinkbroadband Quality Monitors
Re: Jan 2014 updates failing
« Reply #4 on: January 21, 2024, 02:55:44 PM »

I'd imagine so, particularly as any time it tries to update the recovery its going to include this patch so it may block all updates.
Logged
Broadband: Zen Full Fibre 900 + Three 5G Routers: pfSense (Intel N100) + Huawei CPE Pro 2 H122-373 WiFi: Zyxel NWA210AX
Switches: Netgear MS510TXUP, Netgear MS510TXPP, Netgear GS110EMX My Broadband History & Ping Monitors

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7388
  • VM Gig1 - AAISP L2TP
Re: Jan 2014 updates failing
« Reply #5 on: January 23, 2024, 07:04:16 PM »

Although it was a patch to bit locker that caused a failure in this case, isn't it likely that patches to other components are going to run in to the same issue in the future?

Only if this gets moved inside a CU, this current update is separate so wont affect other updates.  New builds of windows will almost certainly have it baked in (on clean installs) so a larger default recovery partition.

I think its unlikely this will go into a CU, as the failure rate for the update is likely to be very high, and it would be a disaster for Microsoft if entire CU's were failing.

Microsoft have now at least released a powershell script which automatically adjusts the partitioning.  Although its still not an automated thing in the update.
« Last Edit: January 23, 2024, 07:07:18 PM by Chrysalis »
Logged
 

anything