<p>Microsoft has acknowledged a VPN issue that was caused by the update KB5009566 that was released with Patch Tuesday.</p>
<p><img class="alignnone size-full wp-image-3427" src="https://www.wincert.net/wp-content/uploads/2019/12/keyboard-update.jpg" alt="" width="640" height="320" /></p>
<p>The January 2022 updates that were released last week came with security patches and Japanese text appearance issues in Windows 10 (KB5009543) and Windows 11 (KB5009566). Unfortunately, these patches also brought other issues including unexpected restarts of Domain Controllers along with broken VPN connection problems.</p>
<p>Many IT administrators also reported their Windows 2012 servers got stuck in a boot loop after the update, while some other admins reported hard drives appearing in RAW format thus becoming unusable. To solve these issues, IT admins had to roll back update packs leaving many servers vulnerable.</p>
<p>Microsoft has fixed the issue for the Windows 11 VPN issue by releasing an out-of-band update (KB5010795) For all Windows 11 devices.</p>
<p>An update can also be manually downloaded from <a href="https://www.catalog.update.microsoft.com/Search.aspx?q=KB5010795" target="_blank" rel="noopener">here</a>.</p>
<p>Cliff Fisher has offered a piece of advice on his Twitter channel on how to patch the downlevel platforms like Windows Server 2012R2, explaining that there are two types of updates for the Operating System on the older servicing stack and that if you don&#8217;t have the December Security Only update or Monthly Rollup equivalent, you have to install the December update before installing January.</p>
<blockquote class="twitter-tweet" data-width="500" data-dnt="true">
<p lang="en" dir="ltr">A quick thread on patching with Windows Updates on downlevel platforms like 2012R2.</p>
<p>There are two types of updates on OSes on the older servicing stack &#8211; a Monthly Rollup (MR) and a Security-Only (SO).</p>
<p>&mdash; Cliff Fisher (BRD on ð¦Sky) (@brdpoker) <a href="https://twitter.com/brdpoker/status/1483468179108106241?ref_src=twsrc%5Etfw">January 18, 2022</a></p></blockquote>
<p><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script></p>