Final patches for 2022

Topic

New Reply

#PatchTuesday and MicrosoftCentric It’s the final patches for 2022 for those of you in the Microsoft centric world But don’t just think operating syst
[See the full post at: Final patches for 2022]

Susan Bradley Patch Lady

7 users thanked author for this post.

CAS, lmacri, fk5353, abbodi86, geekdom, joni1eye, Alex5723

Reply | Quote

Replies

AKB 2000003 has been updated for Group B Win7 (ESU) and Win8.1 on Dec 13, 2022.

There is a Security-only Update for those with Win7 ESU subscriptions.
There is no December IE11 CU for Win7 ESU subscriptions.

December Rollup KB5021291 Download 32-bit or 64-bit for those with Win7 ESU subscriptions.

******  Note changes to SSU requirements:
You must have at least the September 2022 Servicing Stack KB5017397 previously installed to receive these updates – Download 32-bit or 64-bit  for those with Win7 ESU subscriptions.

There are .NET Framework updates listed for Win7. See #2507830.

****** NOTE: ********
Microsoft has released a new ESU Licensing Preparation Package KB5016892 for the extension of Win7/Windows Server 2008 R2 SP1 ESU on Aug 25, 2022. Requires SHA-2 KB4474419 (9/23/2019 or later) and SSU KB4490628 (3/12/2019).

2 users thanked author for this post.

abbodi86, SueW

Reply | Quote

Apple Released today:

iOS 16.2 (20C65) –
iPadOS 16.2 (20C65) –
macOS 13.1 (22C65) –
watchOS 9.2 (20S361) –
tvOS 16.2 (20K362) –
iOS 15.7.2 (19H218) –
iPadOS 15.7.2 (19H218) –
HomePod software version 16.2 –

https://support.apple.com/en-us/HT201222

3 users thanked author for this post.

bassmanzam, arfurdent, BobbyB

Reply | Quote

Also see AKB2000014 for more information on the Apple updates.

Reply | Quote

Guinea Pig Update
Version and build after update: Win11Pro 22H2.22621.963 x64

Windows Update for all and waited to reboot until all finished installation:

• 2022-12 .NET Core 3.1.32 Security Update for x64 Client (KB5021953)
• 2022-12 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5020880)
• 2022-12 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5021255)
• Windows Malicious Software Removal Tool x64 – v5.108 (KB890830)

All installed without error and the system rebooted without error.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1413 x64 i5-9400 RAM16GB HDD Firefox112.0b3 MicrosoftDefender

Reply | Quote

Microsoft Windows Security Updates December 2022 overview

Windows 10 version 21H1 reached end of support today. There will be no future updates for the operating system.

There will be only one more Patch Day for Windows 7 and 8/8.1 after the December 2022 Patch Tuesday.

Microsoft designated Windows 10 version 22H2 for broad deployment.

Microsoft released security advisory ADV220005 on Microsoft Signed Drivers Being Used Maliciously.

The following client versions of Windows have known issues: Windows 7, Windows 8.1, Windows 10 version 20H2, 21H1, 21H2 and 22H2, Windows 11 version 21H2 and 22H2

The following server versions of Windows have known issues: Windows Server 2008, 2008 R2, 2012, 2012 R2, Windows Server 2016, 2019 and 2022

Operating System Distribution:

Windows 7 (extended support only): 15 vulnerabilities: 3 critical and 11 important, 1 moderate
PowerShell Remote Code Execution Vulnerability — CVE-2022-41076
Windows Secure Socket Tunneling Protocol (SSTP) Remote Code Execution Vulnerability — CVE-2022-44676
Windows Secure Socket Tunneling Protocol (SSTP) Remote Code Execution Vulnerability — CVE-2022-44670

Windows 8.1: 20 vulnerabilities: 3 critical and 16 important, 1 moderate
same as Windows 7

Windows 10 version 21H1, 21H2 and 22H2: 26 vulnerabilities, 3 critical and 22 important, 1 moderate
same as Windows 7

Windows 11 and Windows 11 version 22H2: 25 vulnerabilities, 3 critical and 21 important, 1 moderate
same as Windows 7

