• BitLocker-related update triggers install problems

    Home » Forums » Newsletter and Homepage topics » BitLocker-related update triggers install problems

    Author
    Topic
    #2627506

    PATCH WATCH By Susan Bradley January starts off the year with a bang, in the form of an install problem that may affect some of your Windows 10 PCs. F
    [See the full post at: BitLocker-related update triggers install problems]

    Susan Bradley Patch Lady/Prudent patcher

    8 users thanked author for this post.
    Viewing 11 reply threads
    Author
    Replies
    • #2627561

      In a consumer setting, where BitLocker is not in use and physical access to, and control of, the PC is in the user’s hands, this vulnerability is of extremely low risk.

      In fact, I’m willing to call it zero risk.

      Until a laptop gets stolen? —

      Over 2 million laptops are stolen every year in the United States.

      A laptop is stolen every 53 seconds in the United States.

      In the UK, 10,000 laptops are reported stolen every year.

      Laptop theft accounts for 57% of all identity theft.

      Must-Know Laptop Theft Statistics [Recent Analysis]

       

      In the case of my home Windows 10 PC, TPM is not supported; BitLocker could not be enabled, even if I tried.

      I have two home pcs that have NO TPM chip and thus no way to ever have bitlocker.

      It’s possible to use Bitlocker without a TPM:

      How to Turn on BitLocker Without TPM on Windows 10

      1 user thanked author for this post.
      • #2627604

        Sorry b, the risk of theft is not going to convince me that there is a need for Bitlocker in a home setting -and with this audience request to not have a Microsoft account-even more of a reason to not use Bitlocker .  The best way to do bitlocker is with a TPM chip -the very reason for Microsoft’s hardware mandate. Anything else is a klutzy substitute.  Sorry b this release was poorly thought out and released.

        Susan Bradley Patch Lady/Prudent patcher

        3 users thanked author for this post.
        • #2627640

          -and with this audience request to not have a Microsoft account-even more of a reason to not use Bitlocker .

          43% of your readers use Microsoft 365 and plenty more use OneDrive, Skype, Xbox etc., so most probably already have a Microsoft account.

          But Bitlocker does not require a Microsoft account anyway.

          The best way to do bitlocker is with a TPM chip -the very reason for Microsoft’s hardware mandate.

          Bitlocker is not the only use for a TPM (e.g. Passkeys), or even the primary reason for the requirement (i.e. Platform Integrity):

          The primary scope of TPM is to ensure the integrity of a platform. In this context, “integrity” means “behaves as intended”, and a “platform” is any computer device regardless of its operating system. This is to ensure that the boot process starts from a trusted combination of hardware and software, and continues until the operating system has fully booted and applications are running.

          TPM — Uses — Platform Integrity — Wikipedia

    • #2627603

      Susan Bradley wrote: In a consumer setting, where BitLocker is not in use and physical access to, and control of, the PC is in the user’s hands, this vulnerability is of extremely low risk. In fact, I’m willing to call it zero risk.

      Until a laptop gets stolen? —

      Susan said “where BitLocker is not in use” so, since this is a BitLocker fix, she’s correct. If a non-Bitlocker’d laptop is stolen, a BitLocker fix is not going to make the slightest difference.

      • #2627619

        Correct. But is it zero risk if someone skips the fix now and then decides to enable Bitlocker in six months time before travel with a laptop to guard against identity theft?

        • #2627714

          Nothing is zero risk. But it’s MY decision what risk(s) is(are) acceptable for ME. If MS takes it upon themselves to offer bitlocker or some other encryption, then they need to support it in a manner that’s accessible to their users. Of course that would apply to any “feature” they offer.

          1 user thanked author for this post.
    • #2627617

      I’ve read that this update requires 250MB free space in the RE partition.  I’ve just checked two different systems installed off the official Microsoft Windows 10 ISOs.  One was installed with 20H2 and the second was the latest 22H2 image.  Both have a recovery partition of approx 500MB with about 80-85MB free.

      What exactly is Microsoft thinking when their own ISOs didn’t create a large enough partition from the start?

    • #2627644

      There is not need to worry about resizing your Recovery Partition anymore.
      1.  You should just do nothing and wait. Microsoft will eventually fix the issue – probably next month.
      Or
      2. Microsoft has already released and alternative to resizing the partition – a simple patch:
      KB5034957: Updating the WinRE partition on deployed devices to address security vulnerabilities in CVE-2024-20666
      https://support.microsoft.com/en-us/topic/kb5034957-updating-the-winre-partition-on-deployed-devices-to-address-security-vulnerabilities-in-cve-2024-20666-0190331b-1ca3-42d8-8a55-7fc406910c10

      More Info:
      https://www.bleepingcomputer.com/news/microsoft/microsoft-shares-script-to-update-windows-10-winre-with-bitlocker-fixes/

       

       

      • #2627656

        Simple for the many “Geeks” in this forum.  For others it isn’t.   Microsoft should only offer this update to systems that have BitLocker enabled.  Plus the update should be seamless – that is no powershell scripts…

        3 users thanked author for this post.
        • #2627686

          IMO Resizing partitions always has risk, which just means backup first.  If you wait a month, Microsoft may, by compressing files or deleting deprecated files, find a way to get it to work with too small partitions.

      • #2627830

        Yep…I can see “Aunt Mildred” running that PowerShell script…what could go wrong.

         

         

    • #2627699

      Microsoft may, by compressing files or deleting deprecated files, find a way to get it to work with too small partitions.

      They already did with releasing a PowerShell script that doesn’t require enlarging Restore partition.

    • #2627746

      Just like I said:

      Microsoft working on a fix for Windows 10 Bitlocker Issue

      https://www.bleepingcomputer.com/news/microsoft/microsoft-working-on-a-fix-for-windows-10-0x80070643-errors/

      1 user thanked author for this post.
    • #2627792

      I intend to wait to do updates until Microsoft fixes the issue.  As a Windows 10 Home user, will the tools suggested at http://www.blockapatch.com work for me? I always assumed these tools were only for Windows 10 (or 11) Pro users.

      • #2627950

        Blockapatch has solutions for every version of Windows. I have Home and use WUMgr.

        cheers, Paul

        1 user thanked author for this post.
    • #2627846

      Hello,

      For anyone resizing the recovery partition and following Microsoft instructions well it seems one one more step in the process is needed. By adding this step when the new RE recovery partition is added and you take a look at it in Disk management it is all correctly done. No drive letter added etc.

      I think this would work also work with GUID Partition Table (GPT)

      “Support Article to Resize Windows Recovery Partition is Incorrect for MBR Disks”

      https://answers.microsoft.com/en-us/windows/forum/all/support-article-to-resize-windows-recovery/c35285d7-e93d-4f66-8f06-b76bcd303e49

      Note, it fixed the correct partition but ( KB5034441) still wont install and best to just hide it through using https://blockapatch.com/

      What a real mess Microsoft have created.

      It’s there Happy New Year patch gift to us all!

       

    • #2627931

      In Disk Management, my recovery partition has 522 MB free out of 522 MB, probably cause I’ve disabled restore points?

    • #2628105

      At least this this “security patch” isn’t part of the January cumulative update

    • #2628157

      Situation: Win 10 Pro 64, Windows Updates are configured for manual d/l using Group Policy, and BitLocker is off.  Noticed some sluggishness on Patch Tues but ignored it. Next day I found out KB5034441 had d/l and installed successfully with no errors. No other updates d/l. PC seem to be working normally.

      Question: Since I don’t trust MS, does a successful install of KB5034441 introduce problems I should be aware of? If so, what might they be, and are there mitigation recommendations?

      Thanks for reading.

    • #2628158

      does a successful install of KB5034441 introduce problems

      None.
      It will be there if/when you decide to enable BitLocker.

      1 user thanked author for this post.
    Viewing 11 reply threads
    Reply To: BitLocker-related update triggers install problems

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: