Windows 10 users report seeing errors when attempting to install Microsoft's January patch.

When trying to install the KB5034441 security update for BitLocker, Windows 10 customers are encountering 0x80070643 problems.

[{"selector":"#anim-a5cd8234-fc11-4cb7-8e19-2210ec44e8bb [data-leaf-element=\"true\"]","keyframes":{"transform":["translate3d(21.874999829338595%, 0, 0)","translate3d(0%, 0, 0)"]},"delay":0,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"both"}] [{"selector":"#anim-7fcc92c1-1b61-4630-9c54-faf60666815e","keyframes":{"opacity":[0,1]},"delay":0,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}] [{"selector":"#anim-2f30f6a8-b12b-4c04-a211-d8a479a9d2a3","keyframes":{"transform":["translate3d(0px, 141.65713%, 0)","translate3d(0px, 0px, 0)"]},"delay":0,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}]

A security update (KB5034441) was made available yesterday as part of Microsoft's January 2024 Patch Tuesday.

[{"selector":"#anim-26446fe2-b251-4e3e-99a5-dcdc5bbe6c39 [data-leaf-element=\"true\"]","keyframes":{"transform":["translate3d(-34.179687404002955%, 0, 0)","translate3d(0%, 0, 0)"]},"delay":0,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"both"}] [{"selector":"#anim-4c9ba683-bd12-46d9-b222-4477a42fc6dc","keyframes":{"opacity":[0,1]},"delay":1,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}] [{"selector":"#anim-beaab936-65ab-497d-a1ba-83f79f3175cb","keyframes":{"transform":["translate3d(0px, 315.52442%, 0)","translate3d(0px, 0px, 0)"]},"delay":1,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}]

This update addresses CVE-2024-20666, a BitLocker encryption bypass that permits users to access encrypted data.

[{"selector":"#anim-c196359a-4c57-4260-bd9f-b1dd2ebb21e0 [data-leaf-element=\"true\"]","keyframes":{"transform":["translate3d(14.834091476175074%, 0, 0)","translate3d(0%, 0, 0)"]},"delay":0,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"both"}] [{"selector":"#anim-29d57c9c-d8f7-4a00-a028-52226d3a37de","keyframes":{"opacity":[0,1]},"delay":3,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}] [{"selector":"#anim-656d68de-ca9b-44ca-b7bf-03c723d61ce3","keyframes":{"transform":["translate3d(0px, 315.52442%, 0)","translate3d(0px, 0px, 0)"]},"delay":3,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}]

Unfortunately, Windows 10 customers are experiencing 0x80070643 issues and installation failures while trying to install this update.

[{"selector":"#anim-5ee4bbaa-ccaf-44fe-a178-b58443f05499 [data-leaf-element=\"true\"]","keyframes":{"transform":["translate3d(28.90624987200394%, 0, 0)","translate3d(0%, 0, 0)"]},"delay":0,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"both"}] [{"selector":"#anim-78439fd9-f55f-4a04-918d-69a3bcac539d","keyframes":{"opacity":[0,1]},"delay":4,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}] [{"selector":"#anim-91299976-7d9a-48bb-8e51-93b31c754a55","keyframes":{"transform":["translate3d(0px, 130.32818%, 0)","translate3d(0px, 0px, 0)"]},"delay":4,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}]

Users will see a Windows Update box after rebooting, informing them that an error occurred and advising them to try again later.

[{"selector":"#anim-636c144a-cd4d-4035-b374-9a452187ca9e [data-leaf-element=\"true\"]","keyframes":{"transform":["translate3d(31.249999886225726%, 0, 0)","translate3d(0%, 0, 0)"]},"delay":3,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"both"}] [{"selector":"#anim-b20d78b0-1eea-4c80-ad49-e157a002ba45","keyframes":{"opacity":[0,1]},"delay":7,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}] [{"selector":"#anim-eabb25fd-b78d-4abb-820e-5986465416e9","keyframes":{"transform":["translate3d(0px, 264.20250%, 0)","translate3d(0px, 0px, 0)"]},"delay":7,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}]

The "Windows Recovery Environment servicing failed, (CBS_E_INSUFFICIENT_DISK_SPACE)" message should ideally appear on users' screens as per the support bulletin

[{"selector":"#anim-7ba537b8-04b4-49ad-a0d4-f0c58fced65a [data-leaf-element=\"true\"]","keyframes":{"transform":["translate(-1.0658141036401503e-14%, 0%) scale(1.5)","translate(0%, 0%) scale(1)"]},"delay":0,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"forwards"}] [{"selector":"#anim-ef4f580a-f705-4c36-9204-1be085cd8293","keyframes":{"opacity":[0,1]},"delay":7,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}] [{"selector":"#anim-c5aba37f-25ca-4dff-b4d4-a1e211ea0bd8","keyframes":{"transform":["translate3d(0px, 119.11817%, 0)","translate3d(0px, 0px, 0)"]},"delay":7,"duration":600,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}]

Instead, the Windows Update displays the generic "0x80070643 - ERROR_INSTALL_FAILURE" error message due to a coding problem.

[{"selector":"#anim-07c1726d-3ee9-47f3-8182-dcb2e05d63d8 [data-leaf-element=\"true\"]","keyframes":{"transform":["translate3d(-28.90624987200394%, 0, 0)","translate3d(0%, 0, 0)"]},"delay":5,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"both"}] [{"selector":"#anim-be64aeaa-8afe-4bef-a036-085a9b4d91ab","keyframes":[{"offset":0,"transform":"translate3d(0, -177.30328%, 0)","easing":"cubic-bezier(.5, 0, 1, 1)"},{"offset":0.289999999999999980015985556747182272374629974365234375,"transform":"translate3d(0, 0%, 0)","easing":"cubic-bezier(0, 0, .5, 1)"},{"offset":0.450000000000000011102230246251565404236316680908203125,"transform":"translate3d(0, -49.857682336%, 0)","easing":"cubic-bezier(.5, 0, 1, 1)"},{"offset":0.60999999999999998667732370449812151491641998291015625,"transform":"translate3d(0, 0%, 0)","easing":"cubic-bezier(0, 0, .5, 1)"},{"offset":0.70999999999999996447286321199499070644378662109375,"transform":"translate3d(0, -16.950193568%, 0)","easing":"cubic-bezier(.5, 0, 1, 1)"},{"offset":0.8000000000000000444089209850062616169452667236328125,"transform":"translate3d(0, 0%, 0)","easing":"cubic-bezier(0, 0, .5, 1)"},{"offset":0.84999999999999997779553950749686919152736663818359375,"transform":"translate3d(0, -6.365187752000001%, 0)","easing":"cubic-bezier(.5, 0, 1, 1)"},{"offset":0.92000000000000003996802888650563545525074005126953125,"transform":"translate3d(0, 0%, 0)","easing":"cubic-bezier(0, 0, .5, 1)"},{"offset":0.95999999999999996447286321199499070644378662109375,"transform":"translate3d(0, -2.765931168%, 0)","easing":"cubic-bezier(.5, 0, 1, 1)"},{"offset":1,"transform":"translate3d(0, 0%, 0)","easing":"cubic-bezier(0, 0, .5, 1)"}],"delay":6,"duration":600,"fill":"both"}]

The recovery partition that Windows 10 produces, which is typically 500 MB in size, is insufficient to accommodate the new Windows RE image (winre.wim) file that the KB5034441 update creates.

[{"selector":"#anim-80e8c0e5-bbfa-4d81-95ac-6ba1ec8dd4c8 [data-leaf-element=\"true\"]","keyframes":{"transform":["translate(0%, 0%) scale(1.5)","translate(0%, 0%) scale(1)"]},"delay":6,"duration":1800,"easing":"cubic-bezier(.3,0,.55,1)","fill":"forwards"}] [{"selector":"#anim-d54368c0-42a7-425d-9f8f-1e89a2f6dfb7","keyframes":{"opacity":[0,1]},"delay":5,"duration":1000,"easing":"cubic-bezier(0.4, 0.4, 0.0, 1)","fill":"both"}]

KB5028997 Fix: steps for manually resizing your partition so that the WinRE upgrade can be installed

[{"selector":"#anim-d18ca27c-e8aa-4b4a-a2b2-1a0a97a4092b [data-leaf-element=\"true\"]","keyframes":{"transform":["translate(-1.4210854715202004e-14%, 0%) scale(1.5)","translate(0%, 0%) scale(1)"]},"delay":0,"duration":2000,"easing":"cubic-bezier(.3,0,.55,1)","fill":"forwards"}] [{"selector":"#anim-b1fcdecf-2930-4ec3-a4e4-3796a77dee66","keyframes":{"opacity":[0,1]},"delay":10,"duration":800,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}] [{"selector":"#anim-066a928e-ae0a-4d2b-9472-063360fb4b41","keyframes":{"transform":["translate3d(0px, 304.77676%, 0)","translate3d(0px, 0px, 0)"]},"delay":10,"duration":800,"easing":"cubic-bezier(0.2, 0.6, 0.0, 1)","fill":"both"}]