Master Patch List as of December 13, 2022

Topic

New Reply

#PatchTuesday Business patchers:  Microsoft has indicated that they fixed the memory issue with the LSASS patch but still waiting for community confir
[See the full post at: Master Patch List as of December 13, 2022]

Susan Bradley Patch Lady

2 users thanked author for this post.

abbodi86, Alex5723

Reply | Quote

Replies

From Master Patch List ;

WINDOWS 10
Remember 2004 dropped out of support in December/20H2 got the final update in May

Windows 7 (ESU), Windows 8.1, Windows 10 21H1 got the final update in December.

Reply | Quote

Alex5723 wrote:

Windows 7 (ESU), Windows 8.1, Windows 10 21H1 got the final update in December.

Regarding Win7 ESU and Win8.1 Nope, January 10th 2023 is the MSFT scheduled last service patch for these (although may be salted so, I’m in NO hurry to install them and shall be sticking to feedback/ recommendations here and elsewhere for Win7 ESU and Win8.1)
So, 1/3 correct with ‘Windows 10 21H1 got the final update in December’ 🙂

Keep IT Lean, Clean and Mean!

Reply | Quote

Microfix wrote:

Regarding Win7 ESU and Win8.1 Nope, January 10th 2023 is the MSFT scheduled last service patch for these

Correct. My mistake.

Reply | Quote

regarding KB5012170 for both 22H2 releases on Win10 & Win11, I saw this recently on Neowin:

Microsoft acknowledges it pushed buggy update on Windows 11 and Windows 10 22H2

1 user thanked author for this post.

Lars220

Reply | Quote

They didn’t “acknowledge” anything new or different, all that was listed for all Windows versions since the beginning

do Neowin know that Windows 10 22H2 get the exact same update as Windows 10 20H2-21H2? why would it cause different issue?

2 users thanked author for this post.

PKCano, Microfix

Reply | Quote

abbodi86 wrote:

They didn’t “acknowledge” anything new or different,

I think they did :

Last updated: 2022-12-14

Next steps: We are presently investigating and will provide an update in an upcoming release.

https://www.askwoody.com/forums/topic/final-patches-for-2022/#post-2508830

Reply | Quote

They didn’t, this was listed as known issue in KB5012170 since released in August
https://support.microsoft.com/topic/kb5012170-security-update-for-secure-boot-dbx-72ff5eed-25b4-47c7-be28-c42bd211bb15
https://borncity.com/win/2022/08/12/windows-sicherheitsupdate-kb5012170-fr-secure-boot-dbx-9-august-2022/
https://www.askwoody.com/forums/topic/windows-update-possibly-kb5012170-causes-problems/

Reply | Quote

abbodi86 wrote:

this was listed as known issue in KB5012170 since released in August

Yet Microsoft continued to release it month after month.

Reply | Quote

To be exact they haven’ t released it month after month. It was released back in August to  21H1 and earlier and never pulled.  What happened this month is that they updated the detection to apply to 22H2.  It appears (to me) that many in the reddit thread are on older systems.  I’m not justifying the behavior mind you, I’m just being pedantic.

Susan Bradley Patch Lady

2 users thanked author for this post.

abbodi86, Alex5723

Reply | Quote

At the risk of not seeing the obvious, I installed KB5012170 with the August updates for W10 Pro version 21H2. I have since upgraded to W10 Pro version 22H2 and am wondering if KB5012170 is going to be offered and installed a second time with the December updates for the current version of W10. This security patch has been quite confusing to me. THX for any added info on this.

Reply | Quote

It was offered again with my Dec. Win10 updates.
Susan is recommending hiding it at this time.

Reply | Quote

You won’t get it again if already installed
it’s the same update for Windows 10 20H2-22H2 (like .NET Framework updates)

Reply | Quote

Regarding the .NET Core/.NET 5.0 entry in the Dec 13 Master Patch List, is there a need to revise here?

I am Win10/Pro,21H2. WU delivered .NET6.0.12 KB5021954 and I’ve hidden it with WUSHOWHIDE until MS-DEFCON changes to 3+

The Release Notes for 6.0.12 say that it is a security patch.

Reply | Quote

On neowin.net “Microsoft: Patch Tuesday KB5021233 causing hidparse blue screen on Windows 10 22H2” + workaround

 

Reply | Quote

Already posted here:

KB5021233: You might receive an error (0xc000021a) with a blue screen

Windows 11 Pro version 22H2 build 22621.1413 + Microsoft 365 + Edge

Reply | Quote

For both of my 22H2 Pro and 22H2 Home machines, I could not find hidparse.sys in the Windows\System32 folder, only in the Windows\System32\drivers folder. Any suggestion of how to find the file and compare the version before attempting to install KB5021233? Thank you for the help.

 

Reply | Quote

I am not sure there is a way to tell in advance if your system will be affected as it seems the hidparse.sys file discrepancy might be caused by the KB5021233 installation itself. Sometimes hidparse.sys bsods are caused by out-of-date drivers but this seems to be the cumulative updates handiwork. It should be relatively easy for MS to isolate and fix the problem and so, pending more information, I would recommend not installing the update at this time. Perhaps someone else will post some insight here.

Reply | Quote

Please see the Several Windows 10 versions affected by blue screen issue topic for a more thorough discussion of this issue.

Reply | Quote

Susan Bradley wrote:

#PatchTuesday Business patchers:  Microsoft has indicated that they fixed the memory issue with the LSASS patch but still waiting for community confir
[See the full post at: Master Patch List as of December 13, 2022]

Do we have confirmation that the LSASS issue is fixed ??
As recommended I skipped last months (November) patches on Domain Controller 2012R2.
Are we clear to install the most current updates that are in the update QUE or do I need to manually pick patches to install to get up to date for December ???
Any advise as to what us Business patchers should do about our Domain Controllers and Servers is appreciated.

Reply | Quote