Forum Discussion

BrianG-PPN's avatar
BrianG-PPN
Brass Contributor
Jan 12, 2022
Solved

January 2022 Quality Update Breaks VPN Connections

A couple forum posts: https://community.meraki.com/t5/Security-SD-WAN/Client-VPN-Error-After-January-Windows-Updates/m-p/137114   https://www.reddit.com/r/sysadmin/comments/s1oqv8/kb5009543_januar...
  • Reza_Ameri's avatar
    Reza_Ameri
    Jan 20, 2022
    Yes, your argument is valid.
    As a workaround you may use "Win32 app management" in Microsoft Intune and download the package from the Microsoft Update Catalogue and then deploy it using the Microsoft Intune, take a look at:
    https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-deploy-update-package
    I know it is a bit challenging but it is possible to deploy updates in the Microsoft Intune too.
helviopichamone's avatar
helviopichamone
Copper Contributor
Jan 19, 2022

BrianG-PPN I can confirm the update works, but I got really surprised it is not released as critical update, as it does not seems reasonable Microsoft stop half the companies in the world and does not releases it to automatic applying. Testing, I installed all updates (as I asked all my customers to do) and the bug was there. So I could see one must choose the "Optional Updates", click on the bug correction and apply it manually. It will keep a lot of enterprises, where a technician cannot come computer by computer, in the Cave Era for some time yet.

BrianG-PPN's avatar
BrianG-PPN
Brass Contributor
Jan 19, 2022
The update works however when using Windows Update for Business the "Optional Updates" section within the Windows Update tool is not available so this isn't an option for distributing the updates. If you navigate to the page describing the out of band update here: https://support.microsoft.com/en-us/topic/january-17-2022-kb5010795-os-build-22000-438-out-of-band-2d2b9310-d845-41c4-9907-aeea24f36a63 you can see (in the How to Get This Update section under Windows Update for Business) that it's not available through that release channel. So the behaviour is apparently "as designed" or "expected" but frustrating when we have an OOB update that we'd like to distribute efficiently.
  • jakeward's avatar
    jakeward
    Copper Contributor
    Jan 21, 2022

    BrianG-PPN I've got the exact same issue. It's frustrating as using WU4B is what MS recommend for a company like ours and now we are getting the worst experience when it comes to resolving an issue they have introduced.

    I've also found pausing the update rings has not stopped this update from going out to some users.

    • BusinessWatchNetwork's avatar
      BusinessWatchNetwork
      Copper Contributor
      Feb 08, 2022

      jakeward 

      The update worked for me, but now Outlook does NOT work when I am in the VPN. Does anyone have any solutions for that?

      • object_mxm's avatar
        object_mxm
        Copper Contributor
        Feb 10, 2022
        The problem is in Rasmans.dll, you need to take this file from the December assembly and replace everywhere in the register with a new path for the RasMan service, after reboot.
    • Reza_Ameri's avatar
      Reza_Ameri
      Silver Contributor
      Jan 21, 2022
      Have you tried the workaround which I shared?
      Regarding to the issue with pausing update, make sure report it to the Microsoft Support.
      • jakeward's avatar
        jakeward
        Copper Contributor
        Jan 24, 2022

        Reza_Ameri I'm just attempting this now as the VPN problem is causing us issues now.

        It's still very frustrating that the original broken update is still going out to WU4B but the fix cannot be accessed that way.