Windows Server products;

Windows Server 2008 R2 (extended support only): 15 vulnerabilities: 3 critical and 11 important, 1 moderate
PowerShell Remote Code Execution Vulnerability — CVE-2022-41076
Windows Secure Socket Tunneling Protocol (SSTP) Remote Code Execution Vulnerability — CVE-2022-44676
Windows Secure Socket Tunneling Protocol (SSTP) Remote Code Execution Vulnerability — CVE-2022-44670

Windows Server 2012 R2: 20 vulnerabilities: 3 critical and 16 important, 1 moderate
same as Windows Server 2008 R2.

Windows Server 2016: 20 vulnerabilities: 3 critical and 15 important, 2 moderate
same as Windows Server 2008 R2.

Windows Server 2019: 25 vulnerabilities: 3 critical and 21 important, 2 moderate
same as Windows Server 2008 R2.

Windows Server 2022: 25 vulnerabilities: 3 critical and 21 important, 2 moderate
same as Windows Server 2008 R2…

Reply | Quote

KB5019959 broke DA.
Can someone verify if direct Access is fixed by the latest updates?

Reply | Quote

DirectAccess is fixed. I am patching abt 10-20 test users with the issue and is resolved.

some of them downgraded from ENT to PRO… I am guessing because they cannot or could not talk to the KMS server

Reply | Quote

PK reports that searching in the Microsoft catalog site appears to be wonky – you can search by KB but searching by 2022-12 gives you results that don’t make sense. Apparently the Outlook search team is branching out to the Catalog site?

I noticed this last month and discovered if you place “quotes” around the date (double or single quotes),  it’ll work.

i.e. “2022-12” 22h2 x64

Only displays the Dec updates for Windows 10/11 22H2 x64 versions.

1 user thanked author for this post.

Microfix

Reply | Quote

That didn’t work either. Not only the Catalog is broken, but the Software Update Services History page hasn’t been updated today either (as of 5:00pm CST US). See #2507942.

Notice there are over 1000 matches and the shot of page 3 of the search goes back to Sept/Oct.

Reply | Quote

Works just fine for me in SeaMonkey, Edge, Chrome and Opera.

I can’t really tell from your screen shot but, If you copied/pasted the date I posted above into the search box, the quote marks were “smart quotes” not regular quotes (our forum S/W always converts regular quotes into smart quotes) and smart quotes don’t work!

Reply | Quote

I can vouch for your advice. When I tried simply 2022-12 with ordinary quotes from my keyboard’s uppercase ‘ key, I got about 245 results or so. This was about 10 minutes ago using Firefox 108.

When I tried the date without quotes (and when I tried it out of curiosity with the “smart” quotes in red from your post above), I got “over 1000 results” and it wanted me to revise the query to produce better results.

Reply | Quote

OK, If I use the ” from this site, it works as it should.
I have never had to use the quote marks before. The 2022-11 worked fine last month.
Who knows? It’s Microsoft.

I was working on the list for multiple versions (Win7/8.1/10/11) so I needed the general list. It would have been too much trouble to have to specify each one individually.

Reply | Quote

KB5022083 Change in how WPF-based applications render XPS documents for .NET

Reply | Quote

Hardened Windows user:

(KB5021255) Cumulative Update for Windows 11 Version 22H2 for x64-based Systems
(KB5020880) Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64
(KB5021953) .NET Core 3.1.32 Security Update for x64 Client
(KB890830) Windows Malicious Software Removal Tool x64 – v5.108

