MAY22 Patch Failures

Usage and Config Patch
1

Anyone else having high .NET failure numbers in testing on Windows 2012R2? So far, these updates have repeatedly failed multiple servers. Also the 2019 OS update has failed a few times.

2012R2:
Failed MS22-MAY: Security Monthly Quality Rollup - Monthly Rollup - Windows Server 2012 R2 - .NET Framework 4.8 - KB5013631 (x64)

Failed MS22-MAY: Security Monthly Quality Rollup - Monthly Rollup - Windows Server 2012 R2 - .NET Framework 3.5 - KB5013638 (x64)

Failed MS22-MAY: Security Only Quality Update - Security Only - Windows Server 2012 R2 - .NET Framework 3.5 - KB5013621 (x64)

Also having high fail rates on 2019:

Failed MS22-MAY: Cumulative Update for .NET Framework 3.5/4.7.2 for Windows Server 2019 - Windows Server 2019 - .NET Framework 3.5/4.7.2 - KB5013641 (x64)

Failed MS22-MAY: Cumulative Update for Windows Server 2019 - Windows Server 2019 - KB5013941 (x64)

2

Also I’m getting a Fixed with Code 3. It reports it as fixed, goes not relevant briefly, then is relevant again. This is with the cumulative update for server 2019. It does copy it to the server successfully, but won’t install. Also WSUS still sees it as relevant obviously because its not installed.
Not sure if the .NET’s are doing the same.

The failing 2019 update shows this:

waithidden “{pathname of system folder & “\wusa.exe”}” “{storage folder of client}__Download\windows10.0-kb5013941-x64_8df2c89490d6cd19f5086728dbc3c991decefad7.msu” /quiet /norestart

The 2016 updates and prior 2019 updates that have been successful show this:

waithidden “{pathname of system folder & “\wusa.exe”}” “{pathname of client folder of current site & "__Download\windows10.0-kb5012647-x64_546889f367caf2a1edd79f5db7d8507e7a53e31b.msu”}" /quiet /norestart

Is this correct?

3

Yep were getting the same - task showing as failed yet actions info showing as Evaluating with an exit code of 3

MS22-MAY KB5013941 (Windows 10 Version 1809 )

4

@Girish might be a field issue.

@SmokyMTN and @clarkc could you please open https://support.bigfix.com support tickets so we can track and investigate further with logs and details?
Related thread:
Content Release: Patches for Windows - May 2022 Security Updates

5

We are getting the same exit code(3). A manual run of windows update installed the updates successfully.

6

Getting the same issue with the new 2019 .NET and Cumulative update. We did the same as others and manually installed to test and was successful. Is there any update to as when this will be fixed?

7

The fixlet is expecting the installer to be located in the BES client storage folder which is not the case

prefetch windows10.0-kb5013641-x64_5cf245f52876a8a50a7155fada0245c6d0533bfb.msu sha1:5cf245f52876a8a50a7155fada0245c6d0533bfb size:80320998 https://catalog.s.download.windowsupdate.com/c/msdownload/update/software/secu/2022/04/windows10.0-kb5013641-x64_5cf245f52876a8a50a7155fada0245c6d0533bfb.msu sha256:16d6213b0505822146549b223347850f356fb263245fdfe029421d17a3b95cf4

// Is Windows Update service running?
continue if {exists running service "wuauserv" OR NOT exists service "wuauserv" whose (start type of it = "disabled")}

waithidden "{pathname of system folder & "\wusa.exe"}" "{storage folder of client}\__Download\windows10.0-kb5013641-x64_5cf245f52876a8a50a7155fada0245c6d0533bfb.msu" /quiet /norestart
8

How has this been delivered if it’s clear it will never be installed?

9

We are seeing the same thing but only with the windows 1809 cumulative. The cumulative for 1607 and 1909 went fine. It’s just 1809 that’s failing. Workstations and servers.

I’ve submitted a support case.

10

Dev just released an update.