![](\"https:\/\/images.idgesg.net\/images\/article\/2020\/07\/microsoft_windows_updates_cycle_arrows_laptop_mobile_phone_3x2_1200x800-100851684-large.3x2.jpg?auto=webp&quality=85,70\"\/)
<\/p>\n<\/p>\n
Credit to Author: Greg Lambert| Date: Fri, 11 Feb 2022 12:21:00 -0800<\/strong><\/p>\n There are (<\/span>as of now<\/a>) 51 patches to the Windows ecosystem for February, but no critical updates and no “Patch Now” recommendations from the Readiness team. I’m hoping that with this month’s list of Patch Tuesday updates, we can enjoy the quiet after the storm. January was tough for a lot of folks. And, with this month’s very light release from Microsoft, corporate security and systems administrators can take the time needed to test their applications and desktop\/server builds. It’s also important to invest in their testing methodologies, release practices, and how their applications may be affected by OS-level updates and patches.<\/span><\/p>\n You can find more information on the risk of deploying these Patch Tuesday updates using our detailed infographic<\/a><\/span>.<\/span><\/p>\n There are no reported high-risk changes to Windows this month. However, there is one reported functional change, and an additional feature added:<\/span><\/p>\n When testing your printing services, ensure that you are validating your<\/span> spooler<\/span><\/a> and SHD (shadow files). Testing these service artifacts is especially important if you employ symbolic or hard links to access these jobs.<\/span><\/p>\n Each month, Microsoft includes a list of known issues that relate to the operating system and platforms included in this update cycle. There is more than usual, so I have referenced a few key issues that relate to the latest builds from Microsoft including:<\/span><\/p>\n After installing updates released Jan. 11 or later, applications that use the Microsoft .NET Framework to acquire or set Active Directory Forest Trust Information might have issues. The apps might fail or close, or you might receive an error from the app or Windows. You might also receive an access violation (0xc0000005) error. To resolve this issue manually, apply the out-of-band updates for the version of the .NET Framework used by the app. We recommend that you scan your internal line of business applications for any dependencies on<\/span> System.DirectoryServices API<\/span><\/a>.<\/span><\/p>\n Though there is a much smaller list of patches this month, Microsoft released several revisions to previous patches, including:<\/span><\/p>\n This month Microsoft has published two mitigating factors, including:<\/span><\/p>\n Each month, we break down the update cycle into product families (as defined by Microsoft) with the following basic groupings:<\/span><\/p>\n There are a total of 22 (+1) updates to the Microsoft Edge (Chromium) browser this month. None are critical, with one patch rated moderate and the remaining rated important. Unusually, there was an additional update for Microsoft Edge posted yesterday (<\/span>CVE-2022-23246<\/span><\/a>) that was included as part of an updated release note for\u00a0<\/span>Microsoft Edge security update found\u00a0here<\/a>. Add these Chrome (Edge and Chromium) updates to your regular update release schedule.<\/span><\/p>\n We were hoping for a quieter update this month and Microsoft really delivered \u2014 with no critical updates for Windows or Microsoft Office. Given that January\u2019s release was large and complex, several problems were encountered, including:<\/span><\/p>\n To remedy these and other reported (minor) issues, a rare Out-of-Band (OOB) update<\/span>\u00a0was released on Jan 17<\/a>. Microsoft has posted 26 patches this month, covering Hyper-V, printing, error\/logging sub-systems, networking, and video codecs. Given the testing requirements for these types of changes to the core operating system, we suggest a staged approach and adding these Windows updates to your standard update release schedule.<\/span><\/p>\n This month’s patches for Microsoft Office will install on the following baselines:<\/span><\/p>\n Though Microsoft has published 11 updates (all rated important) for this release, only eight apply to Windows systems. Microsoft has shared some basic testing guidelines for the updates, including:<\/span><\/p>\n Microsoft also published a major known issue with this month’s Office update, saying: “<\/span>The Machine Translation service fails if the content contains certain HTML tags.” To work around this issue, see <\/span>Publishing pages cannot be translated in SharePoint Server 2019 (KB5011291)<\/span><\/a>. <\/span>All the local office installations (excluding click-to-run virtualized instances) require user interactions and do not significantly degrade the system if affected. These patches represent a low risk and have been documented to affect core functionality (potentially affecting dependent line-of-business applications). Add these updates to your standard Office update schedule.<\/span><\/p>\n Following the trend of a very light patch cycle, Microsoft has not released any updates for the Exchange Server platform.<\/span>\u00a0<\/span><\/p>\n Things are definitely light on the ground this month, but we do have a few very minor updates for Microsoft development tools, including two patches to Visual Studio (<\/span>CVE-2022-21986<\/span><\/a> and<\/span> CVE-2022-21991<\/span><\/a>) Both of these minor updates are rated important by Microsoft and should be (almost casually) added to your standard development patch schedule.<\/span><\/p>\n Adobe released several security updates this month, but luckily nothing for Adobe Reader. You can find Adobe’s\u00a0<\/span>February release notes\u00a0here<\/a>; it\u00a0relates to Adobe Premier, Illustrator, Photoshop, After Effects, and Creative Cloud Desktop. Let’s see what Adobe has in store for us in March.<\/span><\/p>\n http:\/\/www.computerworld.com\/category\/security\/index.rss<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Credit to Author: Greg Lambert| Date: Fri, 11 Feb 2022 12:21:00 -0800<\/strong><\/p>\n<\/p>\n