Now running Windows 11 Pro Version 22H2 (OS Build 22621.963.

No hiccups.  Firefox also (automatically) updated to v108.0.

NAS

(KB5021233) Cumulative Update for Windows 10 Version 22H2 for x64-based Systems
(KB5021089) Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Windows 10 Version 22H2 for x64
(KB5021953) .NET Core 3.2.32 Security Update for x64 Client
(KB890830) Windows Malicious Software Removal Tool x64 – v5.108

Now running Windows 10 Pro Version 22H2 (OS Build 19045.2364)

No hiccups.  Firefox also (automatically) updated to v108.0.

Create a fresh drive image before making system changes/Windows updates, in case you need to start over!

We all have our own reasons for doing the things that we do. We don't all have to do the same things.

Computer Specs

2 users thanked author for this post.

geekdom, fernlady

Reply | Quote

Booted into the B side of my dual boot:

(KB5021255) Cumulative Update for Windows 11 Version 22H2 for x64-based Systems
(KB5020880) Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64
(KB5021953) .NET Core 3.1.32 Security Update for x64 Client
(KB5012170) Security Update for Windows 11 22H2 for x64-based Systems
(KB890830) Windows Malicious Software Removal Tool x64 – v5.108

Now running Windows 11 Pro Version 22H2 (OS Build 22621.963.

No hiccups. Firefox also (automatically) updated to v108.0.

Create a fresh drive image before making system changes/Windows updates, in case you need to start over!

We all have our own reasons for doing the things that we do. We don't all have to do the same things.

Computer Specs

Reply | Quote

Thanks for the heads up about KB5012170! I hid that one, along with the other 3 released today. I plan to install the other 3 on or about the 27th of this month (with Susan’s blessing, of course) and AFTER installing the other 3 and rebooting successfully, I’ll wait my usual 15 minutes or so for everything to finish running in the background.

Once that’s done, I’ll try my hand at having WU install 5012170 to see if I have any success. If the installation fails, then it’s off to purgatory for that one! Period.

Until I decide to make some changes to my machines, like enabling TPM 2 and changing the SSD from MBR to GPT so I can then enable the fancier suite of protection in windows 10. Only then will KB5012170 be allowed out of purgatory.

Reply | Quote

About MU catalog search shenanigans, here is some discoveries based on experiments, take it with fudge factor

– use the + sign between words directly in browser url to return the results presorted by Last Updated

– the search term doesn’t look into the Title only
it can be formated to fill the catalog columns in respective order, separated with + sign (or spaces): Title+Products+Classification
one of them can be dropped in some cases, and still get results

– the – sign can be used to separate words in a column for above format

– the double qoutes doesn’t seem to have any effect in my tests, i get the same results with ot without it

– for version shared across multiple products (e.g. 22H2), you can use the product picker to separate results

===
suggested search format, just change the year-month for upcoming months

Win11 22H2

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-22H2+11+Updates

Win10 22H2

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-22H2+10+Updates

Win10 21H2

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-21H2+10+Updates

Win10 1809

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-1809+10+Updates

Win10 1607

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-1607+10+Updates

Server 22H2

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-22H2+Server+Updates

Server 2022 / 21H2

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-21H2+Server+Updates

Server 2019

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-2019+Server+Updates

Server 2016

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-2016+Server+Updates

Server 2012 / R2

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-2012+Server+Updates

Windows 8.1

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-8.1+8.1+Updates

Windows 8 Embedded

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-8+Embedded-8+Updates

Windows 7 Embedded

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-7+Embedded-7+Updates

Windows 7

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12-7+7+Updates

other examples:

all Win10 updates for this month (you still get some Win11 updates published in Windows 10 GDR-DU category)

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12+10+Updates

all Win11 this month (21H2 can’t be separated because the version id is not used)

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12+11+Updates

all .NET updates for this month

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12+.NET+Updates

or for .NET Framework only

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-12+Framework+Updates

new .NET Frameworks for Win10 1607

https://www.catalog.update.microsoft.com/Search.aspx?q=1607+Feature

new .NET Frameworks for all Win10 versions

https://www.catalog.update.microsoft.com/Search.aspx?q=.NET+10+Feature

all 2022 security updates for Win10 LTSB/LTSC (the 3 versions)

https://www.catalog.update.microsoft.com/Search.aspx?q=2022-+LTSB+Security

all updates for Win10 1809

https://www.catalog.update.microsoft.com/Search.aspx?q=1809+10+Updates

all updates for Server 2019

https://www.catalog.update.microsoft.com/Search.aspx?q=Cumulative-2019+Windows-Server+Updates

2 users thanked author for this post.

Steve, Sueska

Reply | Quote

I appreciate these direct links because I noticed, probably back in October, that trying to use the normal 2022-10 in the search box was not working properly. These links work well for Windows 10 22H2 and Windows 7.

However, your link for Windows 8.1 doesn’t seem to work (giving me a 404 error). That said, even using the normal search before October never seemed to allow me to isolate the 8.1 entries (so I would just sort on the Products column and page down to find 8.1 updates).

Reply | Quote

Search is accidentally missing from W8.1 url, I cannot edit the reply now 🙂

1 user thanked author for this post.

Matthew

Reply | Quote

Fixed that for you.

2 users thanked author for this post.

abbodi86, Matthew

Reply | Quote

macOS Big Sur 11.7.2 Updated successfully 0n 2020 iMac

macOS Monterey 12.6.2 Updated successfully on OCLP 2014 MacBook Pro

Safari 16.2 on both machines Succesful

OCLP users of unsupported Macs running Monterey and Bootcamp may experience high CPU\Fan use with MDS_stores and VSService process’s fixed here, after leaving for an hour for indexing, by System Preferences->Spotlight->Privacy (tab) and adding any external Storage or Bootcamp partition to the “Prevent Spotlight” search list, no degredation of speed in storage etc but your Battery (life)\Fan\CPU will thank you.

Up to now on the OCLP Monterey machine “post install” repatching hasn’t needed to be done. Apart from that no problems.

Just open a terminal window and type “top” without the quotes to see the process thats giving high use.

Reply | Quote

Windows 10 Home 22H2

KB5021233 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems
and
KB5021233 Cumulative Update for .NET Framework 3.5, 4.8, and 4.8.1 for Windows 10, version 22H2 for x64

Installed in < 2 minutes.

No problems or changes detected.

HTH, Dana:))

1 user thanked author for this post.

geekdom

Reply | Quote

Windows 11 Pro 22621.963

Windows Malicious Software Removal Tool x64 – v5.108 (KB890830)

2022-12 .NET 6.0.12 Security Update for x64 Client (KB5021954)

2022-12 .NET 7.0.1 Security Update for x64 Client (KB5021955)

2022-12 .NET Core 3.1.32 Security Update for x64 Client (KB5021953)

PowerShell v7.3.1 (x64)

2022-12 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5020880)

2022-12 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5021255)

All were installed with no issues.

 

--Joe

1 user thanked author for this post.

geekdom

Reply | Quote

December 2022 Patch Update:
Win10 Pro x86 and x64
KB5021233 CU & KB5021089 NET updated with a slight issue,
required a second try on both systems which, installed successfully.
SFC & DISM checkhealth reported no violations.
Eventviewer clean and usual config re-introduction to O&OShutup 10++
Winver: 22H2 (OS Build 19045.2364)

Win8.1 Pro x64
KB5021294 SMQR and KB5020878 NET4.8 went in without a hitch
(two devices done one more awaits)
SFC and DISM checkhealth showed no violations.

Keep IT Lean, Clean and Mean!

2 users thanked author for this post.

DrBonzo, geekdom

Reply | Quote

.NET 7.0.1

Reply | Quote

FYI

From the .NET Blog:

1) .NET December 2022 Updates – .NET 7.0.1, .NET 6.0.12, .NET Core 3.1.32

• Today, we are releasing the .NET December 2022 Updates. These updates contain security and non-security improvements.
• Security CVE-2022-41089 – .NET Remote Code Execution Vulnerability. Microsoft is releasing this security advisory to provide information about a vulnerability in .NET Core 3.1, .NET 6.0., and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A remote code execution vulnerability exists in .NET Core 3.1, .NET 6.0, and .NET 7.0, where a malicious actor could cause a user to run arbitrary code as a result of parsing maliciously crafted xps files.

2) .NET Framework December 2022 Security and Quality Rollup Updates

• Today, we are releasing the December 2022 Security and Quality Rollup Updates for .NET Framework.
• Security CVE-2022-41089 – .NET Framework Remote Code Execution Vulnerability. This security update addresses a vulnerability where restricted mode is triggered for the parsing of XPS files, preventing gadget chains which could allow remote code execution on an affected system. For more information please see CVE-2022-41089.

HTH.

 

1 user thanked author for this post.

Alex5723

Reply | Quote

Listed on the master patch list.

Susan Bradley Patch Lady

Reply | Quote

Microfix wrote:

Win8.1 Pro x64
KB5021294 SMQR and KB5020878 NET4.8 went in without a hitch
(two devices done one more awaits)
SFC and DISM checkhealth showed no violations.

This is the last update for Windows 8.1.
Are you thinking on upgrating to Windows 10 ?

Reply | Quote

Not the last, Win8.1 gets January updates which may/may not be the last (remember win7 in February 2020 a final patch was issued to fix a destop GUI fluxup)
No plans to up/down-grade beyond Win8.1 on those devices and shall be used offline. Total migration to W10 is already done with a few loose ends to tie up during the holiday season on other devices.

Keep IT Lean, Clean and Mean!

Reply | Quote

KB5021249 is breaking virtual machines :

After installing this update, apps that use ODBC connections through Microsoft ODBC SQL Server Driver (sqlsrv32.dll) to access databases might not connect. Additionally, you might receive an error in the app, or you might receive an error from the SQL Server. Errors you might receive include the following messages:

The EMS System encountered a problem. Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream.

The EMS System encountered a problem. Message: [Microsoft][ODBC SQL Server Driver] Unknown token received from SQL Server…

We are working on a resolution and will provide an update in an upcoming release.

After installing this update on Hyper-V hosts managed by SDN configured System Center Virtual Machine Manager (VMM), you might receive an error on workflows involving creating a new Network Adapter (also called a Network Interface Card or NIC) joined to a VM network or a new Virtual Machine (VM) with a Network Adapter joined to a VM network. Existing VMs with existing Network Adapters should not have issues connecting after installing this update, only new Network Adapters created after installation of this update are affected.

When experiencing this issue, you might receive one of the following errors:

When creating a new VM or a new network adapter on an existing VM, you might receive, “<vmName> failed to modify device ‘Ethernet Connection”

Software defined networking (SDN) software load balancer service might fail, and you might receive, “<SLBVMName> failed to modify device ‘Ethernet Connection’ error”

SDN RAS Gateway service might fail, and you might receive, “<GatewayVMName> failed to modify device ‘Ethernet Connection’ error”

* mitigation and script available.

1 user thanked author for this post.

deuxbits

Reply | Quote

Oops! This month I forgot to reset my Local Group Policy Editor update deferral after my November quality updates for Win 10 Pro. Yikes!

I normally keep quality updates deferred for 30 days, or until the AskWoody all clear is given. As a result the December updates just got auto-installed, and a reboot request popped up today!

So far, so good, as a home user with Win10 22H2 Pro. Whew! But at least I had last night’s image available if needed! 🙂

2 users thanked author for this post.

Microfix, geekdom

Reply | Quote

For those who installed .NET core 3.1 updates, are you keeping it installed because some program still requires it? .NET core 3.1 is end of support as of this Tuesday and will no longer get updates: https://devblogs.microsoft.com/dotnet/net-core-3-1-will-reach-end-of-support-on-december-13-2022/

Reply | Quote

KB5012170 might fail to install and you might receive a 0x800f0922 error

When attempting to install KB5012170, it might fail to install, and you might receive an error 0x800f0922.

Note: This issue only affects the Security update for Secure Boot DBX ( KB5012170) and does not affect the latest cumulative security updates, monthly rollups, or security only updates.

Workaround: This issue can be mitigated on some devices by updating the UEFI bios to the latest version before attempting to install KB5012170.

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

Affected platforms:

​Client: Windows 11, version 22H2; Windows 11, version 21H2; Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSC 2016; Windows 10 Enterprise 2015 LTSB; Windows 8.1
​Server: Windows Server 2022; Windows Server, version 20H2; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012

Reply | Quote

Updated so far with no problems:

1x Win7 Ultimate: KB5021291 Rollup, KB5020861 .NET 3.5.1, KB5020879 .NET 4.8

x2 Win8.1 Pro: KB5021294 Rollup, KB5020862 .NET 3.5, KB5020878 .NET 4.8

x3 Win10 22H2 Build 19045.2364: KB5021233 CU, KB5021089 .NET Rollup. Hid KB5012170

