Jump to content
  • Microsoft shares Group Policy fix for KB5043145 that breaks USB, Bluetooth, leads to BSOD

    Karlston

    • 276 views
    • 3 minutes
     Share


    • 276 views
    • 3 minutes

    A few days ago, we reported that the latest KB5043145 C-release update (non-security preview) was breaking PCs, leading to constant restarts, blue screens or green screens of death (BSOD / GSOD), or booting into BitLocker Recovery via the Windows Automatic Repair Tool.

     

    To better understand the issue, Microsoft had urged users to share more feedback about it via the Feedback Hub. Today, the company has issued an update on the problem, adding that USB and Bluetooth device failures can occur as a result of KB5043145.

     

    In case you are having problems with USB connections or Bluetooth, the company says a yellow exclamation mark is displayed against the devices in Device Manager (DEVMGMT).

     

    The company writes:

     

    This issue also causes USB and Bluetooth connections to fail in some devices. Hardware connected via USB and Bluetooth, such as keyboards, memory sticks, printers, and wireless mouses, no longer work after installing the update. In these cases, the USB Host Controller under the Device Manager displays a yellow exclamation mark.

    For now, Microsoft has issued a Group Policy fix for IT admins and system admins that will allow affected managed user devices to roll back the update via Known Issue Rollback (KIR). This is the classic Microsoft technique to "mitigate" a problematic update when a major issue or bug pops up on Windows PCs.

     

    Meanwhile, the KB5043145 update has also been pulled for consumer PCs though it can take up to a full day for the resolution to take effect.

     

    The company explains:

     

    Resolution:

     

    This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices and business devices that are not managed by IT departments. Restarting your Windows device might help the resolution apply to your device faster.

     

    For enterprise-managed devices managed by IT departments that have installed the affected update and encountered this issue, IT administrators can resolve it by installing and configuring the Group policy listed below. The special Group Policy can be found in Computer Configuration -> Administrative Templates -> .

     

    For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback.

     

    Group Policy downloads with Group Policy name:

     

     

    Important: You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting.

    As always, Microsoft says that it is looking to fix the issue in a future update.

     

    Source


    RIP Matrix | Farewell my friend  :sadbye:

     

    Hope you enjoyed this news post.

    Thank you for appreciating my time and effort posting news every day for many years.

    2023: Over 5,800 news posts | 2024 (till end of September): 4,292 news posts


    User Feedback

    Recommended Comments

    There are no comments to display.



    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...