Jump to content
  • Windows 10 January 2024 Patch Tuesday (KB5034122) out -- here's what's new and what broke


    Karlston

    • 4 comments
    • 1.4k views
    • 3 minutes
     Share


    • 4 comments
    • 1.4k views
    • 3 minutes

    It's the second Tuesday of the month, which means it's Patch Tuesday time again. As such, today Microsoft is rolling out the monthly security update (also called "B release") for January 2024 on Windows Server 20H2, and Windows 10 for the latest supported versions, 20H2, 21H2, and 22H2. The new updates are being distributed under KB5034122, bumping up the builds to 19044.3930 and 19045.3930. You can find standalone links to download the new update on the Microsoft Update Catalog at this link here.

     

    The major highlight of the release as usual is security updates for Windows 10.

     

    Highlights

     

    This update addresses security issues for your Windows operating system.

    After a couple of weeks without any, known issues are back:

     

    Known issues in this update

     

    Symptom

     

    Workaround

     

    Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected.

     

    Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

    To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured.

     

    We are working on a resolution and will provide an update in an upcoming release.

     

    Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview).

    To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration.

     

    We are working on a resolution and will provide an update in an upcoming release.

    Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen.

     

    To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen.

     

    We are working on a resolution and will provide an update in an upcoming release.

    Some of the older Windows 10 versions have also received updates today which have been listed below with their respective release notes (KB) linked as well as links to download them at Microsoft's Update Catalog:

     

    Version KB Build Download Support
    1809

    KB5034127

    17763.5329

    Update Catalog Long-Term Servicing Channel (LTSC)
    1607

    KB5034119

    14393.6529

    Update Catalog
    1507

    KB5034134

    10240.20402

    Update Catalog

     

    It is noteworthy here that Windows 10 20H2 and Windows 10 1909 reached the end of servicing. Some editions of 21H2 have also reached the end of servicing.

     

    Source


    User Feedback

    Recommended Comments

    The article misses out on another buggy update.  Im getting error 0x80070643 for KB5034441 today.  From what I am reading elsewhere you get the error if your recovery partition is to small.  I think I will wait to see if it gets fixed before I start messing around with my partitions.

    Link to comment
    Share on other sites


    i had the same problem. i increased the size of the recovery partition to 900mb and the update was then successful.

    when i increased it to over 1gb, i saw problems with a mystery volume in system restore.

    so, 900mb seems fine,

    cheers

    Link to comment
    Share on other sites


    SacredCultivator

    Posted (edited)

    Okay, didn't see comments, but I am also experiencing that Error for KB5034441 as well.
    As Herobrine mentioned, hopefully the update fixes itself in future rather than needing me to tweak the recovery partition.

     

    EDIT:
    Apparently Microsoft most likely won't fix this and it is "on us" to tweak to get the update? That's bogus.
    I was just reading this post about it, so it only pertains to certain users and isn't really a "needed" update?

    Edited by SacredCultivator
    Link to comment
    Share on other sites




    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...