1x Win11 22H2 Pro Build 22621.963: KB5021255 CU, KB5020880 .NET Rollup Hid KB5012170

1x Win11 on ARM Pro Insider Preview Beta 22H2 Build 22623.1028: KB5021866 CU, KB5020880 .NET Rollup

I have also been hiding KB4023057 when it showed up.

*****
x1 M1 MacMini 16GB RAM, 1T NVME: MacOS Monterey 12.6.2 + Safari 12.6
x1 iMac4K Intel gen 7 Kaby Lake i7 7700 32GB RAM, 512GB SSD: MacOS Monterey 12.6.2 + Safari 12.6
x1 15″ MacBook Pro Intel gen 4 Haswell i7 4960HQ, 16GB RAM, 512GB SSD: MacOS Big Sur 11.7.2 + Safari 12.6

2 users thanked author for this post.

geekdom, Microfix

Reply | Quote

Windows 10 Pro 22H2 (i7 8 Gen, 32GB RAM, 256GB SSD).
Took 22 Min. from start to desktop
Winver 19045.2364

All well.

1 user thanked author for this post.

geekdom

Reply | Quote

Microsoft fixed (again) gaming performance in Windows 11 22H2. Removed block.

https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2#2950msgdesc

..Resolution: This issue was resolved in KB5020044 and the safeguard hold has been removed as of December 14, 2022. Please note, if there are no other safeguards that affect your device, it can take up to 48 hours before the update to Windows 11, version 22H2 is offered. ..

Reply | Quote

https://learn.microsoft.com/en-us/windows/release-health/status-windows-10-22h2#2983msgdesc

Taskbar elements might flicker and causes device instability

After installing updates released September 20, 2022 or later, taskbar elements might flicker and cause system instability. Symptoms might include:

​The Weather or News and Interests widget or icons flickers on the Windows taskbar
​The Windows taskbar stops responding
​Windows Explorer stops responding
​Applications including Microsoft Word or Excel might stop responding if they are open when the issue occurs..

This issue is resolved using Known Issue Rollback (KIR)

Reply | Quote

Slightly confusing (this is MS after all) in that it is claimed this has been the case since September, but no indication why they are reporting it now.

Questions MS should have answered: Does the December (2022) cumulative update make it worse? Does it surface it if it wasn’t apparent previously? If you have not been affected by it with the September, October and November updates, is the December update likely to cause it?

Reply | Quote

KB5021233 : Client: Windows 10, version 22H2; Windows 10, version 21H2; Windows 10, version 21H1; Windows 10, version 20H2

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

After installing KB5021233, some Windows devices might start up to an error (0xc000021a) with a blue screen. Technical note: After installing KB5021233, there might be a mismatch between the file versions of hidparse.sys in c:/windows/system32 and c:/windows/system32/drivers (assuming Windows is installed to your C: drive), which might cause signature validation to fail when cleanup occurs.

Workaround: To mitigate this issue on devices already experiencing it, you will need to use Windows Recovery Environment (WinRE) with the following steps:…

Important: It is not recommended to follow any other workaround than those recommended above. We do not recommend deleting the hidparse.sys from your Windows\System32 folder.

Next steps: We are working on a resolution and will provide an update in an upcoming release.

5 users thanked author for this post.

curious leo, wavy, abbodi86, oldfry, creem

Reply | Quote

Hi Susan:

Windows Update successfully installed the following Dec 2022 Patch Tuesday updates on my Win 10 Pro v22H2 laptop and I haven’t noticed any negative effects so far:

• KB5021233: 2022-12 Cumulative Update for Win 10 Version 21H2 for x64 (OS Build 19045.2364)
• KB5021953: 2022-12 .NET Core 3.1.32 Update for x64 Client*
• KB5021954: 2022-12 .NET 6.0.12 Update for x64 Client *
• KB5021089: 2022-12 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Win 10 v21H2 for x64 *
• KB890830 : Windows Malicious Software Removal Tool x64 – v5.108

* Includes security patch for CVE-2022-41089

