Win 10 Host Refresh: KB5034441 Error 0x80070643

Bournesup

Member
I received this error on Jan 9 when I did a host refresh; The error indicates a net framework error. However, this update is not part of the download when you check for online updates; My version of windows is win1022H2
 
KB5034441 is the BitLocker security fix for WinRE. Error 0x80070643 is ERROR_INSTALL_FAILURE.

I would save the NTLite.log & NTLite_dism.log for nuhi.
 
Do you have a Recovery partition? There are reports that Jan 2023 CU is causing issues, because it needs a bigger Recovery partition to fit WinRE. Normally it would automatically resize it, but if your Recovery partition is placed in front of System – it can't grow.
 
Yes, I have read those same reports. Some say the partition needs to be at least 500MB. The recovery partition on my computer is 530 MB.

The layout looks like this;
C: OS; 250GB
disk 0 partition 1; EFI system partition; Capacity 100MB Free 100MB
disk 0 partition 4; Recovery Partition; Capacity 530MB Free 530MB

What makes it interesting is that the update (Kb5034441) is downloaded after a fresh install with the Jan 2023 integrated into the setup.
Yes, I did both, a host refresh and fresh install and got the same results.

Yes, my drive is partition, but on a fresh install I delete the partitions relating to windows O/S and it is now unallocated space and I install windows to that space. Thus, all the partitiions are size accordingly.
 
Last edited:
I solved the problem by decreasing the O/S partition by 250MB and increased the recovery partition by 250MB, But really that should be included in the latest CU by microsoft
 
Starting with June 2023, CU is always patching Recovery Partition (mostly to enforce BitLocker security updates). I hear some experts suggesting a 750MB-1GB default partition size to account for future growth.

/shrug
 
Starting with June 2023, CU is always patching Recovery Partition (mostly to enforce BitLocker security updates). I hear some experts suggesting a 750MB-1GB default partition size to account for future growth.

/shrug
is it possible to set only the recovery partition size using the disk partition configuration tool from ntlite?, so i can avoid this problem with the update KB5034441 not being able to install with the auto generated 500mb partition. my idea is that the instalation process generates, the default 100mb boot partition, then creates a 1gb recovery partition, then use the rest of the space as the C: drive
 
Using the Disk Template, you can assign 1024 MB as the Recovery partition's size. The problem is the template is restricted by Setup's limitation that any extended partition (normally Windows) must be the last partition on the disk. If you can't use extend volume for sizing, then you must know the entire disk size in advance.

This traps the Recovery partition to being assigned in front of Windows, and no easy opportunity for growing it once it's in production.

Another solution is you can assign 0 MB to the Recovery partition, which NTLite interprets as you don't want one. Setup will install Windows without Recovery, and it's possible to run a Post-Setup sequence to shrink Windows volume with diskpart, and execute "reagentc /enable" to recreate the missing Recovery in the new space.
 
I'm working a new script to rewrite any unattend file, and insert two WinPE commands to correctly diskpart the drive using the "modern" layout. This avoids the need to modify boot.wim, and the only parameter would be the shrink size.

Source commands:
Code:
select disk 0
clean
convert gpt
create partition efi size=100
format quick fs=fat32
create partition msr size=16
create partition primary
shrink minimum=1024
format quick fs=ntfs
create partition primary
format quick fs=ntfs
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001

For those experts who understand unattend files, you can copy these XML blocks:
Code:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ImageInstall>
                <OSImage>
                    <InstallTo>
                        <DiskID>0</DiskID>
                        <PartitionID>3</PartitionID>
                    </InstallTo>
                </OSImage>
            </ImageInstall>
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>cmd /c @echo off &amp; (echo sel disk 0&amp;echo cle&amp;echo con gpt&amp;echo cre par efi size=100&amp;echo for quick fs=fat32&amp;echo cre par msr size=16&amp;echo cre par pri&amp;echo shr minimum=1024&amp;echo for quick fs=ntfs) &gt; X:\UEFI.txt</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Order>2</Order>
                    <Path>cmd /c @echo off &amp; (echo cre par pri&amp;echo for quick fs=ntfs&amp;echo set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"&amp;echo gpt attributes=0x8000000000000001&amp;echo exit) &gt;&gt; X:\UEFI.txt &amp; diskpart /s X:\UEFI.txt</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
            <UserData>
                <ProductKey>
                    <Key></Key>
                </ProductKey>
            </UserData>
        </component>
    </settings>
</unattend>
 
Back
Top