KB5010795 out-of-band update for Windows 11, 10 and Windows Server released

Martin Brinkmann
Jan 18, 2022
Updated • Jan 18, 2022
Windows Updates
|
22

Microsoft released out-of-band updates for Windows 11, Windows Server 2022, Windows 10 and other client and server versions of Windows on January 17, 2022.

KB5010795 windows 11

Microsoft acknowledged that the January 2022 security updates were causing issues, especially on Windows Server systems. Windows Update breaking VPN connections was one of the main issues affecting users.

Tip: check out our known issues overview for Windows 11, which we update regularly.

ADVERTISEMENT

The out-of-band updates address several issues in client and server versions of Microsoft's Windows operating system.

Windows 11 -- KB5010795

KB5010795 for Windows 11 is already available via Windows Update, as a direct download, and WSUS (by importing it). The update includes the latest servicing stack update.

The update fixes the following two issues:

  • Fixes an issue that could cause IPSEC (IP Security) connections that contain Vendor IDs to fail.
  • Fixes an issue that could cause removable media that is using the Resilient File System (ReFS) from failing to mount or mounting in the RAW file format.

The known issue that some " image editing programs might not render colors correctly on certain high dynamic range (HDR) displays" remains.

Windows 10 versions 20H2, 21H1 and 21H2 -- KB5010793

KB5010793 for Windows 10 is already available via Windows Update, the Microsoft Update Catalog, and as an import via WSUS.

The update addresses four issues in total:

  • Fixes an issue that could cause IPSEC (IP Security) connections that contain Vendor IDs to fail.
  • Fixes an issue that could cause removable media that is using the Resilient File System (ReFS) from failing to mount or mounting in the RAW file format.
  • Fixes an issue that could cause Windows Servers to restart unexpectedly on domain controllers.
  • Fixes an issue that prevented "Active Directory (AD) attributes from being written properly during a Lightweight Directory Access Protocol (LDAP) modify operation" when multiple attribute changes were made.

Microsoft lists three known issues, all of which are long-standing:

  • The new Microsoft Edge may not be installed on devices that use custom ISO images or custom offline media to install new versions of Windows 10.
  • Some devices may not be able to install updates after installing KB5003690 from June 2021. Windows may display the error "PSFX_E_MATCHING_BINARY_MISSING".
  • when connecting devices in an untrusted domain using Remote Desktop, connections may fail to authenticate using smart card authentication. Should be resolved according to Microsoft through Known Issue Rollback.

Windows Server 2022 -- KB5010796

KB5010796 for Windows Server 2022 is available via Windows Update, as a direct download from the Microsoft Update Catalog, and as an import via WSUS. The update requires the installation of KB5005039, released August 2021.

The update fixes four issues, two of which are also fixed in Windows 11's update described above, and all four are also fixed in Windows 10's update.

  • Fixes an issue that could cause IPSEC (IP Security) connections that contain Vendor IDs to fail.
  • Fixes an issue that could cause removable media that is using the Resilient File System (ReFS) from failing to mount or mounting in the RAW file format.
  • Fixes an issue that could cause Windows Servers to restart unexpectedly on domain controllers.
  • Fixes an issue that prevented "Active Directory (AD) attributes from being written properly during a Lightweight Directory Access Protocol (LDAP) modify operation" when multiple attribute changes were made.

Microsoft lists one known issues: when connecting devices in an untrusted domain using Remote Desktop, connections may fail to authenticate using smart card authentication. Should be resolved according to Microsoft through Known Issue Rollback.

Other out-of-band updates

Microsoft released the following updates as well:

KB5010792 for Windows 10 version 1909 -- fixes the IPSEC issue.

KB5010790 for Windows 10 version 1607 and Windows Server 2016 -- fixes the same four issues that the Windows Server 2022 update fixes

Now You: have you installed the out-of-bound updates? (via Born)

Summary
KB5010795 out-of-band update for Windows 11, 10 and Windows Server released
Article Name
KB5010795 out-of-band update for Windows 11, 10 and Windows Server released
Description
Microsoft released out-of-band updates for Windows 11, Windows Server 2022, Windows 10 and other client and server versions of Windows on January 17, 2022.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Previous Post: «
Next Post: «