One small bit of good news. Unlike previous Patch Tuesdays, Windows Update proceeded normally and I was not prompted to “Restart Now” until all updates had finished installing. In previous months, Windows Update would prompt me to “Restart Now” as soon as my MS .NET Framework 3.5, 4.8 and 4.8.1 update (if offered) finished installing, even if my monthly cumulative Quality Update was still installing (see my image in post # 2497973 of last month’s November Updates Are Here for one example). For some reason the installation of this month’s MS .NET Framework 3.5, 4.8 and 4.8.1 update ran to completion without displaying the usual “Status: Pending Restart” after it reached “Status: Installing – 100%”.

Note that I was NOT offered this month’s KB5012170: 2022-12 Security Update for Windows 10 Version 22H2 for x64-based Systems (i.e., the Security Update for Secure Boot DBX). It seems a bit odd to me that the KB5012170 release notes <here> indicate that the latest KB5012170 for 64-bit Win 10 v22H2 includes TpmTasks.dll v10.0.14393.5285 (dated 21-Jul-2022), while the KB5012170 for 64-bit Win 10 v21H2 that was installed with my August 2022 Patch Tuesday Updates when I was still on Win 10 v21H1 (see first image below) included TpmTasks.dll v10.0.19041.1880 (dated 11-Jul-2022) with a higher version number.  I checked C:\Windows\system32\TpmTasks.dll and my current version is listed as v10.0.19041.2311 (created 19-Dec-2022) so there must be something other than KB5012170 that can modify the dbupdate.bin, dbxupdate.bin and/or TpmTasks.dll files that are bundled inside KB5012170.

I should add that System Information (msinfo32) confirms that Secure Boot is currently disabled on my system.

———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2364 * Firefox v108.0.1 * Microsoft Defender v4.18.2211.5-1.1.19900.2 * Malwarebytes Premium v4.5.19.229-1.0.1860 * Macrium Reflect Free v8.0.7175

2 users thanked author for this post.

DrBonzo, geekdom

Reply | Quote

Did you install KB5012170 with v21H2? it’s the same as v22H2
the KB article is mistaken about file version (someone accidentally copied v1607 info)

TpmTasks.dll can be updated with latest cumulative update (regularly)
but dbupdate.bin, dbxupdate.bin are only updated via KB5012170

2 users thanked author for this post.

lmacri, DrBonzo

Reply | Quote

abbodi86 wrote:

Did you install KB5012170 with v21H2?…TpmTasks.dll can be updated with latest cumulative update (regularly) but dbupdate.bin, dbxupdate.bin are only updated via KB5012170

Hi abbodi86:

Yes, my first image in post # 2509885 shows that the Secure Boot DBX update KB5012170 (2202-08 Security Update for Windows 10 Version 21H2) was installed with my August 2022 Patch Tuesday updates on 12-Aug-2022 when I was still on Win 10 Pro v21H2 (I updated from v21H2 to v22H2 on 06-Dec-2022).  The second image in that post shows that the dbxupdate.bin file in C:\Windows\System32\SecureBootUpdate\ was also created on that same date on 12-Aug-2022.

That second image in post # 2509885 shows that C:\Windows\System32\SecureBootUpdate\dbupdate.bin was created on 07-Dec-2019. I can’t say for certain what KB update installed that file, since I reset my Dell Inspiron 5584 back to factory condition in August 2020, and the only KB5012170 listed in my Windows Update history (or displayed by the command wmic qfe | find “KB5012170” in an elevated command prompt) is the KB5012170 installed on 12-Aug-2022.

As previously noted in post # 2509885, my current TpmTasks.dll v10.0.19041.2311 was created on 19-Dec-2022, which is the same day my December 2022 Patch Tuesday updates were installed.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2364 * Firefox v108.0.1 * Microsoft Defender v4.18.2211.5-1.1.19900.2 * Malwarebytes Premium v4.5.19.229-1.0.1860 * Macrium Reflect Free v8.0.7175

Reply | Quote

Both files have existed out of the box since Windows 8, secure boot updates just update them.
dbupdate.bin is a placebo file that never gets updated.
dbxupdate.bin is the one that matters.

1 user thanked author for this post.

lmacri

Reply | Quote

Has anyone with a Win 10 v22H2 noticed RuntimeBroker.exe errors being logged in their Reliability Monitor / Event Viewer since installing their December 2022 Patch Tuesday (OS Build 19045.2364) updates were installed?

I applied my Dec 2022 Patch Tuesday updates on my Win 10 v22H2 laptop on 19-Dec-2022 (see post # 2509885 in this thread) and since then I’ve noticed that my Reliability Monitor has logged a RuntimeBroker.exe error once a day. The faulting module name is usually ntdll.dll (but today it was combase.dll) and all errors seem to be related to Windows Search (see attached image and log for my 22-Dec-2022 error). System File Checker (sfc /scannow) and the DISM command Dism /Online /Cleanup-Image /CheckHealth do not find any problems with my system files, and these RuntimeBroker.exe errors don’t seem to be causing any noticeable issues on my system.

I’ll try rebuilding my search index (Control Panel | Indexing Options | Advanced | Index Settings tab | Troubleshooting | Delete and Rebuild Index | Rebuild) and/or start a new topic if no one else is seeing a similar problem.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v22H2 build 19045.2364 * Firefox v108.0.1 * Microsoft Defender v4.18.2211.5-1.1.19900.2 * Malwarebytes Premium v4.5.19.229-1.0.1860 * Macrium Reflect Free v8.0.7175

Reply | Quote

I’m trying to get some information about KB5021089 which is on the Patch List as Install. I was just wondering what this KB is and if it is safe to install now, or should I just hide it and wait till the end of January?

I’m not sure I understand this part: “Parent KB – The Windows update will show the parent KB but you will see the “sub” KBs in update history”

When I follow the link to that KB, the MS info does seem to indicate that there may be an issue with that one. I’m not sure that applies in my situation, so is there any drawback to just hiding it and waiting till the end of January?

I have two Win 10 Pro laptops, both v 22H2, and this is offered on both through WuMgr.

I already hid KB5021233 and KB5012170 on both laptops.

Thanks!

Reply | Quote

KB5021089 is the Cumulative update for .NET Framework 3.5 – 4.8. It is safe to install

1 user thanked author for this post.

LHiggins

Reply | Quote

Great – thanks so much!

Reply | Quote

Question about the 2 sub KBs that show up under the .NET CU parent KB – looks like one of the subs is for .NET 3.5/4.8 framework and the other for .NET 3.5/4.8.1

If installing manually do you need both?  Or if you have .NET 3.5/4,8.1 framework can you just install the one sub KB?

Reply | Quote

3.5 is irrelevant here
if you manually installed .NET Framework 4.8.1, then you need the CU for it
otherwise, install .NET 3.5/4.8 CU

Reply | Quote

Yes, I get that 3.5 is irrelevant – I was trying to be clear on describing the sub KBs contents – both included 3.5 along with either 4.8 or 4.8.1.

I have .NET 4.8.1 so therefore I only install the sub KB for 4.8.1, correct?

Reply | Quote

Correct

Reply | Quote

lmacri wrote:

Has anyone with a Win 10 v22H2 noticed RuntimeBroker.exe errors being logged in their Reliability Monitor / Event Viewer since installing their December 2022 Patch Tuesday (OS Build 19045.2364) updates were installed?

I have none on my Windows 10 Pro 22H2.

RuntimeBroker.exe is triggered every time a Microsoft Store UMP app is open or updated.
I have uninstalled all UMP apps (except Microsoft Store) and blocked Microsoft Store updates on my PC.

Reply | Quote

lmacri wrote:

Has anyone with a Win 10 v22H2 noticed RuntimeBroker.exe errors being logged in their Reliability Monitor / Event Viewer since installing their December 2022 Patch Tuesday (OS Build 19045.2364) updates were installed?

Running Win10 Pro 22H2 with Dec updates installed and also no errors!

Just FYI, I also have MS Store updates disabled on mine, but RuntimeBroker.exe always shows it’s up and running (most likely because I have an RTX 3060 Ti GPU and the Nvidia Control Panel UWP is always running!)

1 user thanked author for this post.

Alex5723

Reply | Quote