Comments

  1. AT said on January 18, 2022 at 7:31 am
    Reply

    So should this be installed BEFORE the broken regular updates to prevent them from screwing up our servers and PCs, or AFTER, which might be too late?

  2. notanon said on January 18, 2022 at 11:33 am
    Reply

    @AT, these problems were reported on Tuesday, January 11th on various places like Reddit. Bleeping Computer reported these problems immediately (on Wednesday, January 12th).

    Because Microsoft NEVER acknowledged these problems in their “known issues”, ghack didn’t report squat (nothing in the comments section either).

    And I didn’t give ghacks the heads up in the comments section, since they chose to delete one of my comments in it’s entirety (this is what happens when you censor “wrong think”, no one’s going to help you out and tell you that you’re not reporting some news).

    Bleeping Computer also report OOB Windows Updates a half a day earlier than ghacks. Thank God I don’t rely on this site for all my news LOL.

    Jordan Peterson says 10% of the employees do most of the work.

    Unfortunately for Microsoft, the programmers that could fix the defective Windows Updates issued on Tuesday, January 11th, were out sick to avoid being fired for being unvaccinated for Covid-19 due to Biden’s OSHA Vaccination Mandate that took effect on Monday, January 10th for all private employers with 100 or more employees.

    Since only the incompetent SJW programmers that got jabbed were working, the defective updates were not fixed, and Microsoft refused to acknowledge the problem on their “known issues” (kinda like burying you head in the sand and pretending the problem didn’t exist).

    On Thursday, January 13, the United States Supreme Court struck down Biden’s OSHA Vaccination Mandate in it’s entirety, because OSHA has no jurisdiction and authority to issue a vaccine mandate.

    On Friday, January 14th, unvaccinated employees (of private organizations with 100 or more workers) returned to work. So now the defective Windows Updates could be fixed.

    On Monday, January 18th, the Out of Band Updates were released.

    Apparently, all the smart programmers at Microsoft are unvaccinated.

    1. insect33 said on January 18, 2022 at 1:36 pm
      Reply

      As a JBP fan, your anti-vaccination rant is has nothing to do with what he said. he would never oppose people getting vaccinated, he’s only against government mandating the vaccine against their will.

    2. Sebas said on January 18, 2022 at 5:08 pm
      Reply

      @notanon You’re right, I too read it first at Bleeping Computer. Another up to date source of all things Windows e.a. is https://www.tenforums.com/ and it’s sister site https://www.elevenforum.com/.

  3. microfix said on January 18, 2022 at 11:51 am
    Reply

    rant/ It would appear that ‘screw it up to fix it’ is Microsoft’s philosophy with the dismissal of the QA dept and soon after the 29th July 2015 /rant

    1. semce said on January 18, 2022 at 2:50 pm
      Reply

      Failing to get vaccinated is not very smart either so I wonder just how smart those unvaccinated employees really are.

      1. Borkness Descends said on January 18, 2022 at 8:01 pm
        Reply

        @semce
        Let’s just see about that. The jury’s still out on the matter. Enjoy the rest of your life buddy. That “update” can’t be removed..

      2. TelV said on January 19, 2022 at 4:45 pm
        Reply

        That “update” as you so quaintly put it may save the life of someone else even if you don’t care much about your own.

        By “someone else” I’m talking about the health professionals who will have to take care of you if you arrive in hospital with breathing difficulties. Do you know how many doctors and nurses have died from Covid-19 after being infected by those who refuse to get jabbed? Far too many.

        I had my two Pfizer jabs in April and May last year and a further booster this month. The only side effect was a pain in my arm at the site of the injection which lasted for 12 hours each time, but was gone the next morning. Nothing to be afraid of if that’s the reason you object to being vaccinated.

      3. Anonymous said on January 19, 2022 at 9:44 pm
        Reply

        There are 2 ways to deal with virus problems:
        The best way, take care of your immune system, can be hard/expensive. YMWV
        The easy way, take a vaccine.
        The problem is when the vaccine is experimental…
        I take care of my immune system and do not get cold/flu/etc.
        My immune system is like a shark’s :)
        No need for ANY vaccine for me.

    1. Borkness Descends said on January 18, 2022 at 5:52 pm
      Reply

      Yeah KB5010798 just borked my Windows 7 ESU computer. Starting takes forever and afterwards it says it can’t connect to System Event Notification service, resulting in non admin accounts not able to log in. System Event Notification service IS running and autostarting.. Yet another embarrassment for Microsoft and their team of totally incompetent monkeys. Explain THIS to ESU paying customers, you f****** F***S!!!!!

      1. Martin P. said on January 18, 2022 at 7:13 pm
        Reply

        @Borkness Descends

        Installed with no problems on my Windows 7 box but I believe this is most probably because my config is different from yours.

        Best of luck with your search for a solution.

      2. Borkness Descends said on January 18, 2022 at 7:59 pm
        Reply

        Martin P.
        The solution was to uninstall the so-called update and then everything worked again. KB5010798 is now hidden and will never ever be installed again. Ever.

      3. Martin P. said on January 18, 2022 at 9:23 pm
        Reply

        @Borkness Descends

        Glad it worked for you!

      4. Anonymous said on January 19, 2022 at 12:53 am
        Reply

        I installed KB5010798 on my Windows 7 PC with ESU and no issues like what you are talking about.

      5. Borkness Descends said on January 19, 2022 at 5:42 pm
        Reply

        @Anonymous
        I’m happy for ya. Since you have no issues then I am obviously a liar. Thanks for clearing this up.

  4. chesscanoe said on January 18, 2022 at 3:13 pm
    Reply

    I installed KB5010793 on 1/17, bringing my home Windows 10 21H2 laptop to 91044.1469. However only after an actual shutdown would Belarc Advisor then show KB5010793 and KB5009636 as installed as of 1/18.

  5. VioletMoon said on January 18, 2022 at 8:02 pm
    Reply

    Computer geeks actually install MS updates on the day they are released? And then reinstall with out-of-band updates? Whoa!

    And then write about Covid causing the problem. Got it.

    StartPage came out with a neat privacy add-on for browsers:

    Privacy Score: 4/5
    ghacks.net
    Contains a small number of third-party trackers, and/or one high-risk tracker.

    Tracking away the ghacks way.

    1. Sebas said on January 18, 2022 at 9:05 pm
      Reply

      @VioletMoon “Tracking away the ghacks way”. Excellent, lol. Brave blocks 10 trackers/ adverts, with 4 Adgard ublock filters optimized added and Adguard extension blocks another one on ghacks.

  6. Yuliya said on January 20, 2022 at 9:11 am
    Reply

    I have installed this, but my machies were working fine on the December update also.

    1. Yuliya said on January 20, 2022 at 11:48 am
      Reply

      *January update also…

  7. Bruce said on January 21, 2022 at 10:23 pm
    Reply

    we have a read-only domain controller on windows 2016, and installed kb5010790 last night and it ended up in a continual reboot cycle with the same lsass.exe event that was described with the original patch. So me thinks MS missed something there. Our normal domain controllers were all fine, even when we used the original patch released on Jan 11.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.